Alan W. Irwin wrote: > On 2010-02-18 08:14-0500 Brad King wrote: > >> Alan W. Irwin wrote: >>> Could CMAKE_MODULE_PATH be treated as a colon-separate list of paths >>> that are >>> searched one after another? That would solve the common modules >>> issue for us. >> >> It is already a list: >> >> set(CMAKE_MODULE_PATH /some/path /some/other/path) >> list(APPEND CMAKE_MODULE_PATH /some/third/path) > > Thanks, Brad, for that information. That's going to help a lot in the > language support transition between 2.6.x and 2.8.x. > > The documentation in 2.8.1-RC3 currently says this about CMAKE_MODULE_PATH. > > CMAKE_MODULE_PATH > Path to look for cmake modules to load. > > Specifies a path to override the default search path for CMake > modules. For example include commands will look in this path first > for modules to include. > > Could you add a few words to make clear that CMAKE_MODULE_PATH is a list?
Clarify CMAKE_MODULE_PATH documentation /cvsroot/CMake/CMake/Source/cmDocumentVariables.cxx,v <-- Source/cmDocumentVariables.cxx new revision: 1.47; previous revision: 1.46 -Brad _______________________________________________ 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
