Changes between Version 32 and Version 33 of CMakeModularizationStatus
- Timestamp:
- May 9, 2012, 9:11:27 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CMakeModularizationStatus
v32 v33 1 1 [[PageOutline]] 2 2 3 = CMake Modularization Status =3 = CMake and Modularization Status = 4 4 5 5 Officially, all Boost libraries currently inhabit a [http://svn.boost.org/svn/boost single subversion repository]. … … 81 81 }}} 82 82 83 == CMake Support == 84 85 86 [http://github.com/boost-lib/boost Modularized Boost] is a Git superproject that references each modularized boost library as a Git submodule. There is a parallel [http://github.com/ryppl/boost-zero Modularized and CMake-ified Boost] project that has the same submodules, plus an [https://github.com/ryppl/boost-zero/tree/master/cmake "overlay" of CMakeLists.txt files] and an [https://github.com/ryppl/ryppl-cmake additional support] submodule. This is the project that you can use to build Boost with CMake. It is maintained by the same script as regular [http://github.com/boost-lib/boost Modularized Boost]. 87 83 88 === Integration Testing === 84 89 85 90 The other columns represent the results of Boost "integration tests" of 86 the modularized state on several platforms. An integration test is essentially equivalent to91 the modularized, CMake-ified state on several platforms. An integration test is essentially equivalent to 87 92 Boost's [http://www.boost.org/development/tests/trunk/developer/summary.html official unmodularized tests]: we run all of the libraries' tests 88 93 together, with the latest state of each library. Each time there's a change in the modularized state, we kick off integration tests. … … 93 98 #!sh 94 99 # get the the modularized boost superproject 95 git clone http://github.com/ boost-lib/boostmodules100 git clone http://github.com/ryppl/boost-zero modules 96 101 97 102 # Update all the submodules … … 126 131 really straightforward to handle based on looking at Jamfiles and examples of [https://github.com/ryppl/boost-modularize/issues/search?q=unit+tests&state=closed commits that closed unit test tickets] (follow the link in each ticket). 127 132 128 For a more complex example, see the [https://github.com/ boost-lib/python/blob/master/test/CMakeLists.txt CMake file for Boost.Python],133 For a more complex example, see the [https://github.com/ryppl/boost-zero/blob/master/cmake/python/CMakeLists.txt CMake file for Boost.Python], 129 134 graciously ported by Ravikiran Rajagopal. These are among 130 135 the most complex because they have to invoke Python instead of just