19 Nov
2015
19 Nov
'15
8:42 p.m.
Louis Dionne wrote:
Thanks to everybody for the comments. I, for one, think that a first step can be achieved by providing a CMake build system for new libraries, and slowly porting old libraries to CMake (without removing the old Boost.Build, of course). One thing that I also find useful is to provide a FindXXX.cmake module for my library, so it can be used as an external dependency to any CMake-based project quite easily.
That's the wrong thing to do. Provide XXXConfig.cmake instead. See my other mail in this thread for more. https://cmake.org/cmake/help/git-next/manual/cmake-packages.7.html Thanks, Steve.