dolfin team mailing list archive

["Åsmund Ødegård" <aasmund@xxxxxxxxx>]

Yeah.

On Wed, Mar 12, 2008 at 9:39 AM, Martin Sandve Alnæs <martinal@xxxxxxxxx> wrote:
> I never got any definite answer on this one.
>
>  simula-scons places generated .pc-files in the first writable path
>  found in PKG_CONFIG_PATH, which can be the directory of some other
>  library.

Sure - it's what you put there!

>
>  I consider this bad behaviour. I don't want the build system of pycc
>  to write to f.ex. my syfi installation directory. I don't want to be
>  root or mess with chmod each time I install f.ex. syfi during
>  development.

Sure. The plan is to add an option --with-pkgconf-dir or something to
scons, and use #/scons/pkgconfig as the default.

>
>  In the case of the dolfin build system, the files should rather be
>  placed in the dolfin directory. An explicit option to place the files
>  in another directory would be nice (but of course they should never
>  overwrite existing files).

The downside is that every system that uses simula-scons will generate
its own set of .pc files, which must be kept in sync when you upgrade
dependencies. I have kind of an idea on how to fix that, though.

>
>  Also, it would be nice to be able to write something like
>   scons ... gtsDir=/opt/gts
>  instead of setting the environment variables like GTS_DIR.

Maybe... Thing is that putting it right in the environment makes life
simpler, as scons communicate with the pkgconfiggenerators through
env, because the pkgconfiggenerators also can be run outside scons.

But it is of course a simple thing to fix.

Åsmund