*: _bjam:_ Created as a replacement/extension to perforce JAM it has it's own syntax and supports numerous platforms, it also does not provide flexible packaging features, and lacks the transition glue to move from an auto-tools style build.
-*: *CMake - winner:* CMake is widely adopted in the open source community as a x-platform replacement for auto-tools style builds. It has it's own Macro-style syntax, but unlike the afore mentioned tools it is a generator similar to Imake. Therefore it
+*: *CMake - winner:* CMake is widely adopted in the open source community as a x-platform replacement for auto-tools style builds. It has it's own Macro-style syntax, but unlike the afore mentioned tools it is a generator similar to Imake and it works with existing tools (make, visual studio). Another powerful tool build alongside is CPack which allows for various methods of packaging, across multiple OS distributions.
{section: Plan and phases}
@@ -28,7 +28,7 @@
Time Elapsed: ~1.2 Months
X - Setup existing environment build and analyze.
- X - Create full configuration (autoconf-cmake)
+ X - Create full configuration (auhtmlonf-cmake)
X - Build for linux and Windows
X - Simplify build files (done through cmake macros and updated file extensions .unix .linux .window)
X - Develop plan for dealing with externals
@@ -75,7 +75,10 @@
-----
-*[On Hold per 7.4.0] Stage 2:* Evaluation, Adoption, & Continuation (~1 - ? Months)
+*[On Hold per 7.4.0] Stage 2: Evaluation, Adoption, & Continuation*
+
+ Estimated: ~1 - ? Months
+ Time Elapsed: On Hold
X Cleanup and cruft and provide tracking branch for UW. (origin/CMAKE)
X Setup an wiki page
@@ -86,7 +89,8 @@
-----
- *Stage 3:* Full Parallel Build, Test, and Packaging (Last Month)
+*Stage 3: Full Parallel Build, Test, and Packaging (Last Month)*
+
- Full build and test should be able to run from parallel branch. (Propose switch over.)
- Establish full unit testing examples along-side, you pretty much get this for free (CTest + boost::test)
- Establish packaging using CPack for *all platforms.
@@ -94,7 +98,8 @@
- Do we "need" to support .msi? why?
------
- *Stage 4:* Proper cleanup (optional)
+*Stage 4: Proper cleanup (optional/on-going task)*
+
- start to move the code so #ifdef's are isolated to a bottom layer. The code should never have #ifdef's above a certain point as it simply should not care. This eliminates deps, and allows for easier code refactoring.
{section: Getting Started }
@@ -111,3 +116,7 @@
6.) make || open the visual studio project.
{section: Links}
+
+{link: http://www.cmake.org/cmake/help/documentation.html CMake Official Documentation}
+
+{link: http://www.google.com/codesearch Google Code Search for open source examples}
