So, what I suggest is this:
1. we take one/two good developers as a target, including you for instance. You are the user in this case, and a group of cmake developers should provide you with a way to express your build requirements for a set of libraries of your choice. The library should not be trivial to port though (for instance should not be header only and should have other dependencies), otherwise this would be useless for most of us. 2. you review and interact with the cmake port developers, trying to port eg. another library with the tools that were developed in the first stage. If this is too complicated/difficult/error prone, then we go back to 1. 3. once everybody is happy (or not) we write one tentative how-to and report back to the ML.
Sounds reasonable to me.
On my side, I will mostly try to do what is being done with b2 for boost.test. (Although some people do not like it) it is a central library I believe, and its integration to other project will raise a lot of issues.
What do you think?
Raffi
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
--- This email has been checked for viruses by AVG. http://www.avg.com