Wolfgang Oertl wrote: Hi,
> As a regular user of argyll this itches enough for me to dig into the > Jam build system and to try to modify it so it uses shared libraries. Currently it is an important objective of mine for the ArgyllCMS tools to be robustly portable, while executable size is a lesser consideration. So making the utilities dependent on the install of shared libraries is not something I want to take up in my general ArgyllCMS distribution. I don't like the approach you have use at all - modifying Jambase to make the LibraryFromObjects rule create shared libraries is a hack - the correct approach is to change the Jamfiles to have a "build shared library" option set from Jamtop/emvironment, and then invoke the appropriate ShLibraryFromObjects rule in each Jamfile etc. > The path where the shared libraries are looked for has to be set at > build time and is now hard coded to /usr/local/lib/argyll. In the older > Debian package argyll this was /usr/lib/x86_86-linux-gnu/argyll on my > machine. That would have to be set correctly somehow. Not something I would do either, since it makes things non-movable. Instead I'd set the shared library path to point to where the executable are, i.e. use $ORIGIN. That way they can be locate anywhere, as long as the shared libraries go with them (see the SHLINKSEARCHEXEPATH variable in Jambase). Graeme Gill. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
