Hi! Thanks for joining the thread.
On Wed, 13 May 2015 09:58:02 +1000 Graeme Gill <gra...@argyllcms.com> wrote: > 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. Of course this patch is a rather ugly hack that is not portable. I don't know enough about Jam to properly implement that, but fortunately there are already parts in the makefiles (or rather, jamfiles) that enable shared libraries. My goal was to change as little as possible, so that until the upstream supports that (I have been waiting quite a few months now) it can be used in Debian. > 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). I noticed this $ORIGIN and wondered what it was :) It was late evening and I just wanted to make it work. Sounds good! Thanks a lot for your comments - and of course also for maintaining argyll :) Yours, Wolfgang Oertl
smime.p7s
Description: S/MIME cryptographic signature
