CMake build system is Merged into Trunk

With the encouragement of Doug Gregor and the support of other Boost moderators I have merged the work from the CMake branch into trunk. The CMake branch was a branch to develop a new build system for boost based on the opensource CMake build system (www.cmake.org). The current state of the build system is unstable and still has work to be done. Compiling of the static libraries on at least one system (OS X 10.5.5 Intel) was completed and the installation of the libraries and headers was performed. There is still much work to be done but we are hoping to quickly improve the state of the cmake build system so that it becomes usable. NOTHING has been done to compromise the current build system based on BJam. For more information on getting started with CMake and boost please take a look at this page: <https://svn.boost.org/trac/boost/wiki/CMake> I will be adding to the CMake documentation on the wiki as soon as I can. For those familiar with CMake here is the 2 second how to (For Unix/ line command): Install CMake 2.6.2 from www.cmake.org Update your Boost trunk. Open boost/CMakeLists.txt and comment out the following line: message(FATAL_ERROR "") Create a build directory for boost (I suggest 'Build' within the boost directory) cd into Build cmake ../ .. Let that go for a little while make modularize .. Let that go for a while. This WILL change the layout of the boost working directory so WATCH OUT for this. Once this is complete there is NO 'undo' so the only way to get your working directory back the way it was is to do a revert from svn. Once this runs the bjam system WILL break. So ONLY do this if you want to either work on the CMake system or try it out. And finally run make Windows Users: Run the 'cmake-gui.exe' app and point it to your working directory. Tell the app where to put its build files (Binary directory) and hit configure. Pick what type of build files you want generated, and then let it "configure" After it is done configuring click the "Generate" button. Your project files, makefiles, or Visual Studio files should now be created. Testing is NOT complete as of yet. I am still getting all the cmake files updated. If you have comments, feedback or anything else either file a bug in the trac system or come join us on the boost-cmake mailing list <http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Again, I would like to stress that NOTHING has been done to change the current bjam based build system. If it DID break let me know ASAP and I will fix it. Thanks _________________________________________________________ Mike Jackson mike.jackson@bluequartz.net BlueQuartz Software www.bluequartz.net Principal Software Engineer Dayton, Ohio

Michael Jackson wrote:
With the encouragement of Doug Gregor and the support of other Boost moderators I have merged the work from the CMake branch into trunk. <snip>
NOTHING has been done to compromise the current build system based on BJam.
First off, congrats, I'm glad to see this project moving forward. Providing support for a de-facto standard build system like CMake can only improve the lives of Boost users, and that's the most important thing. How does this effect the lives of Boost developers? My day-to-day work occasionally involves changing jamfiles. Will I also need to edit CMake files? Or is there a CMake build system champion who will be working to keep the two build systems in sync? -- Eric Niebler BoostPro Computing http://www.boostpro.com

On Nov 1, 2008, at 3:30 PM, Eric Niebler wrote:
Michael Jackson wrote:
With the encouragement of Doug Gregor and the support of other Boost moderators I have merged the work from the CMake branch into trunk. <snip> NOTHING has been done to compromise the current build system based on BJam.
First off, congrats, I'm glad to see this project moving forward. Providing support for a de-facto standard build system like CMake can only improve the lives of Boost users, and that's the most important thing.
How does this effect the lives of Boost developers? My day-to-day work occasionally involves changing jamfiles. Will I also need to edit CMake files? Or is there a CMake build system champion who will be working to keep the two build systems in sync?
-- Eric Niebler BoostPro Computing http://www.boostpro.com
I am not sure we have worked out who the "CMake Champion" is. If you understand CMake then updating the CMake files is straight forward. If you don't have any idea what to do then maybe an email to myself or the Boost-CMake mail list? This does present an interesting problem as the CMake build files will always be "Chasing a moving target". I guess some one will have to get some more docs up on trac about how to update the CMake files. At the minimum putting a simple message(STATUS "This Library [Library Name] was updated") in the CMakeLists.txt file for the library would at least let us know that something should be looked at for the library. Anyone else have any thoughts on this? _________________________________________________________ Mike Jackson mike.jackson@bluequartz.net www.bluequartz.net

AMDG Michael Jackson wrote:
With the encouragement of Doug Gregor and the support of other Boost moderators I have merged the work from the CMake branch into trunk.
Did you really intend to merge the 1.34.0 README.txt? The same goes for WELCOME.txt, although it is not out of date. In Christ, Steven Watanabe
participants (3)
-
Eric Niebler
-
Michael Jackson
-
Steven Watanabe