2009/2/17 Alexander Neundorf <a.neundorf-w...@gmx.net>:
>>
>> But a http://autoconf-archive.cryp.to/ type archive for CMake modules
>> would also be a good idea.
>
> At FOSDEM we also discussed about something like this, some kind of
> semi-official place where to get additional cmake files.
> Right now you can look in several places, KDE being one of them.
>
> One idea was to actually ship those files as "unsupported" with cmake, but in
> a directory which is not searched by cmake by default, so that if somebody
> wants to use a file from this directory, he has to do something manually
> (either copy the file somwhere or set CMAKE_MODULE_PATH) to use it.
You may find conflict when trying to bundle the file.
Since CMake CVS seems to be able to file(DOWNLOAD
then only shipping convenient macros that is able to
[conditionnally] and selectively download "unsupported" macros files would
be "better" because:
1) CMake bundler won't have to choose which "unsupported" cmake macros
to bundle
2) One can get up-to-date "unsupported" macro without waiting for next CMake
release
I would go for a macro whose signature may be
get_additionnal_cmake_scripts(URL LOCALFILENAME FORCE_UPDATE)
which would may be usable like this:
get_additionnal_cmake_scripts(http://websvn.kde.org/trunk/KDE/kdeutils/cmake/modules/FindLibZip.cmake
${PROJECT_SOURCE_DIR}/cmake/FindLibZip.cmake
)
--
Erk
_______________________________________________
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
