2009/12/6 Alan W. Irwin <ir...@beluga.phys.uvic.ca>:
>>
>> With this feature you'll get a "portable" project which contains the
>> source tree,
>> a preconfigured build tree + some cmake binaries corresponding to the
>> build tree.
>>
>
> Eric, I didn't see your e-mail before I sent mine. However, now that I have
> read yours, I think your above idea of including cmake in the "source"
> distribution is an excellent one which answers my two caveats (and also your
> additional regeneration caveat above).
I'm glad you find it nice :-)
Currently it may not be done "out-of-the-box" but I think it should be doable
if we can
1) create an archive which contains cmake binaries
It could be done with a FILE(DOWNLOAD pointing to
appropriate http://www.cmake.org/files/v2.8/cmake-2.8.0-XXXX
Another solution would be to add to cmake the builtin capability
to re-create a CMake binary archive from the currently installed cmake,
by calling CMake itself:
cmake --create-cmake-redist ZIP
2) Packaged the pre-configured binary tree such that
next build would automatically trigger a cmake run pointing
to the sibling source tree such that absolute path name could
be updated appropriately by CMake itself.
The problem here is that CMakeCache.txt may be "mostly" invalid
because it would contain absolute path name.
So may be the CMakeCache.txt should be pruned before packaging.
The proposed scheme may be "manually" tested before trying to automate it.
However I'm afraid I won't have the time to do it myself in the short
term though :-(
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
_______________________________________________
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
