[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: more comments about new build system
- To: petsc-dev@xxxxxxxxxxx
- Subject: Re: more comments about new build system
- From: "Lisandro Dalcin" <dalcinl@xxxxxxxxx>
- Date: Tue, 12 Jun 2007 12:18:57 -0300
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Rrg6JiaYZDf+ZEh6qjl2JMSsgj7USL7vlX5kFVH6OMO1clTHrryZhWtGKQFrMRmYYPLiPHXYozr06m9CN75HuiQfmlwhDN9y5RzgKg7N69wPdutWpl8uuBRo1IC0gtYk6dP71pX4hJ69iG/+41NMwI4Je7m0m3blg7aNj30BqKA=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XhMQp7IHSAUnGlrpFJ9zMOhie3c1yF2hrltpocbi6CrCmO/6WoQ+HiVGvJj2U37tfOwE/lZUsYqfkeU5KCXY/h1FaFpn6HQTF1U05QJnGMk6XHO4U9MQy0pmh+Eaoelu0gZviIhiSqZUijfC3OtzvANnfNM7P4o9gE4rHsIGSKk=
- In-reply-to: <Pine.OSX.4.64.0706112054120.24858@bsmith.local>
- References: <e7ba66e40706111606l7d674401h64cbbdd98dd1609a@mail.gmail.com> <Pine.OSX.4.64.0706112054120.24858@bsmith.local>
- Reply-to: petsc-dev@xxxxxxxxxxx
- Sender: owner-petsc-dev@xxxxxxxxxxx
Barry,
What about putting 'conf' inside '$PETSC_ARCH/lib'
In the build directory, arch specific 'conf' dir will be in
$PESC_DIR/$PETSC_ARCH/lib/conf
In the install directory, it will be
'$PETSC_PREFIX/lib/conf'
In such a case, perhaps you can use 'petsc' instead of 'conf'. I am
taking here python as example, in my box I have under '/usr/lib'
/usr/lib/libpython2.4.so -> libpython2.4.so.1.0
/usr/lib/libpython2.4.so.1.0
/usr/lib/python2.4
And also I have under '/usr/include'
/usr/include/python2.4
This is great because the standard 'include' dir is not populated with
many headers, but for petsc this would complicate things.
On 6/11/07, Barry Smith <bsmith@xxxxxxxxxxx> wrote:
Good point. etc was also suggested. Adding the petsc is
kind of ugly with the non-installed version, for example
petsc-dev/$PETSC_ARCH/shared/petsc/petscrules
instead of
petsc-dev/$PETSC_ARCH/shared/petscrules
These things are still up in the air and will be adjusted
as good ideas come in.
Barry
On Mon, 11 Jun 2007, Lisandro Dalcin wrote:
> If one of the goals of the new build system is to be more symmetric
> with the GNU model, in order to make life easier for packagers, so I
> think the '$PETSC_PREFIX/conf' location should be renamed, perhaps to
> '$PETSC_PREFIX/share/petsc'. I believe 'conf' is not a 'standard'
> location.
>
>
>
>
--
Lisandro Dalcín
---------------
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594