[CMake] CMakeModules repository at GitHub?

David Cole dlrdave at aol.com
Thu Mar 28 18:26:27 EDT 2013


Qt is actually the perfect example of this. Stephen Kelly has done a 
superb job getting project config files working with Qt 5. That's right 
-- you can actually do a find_package of Qt for Qt 5 with an existing 
CMake release, *without* having a FindQt5.cmake file in CMake itself. 
It's awesome!

Good idea, Bill to add to the module maintainer wiki page suggesting 
that they first attempt adding a project config file, using Qt 5 as a 
very good example.


David C.

-----Original Message-----
From: Bill Hoffman <bill.hoffman at kitware.com>
To: cmake <cmake at cmake.org>
Sent: Thu, Mar 28, 2013 5:39 pm
Subject: Re: [CMake] CMakeModules repository at GitHub?


On 3/28/2013 5:28 PM, David Cole wrote:
> I, too, live in the real world, in addition to having my theories 
about
> it... :-)
>
> And, for what it's worth, I'd rather add a project config file to any
> project out there that would accept code contributions from me than 
add
> yet another find module into CMake.
>
> Obviously, there will be cases where that is simply not possible for 
one
> reason or another. But it's still the preferred mechanism for
> hooking into CMake's find_package when it is possible.
>
> And when you have to resort to a find module, it should definitely 
live
> in CMake if it's generally useful for more than just your own use...
Well, put.  I like everything said here.  I am thinking maybe we should
update the ModuleMaintainers wiki entry to include instructions on how
to create and contribute a cmake config file to a non-cmake project and
suggest that that is done first.   Maybe it should be a requirement for
any new CMake module that you show that you tried to get a config file
upstream first and failed.  We might still need the module for older
versions of the software, but perhaps the job of the CMake module
maintainer needs to be expanded to include creating and submitting a
cmake config file into the upstream project.

This is a much smaller job than converting a whole project to cmake, 
and
works very well even in non-cmake based projects.

-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

  


More information about the CMake mailing list