Here is my current thoughts on those:
SVN Merge of CMake support into the Boost trunk - If we are just talking about merging in the CMakeList.txt and .cmake files then that shouldn't take more than a half day assuming a few things. I can merge locally then commit all the CMake files to the Boost trunk. If there are other files to merge besides these then this will take me longer as I am not familiar with some portions of Boost.

Finish Modularization of Boost Libraries - I am still walking through the CMake build system for boost. What I have been able to ascertain so far is that the "modularization" of the boost libraries is adding a consistent include directory structure in each sub part of Boost. I will have to read some of the emails to get some background on the design goals of this effort to more accurately decide the length of time required. If the task is basically just copying what is being done for all the other libraries then the initial modularization support is straight forward, just tedious.

Am I on the right track for these?

_________________________________________________________
Mike Jackson                  [EMAIL PROTECTED]
BlueQuartz Software                    www.bluequartz.net
Principal Software Engineer                  Dayton, Ohio



On Oct 27, 2008, at 5:04 PM, David Abrahams wrote:


on Mon Oct 27 2008, Mike Jackson <mike.jackson-AT-bluequartz.net> wrote:

Doug
 Is there any more work to be done on this front? I am looking for a
project to work in the immediate future and I think my own CMake
experience may help to finish this up if needed. Also what else would
need to be worked on?

Doug is exceedingly busy at the moment, but from what he told me, only
some fraction of the libraries have been modularized, and it would be a
big improvement if we could modularize them all.

Another thing you could do, for which I'd be happy to give you svn write
permission, is merge all the CMake support into the Boost trunk.  As I
mentioned earlier, it will make a big difference to be able to get test results for something useful, rather than the outdated boost-cmake branch.

--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
_______________________________________________
Boost-cmake mailing list
Boost-cmake@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-cmake

_______________________________________________
Boost-cmake mailing list
Boost-cmake@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-cmake

Reply via email to