CMake TODO List

These are some features that we would like to implement in the CMake-based build system for Boost (in no particular order).

• Regression testing:
  • For each library, automatically introduce a test that uses the "inspect" program to verify that the library meets all of Boost's coding and licensing requirements (and anything else that inspect checks).
• Documentation generation:
  • Port the BoostBook toolchain over to CMake. Bonus points if it can use CMake to download the appropriate XSLT stylesheets and DocBook DTD using file(DOWNLOAD...), therefore taking the role of the BoostBook configuration scripts, too.
  • Installation of generated documentation.
• Extend boost_library_project to accept optional description, author, and maintainer arguments, and possibly other descriptive arguments that might be helpful for libraries (main documentation URL?). Having this information within the CMake system should make it easier to provide this information to users in various ways, e.g., a per-module description in the Windows installer.
• Determine how the "tools" directory should fit in with "libs". Right now, "tools" is disabled because it doesn't work well with modular libraries.
• Building and testing against an installed tree:
  • Allow a single Boost component's sources to be downloaded and built against an installed Boost
  • Allow regression tests to be built and executed against an installed Boost
  • Update regression-testing scripts to simulate a user's usage: build a Boost tree, build its installer, execute the installer, build the regression tests against the installed version (separately!), run regression tests and report the results.
• "Modularize" the rest of the Boost libraries
• Testing on more platforms and tweaks for those platforms