|
From: Mat M. <mm...@ad...> - 2005-05-17 00:19:02
|
I submitted some substantial changes to the Jamfiles. Some work still needs to be done, but the files seem to triggering the right actions for visual/test md5/test and all of their dependents. A good test is to cd to adove/visual and issue a bjam command--this should cause a build of asl_lib_dev, boost_thread, boost_signal, boost_filesystem, libvisual and the visual app. Some of the changes: 1) Added new Boost Build feature: <asl> with value none or dev. Right now <asl>dev simply causes ADOBE_SERIALIZATION to be defined. But by setting this to a feature libraries get built in separate directories so the adobe/build/Jamfile has been greatly simplified. 2) Fixed the Jamfile.v2 for boost threads. I am attaching the patched file here since it didn't make it into the latest drop. 3) All targets are built with static linking at the moment. This can be fixed, but boost_thread has some complicated requirements in this area. 4) Added a new Jamfile to adobe directory to hold common settings. Projects build successfully with msvc compiler. Some work is needed for gcc 3.3 on mac and windows. Other platforms untested. Suggestions/improvements very welcome. |