[CMake] Idea - Modules development and management

[Eric Noulard]

2009/12/7 Nicholas Yue <yue.nicholas at gmail.com>:
> Hi,
>
>   Does it make sense to separate out the development and deployment of
> "Modules" in CMake?

This kind of idea have already been raised on the ML.
May be you should dig the ML archive in order to collect past ideas
in order to see past pro- and cons- the main idea.

>   I see an advantage because Modules update are more frequent as more
> packages are added compare to the release cycle of CMake itself.
>
>   Maybe there is an easier way? Environment variable to point to an updated
> Module path (note : I am referring to a complete Module including everything
> that was originally ship with a given version of CMake, plus updates)

I think you could already do that now.
If you
 SET(CMAKE_MODULE_PATH /your/prefered/path)
in your CMakeLists.txt

then CMake will look in there first.


-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org