As mentioned before - it is not only your cmake port, all presented boost-cmake files have ported only fraction of the required functionality. For instance feature tests used in Jamfile to test for presence/absence of some C++ features to control the build. Funny you mention that, I recently did some (porting) work on a library
On 19/07/2017 22:46, Oliver Kowalke via Boost wrote: that was planning to move to boost. The project uses CMake (because...well, documentation, support, real world compatibility, etc.. it's already been discussed). I needed to known if some feature was available so I started using a try_(compile|run)... and was asked to refrain from it as "you, know, at some point will have to use bjam, so we need to stick to basic stuff."
If it's so easy to do it with Cmake I'm wondering why it wasn't done. I've the impression that only the easy parts of Jamfile have been ported. The difficult parts are left ...
As Klemens already mentioned, I'm missing a discussion about the requirements of the boost build system and a comparison of pros/cons of other build systems on the ML.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost