finding libraries for programs with doing clean builds

Thiago Macieira thiago at kde.org
Fri Jan 6 15:00:11 CET 2006


Matt Rogers wrote:
>I've tried to think of a good solution for this for the last couple of
> days and I haven't come up with much of anything. Does anybody else
> have some ideas on how to solve this? Obviously setting LD_LIBRARY_PATH
> before running scons works, but there will be a lot of directories that
> will need to be added once we get around to doing things like compiling
> docs, etc. and I'm wondering if we can do something better.

The only solution is to duplicate what libtool does, which is to determine 
how to run a program linked against uninstalled libraries.

Options are:
1) setting the proper environment variable when possible 
(DYLIB_LIBRARY_PATH, LD_LIBRARY_PATH, etc.)

2) relinking the program if no other suitable method is found

Note that a standard Linux uses option #2, because LD_LIBRARY_PATH won't 
work on a standard KDE installation that used --rpath.

Also note that the fact that we run program we've just built makes it 
impossible to do a KDE cross-compilation. The clean solution for this 
would be to split all programs we need for building KDE from the KDE 
build itself.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

1. On frumscafte, hwonne time_t wæs náht, se scieppend þone circolwyrde 
wundorcræftlíge cennede and seo eorðe wæs idel and hit wæs gód.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20060106/d03cd401/attachment.pgp


More information about the Kde-buildsystem mailing list