Am Wed, 13 May 2015 14:49:12 +1000 schrieb Graeme Gill <gra...@argyllcms.com>: > Modifying Jambase is the harder and more risky approach - changing > Jamfiles is far safer and less complex.
On the other hand, there are many Jamfiles, and just one Jambase file, so if the latter could be adapted to support both build modes, it would probably be easier to maintain. The Jamfile could specify what should be a regular .a library, and what can be either. It probably has been discussed before, but I can't help mentioning it. I'm not quite sure what the real advantages of Jam are over gmake, which is widely deployed, very portable in conjunction with the autotools package, and everybody knows it, so it is easier to maintain. No need for a 100k+ Jambase file that provides portability, which certainly fails now with the shared library patch I concocted. Just my 2¢. Cheers, Wolfgang Oertl
smime.p7s
Description: S/MIME cryptographic signature
