On 3/28/2013 1:17 PM, Alan W. Irwin wrote:
All projects should provide a "project config file .cmake script"
readable by CMake's find_package, and installed in a location where
CMake can find it, so that a CMake find module is completely unnecessary.
Hi David:
Your idea sounds like a good one, but can you recommend an easily understood
project that follows this approach that would serve as a good template
for build-system developers to use when implementing this approach for
their own projects?
CMake might need more modules. However, each one needs to come with a
module maintainer. I agree that in a perfect world all projects would
have cmake config files. But, we can not force all projects to move to
cmake, and new important projects will be created that do not have
direct CMake support in them. They will need new CMake modules. I
would rather see direct additions to CMake than a separate module repo.
http://www.cmake.org/Wiki/CMake:Module_Maintainers
-Bill
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
