Changes between Version 15 and Version 16 of CMakeModularizationStatus


Ignore:
Timestamp:
Jan 1, 2012, 1:36:20 AM (11 years ago)
Author:
Dave Abrahams
Comment:

Added more TODOs

Legend:

Unmodified
Added
Removed
Modified

  • CMakeModularizationStatus

    v15 v16  
    3333together, with the latest state of each library.  Each time there's a change in the modularized state, we kick off integration tests.
    3434
    35 === TODOs ===
     35== TODOs ==
     36
     37=== Porting Test Jamfiles ===
    3638
    3739The integration testing columns are currently not all green in part because several
    3840libraries have not had their test Jamfiles ported to
    39 CMake yet.  [https://github.com/ryppl/boost-modularize/issues/search?q=unit+tests&state=closed These tickets] document the libraries whose test Jamfiles have been ported, and [https://github.com/ryppl/boost-modularize/issues/search?q=unit+tests&state=open these] are the libraries whose Jamfiles still need to be ported.
     41CMake yet.  [https://github.com/ryppl/boost-modularize/issues/search?q=unit+tests&state=closed These tickets] document the libraries whose test Jamfiles have been ported, and [https://github.com/ryppl/boost-modularize/issues/search?q=unit+tests&state=open these] show the libraries whose Jamfiles still need to be ported.
    4042Most of these should be
    4143really straightforward to handle based on looking at Jamfiles and examples of commits that [https://github.com/ryppl/boost-modularize/issues/search?q=unit+tests&state=closed closed unit test tickets] (follow the link in each ticket).
    … …  
    4547the most complex because they have to invoke Python instead of just
    4648building and running C++ executables.
     49
     50=== Porting Documentation Jamfiles ===
     51
     52Libraries with generated documentation (e.g. via quickbook or docbook or RestructuredText) need to have their Jamfiles ported as well.  There's a list of tickets [https://github.com/ryppl/boost-modularize/issues/search?q=documentation&state=open here].
     53
     54=== Rewriting Boost History ===
     55
     56Several methods have been discussed for preserving the history of Boost in the modularized git repositories; we still have to settle on and implement one approach.  The easiest to implement, though not necessarily the most useful possible arrangement, would be to simply allow people to graft the Boost SVN history onto their modularized Git repository.
     57
     58=== Further Testing ===
     59
     60There are several levels at which we might want to confirm that the CMake build instructions are doing the same thing that the Boost.Build Jamfiles are.