Hi, Sounds reasonable to me. It reminds me th autoconf archive project. Also, I have always been doing the same: keep my cmake modules in a separate repository which is added as a submodule in all my others projects.
-Nico On Saturday, June 4, 2011, Alexander Neundorf <[email protected]> wrote: > 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. > > I'll get in contact and we'll see what comes out of it. > > Do you think this is a reasonable plan or do you see conceptual issues with it > ? > > Alex > _______________________________________________ > cmake-developers mailing list > [email protected] > http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers > -- Nicolas Desprès _______________________________________________ cmake-developers mailing list [email protected] http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
