Hi,

Does it make sense to separate out the development and deployment of "Modules" in CMake?

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)

Regards

_______________________________________________
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

Reply via email to