[cmake-developers] Creating a separate project/package which provides cmake extensions/modules

[Eric Noulard]

2011/6/4 Alexander Neundorf <neundorf at kde.org>:
> Hi,
>
> again from the KDE sprint...
>
> We have around 150 cmake modules in kdelibs...
> Several libraries are not "before" kdelibs, so they don't have access to
> those.
>
> So, what we came up with is that create a new package which just contains our
> cmake modules, so they can be used by non-KDE applications.
> Of course, there we will also have to care about source compatibility and e.g.
> the required cmake version.
>
> So this is a middle ground between having this stuff in kdelibs and getting it
> completely upstreamed into cmake.
>
> I just noticed that there is https://github.com/rpavlik/cmake-modules .
> Maybe we can simple contribute to that one.

There is this one too:
http://code.google.com/p/cmake-modules/

> Do you think this is a reasonable plan or do you see conceptual issues with it
> ?

May be you should search the ML archive because I think some idea
concerning "external CMake modules" have already popped-up here and there.

An example of idea I submiited during a thread:
http://www.cmake.org/pipermail/cmake/2009-February/027145.html

You should be able to find other/better as well.
-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org