* Boost sources would provide a compatible, drop-in replacement for the 'FindBoost' module that is distributed with CMake. A CMake-based application could point to it and, instead of using the system Boost libraries, Boost targets would be built from source as part of the user build.
Instead of nasty cmake 2 era FindBoost(), why can't end users use the modern cmake 3 pattern: ``` find_package(boost COMPONENTS asio REQUIRED) target_link_libraries(myprogram PRIVATE boost::asio) ``` No cmake innovation needed to do this. This is 100% vanilla cmake 3. BTW David if you do decide to go down this route, you and the Steering Committee should seriously consider contracting Stephen Kelly to advise on doing this properly. He's the primary architect of cmake 3's improvements. He knows more about how to do this right than *anybody* on this list. It would also make good on the way he was chased away from here for the sin of changing other people's code without their permission despite that Dave had asked him to and given him the svn commit privs to do so. It would be the least the Steering Committee could do to put that wrong right and officially say sorry. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/