[email protected] wrote:
> Brad King wrote:
>> Perhaps the install() command is better for that.
>
> it adds an extra step into the procedure
Just run "make install" instead of "make".
> just collecting .exes and .dlls in a directory within
> ${my_project_BINARY_DIR} is hardly a bona fide installation procedure
If you're staging for use by other machines, does it not make
sense to have an explicit stage directory? How is that different
from creating an "install" tree just to create a tarball for
distribution?
The install() command was designed to give precise control over
the construction of install trees (AKA stages before tarballing).
I see no strong need to duplicate this functionality to the same
level of precision for the build outputs.
-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
