Hi Doug, Thanks for all the work on this. On 05/23/08 14:48, Doug Gregor wrote: [snip]
Anyone interested in joining this effort should read about CMake and our CMake-based build system for Boost (links below), then join the Boost-CMake mailing list (also below). To get a sense of the kind of deployment options we would like CMake to provide in the future, please download the CMake-generated binary installer for Windows, linked below, and direct comments to the Boost-CMake mailing list. [snip] Useful links: CMake: http://www.cmake.org Boost-CMake documentation: http://svn.boost.org/trac/boost/wiki/CMake Boost-CMake mailing list: http://lists.boost.org/mailman/listinfo.cgi/boost-cmake [snip]
I got to the page: http://svn.boost.org/trac/boost/wiki/CMakeBuildFeatures from a link on: http://svn.boost.org/trac/boost/wiki/CMake with name: * Tune the CMake build configuration (verbosity, tests, variants)? However, nothing on CMakeBuildFeatures mentions how to specify which compiler *variant* to use. Also, http://svn.boost.org/trac/boost/wiki/CMakeBuildConfiguration mentions ccmake without any link explaining where to get it. Also on CMakeBuildConfiguration there's: On unix, run ccmake <path-to-source> or ccmake <path-to-build> but no explanation of why there's two ways to do what, at this point in the docs, appears to be the same thing. Only later, at the phrase: The same information is stored in a file CMakeCache.txt located in the build directory. This is what ccmake reads if it is started pointing to a build directory. is the reason for the 2nd cmake command obvious; however, it would be clearer to say run: ccmake <path-to-source> the first time, and then you can run: ccmake <path-to-build> -regards, Larry