Hi all,
Is there a way to force a custom target (i.e., ADD_CUSTOM_TARGET) to be built
just before installation?
We have documentation added as a custom target that is **not** passed the "ALL"
keyword because generating the documentation is slow. However, that target
creates files that have a matching INSTALL, so "make install" or "ninja
install" will fail unless the target is built before installation. We want to
encourage developers to configure with documentation turned on, but want
buildbot/dashboard builds to work without magic options or special
configuration.
Along those lines:
1. Is there any ordering of INSTALL(CODE ...) relative to INSTALL(FILES ...)?
If it is guaranteed to run first, we could force the target to build that way.
2. Is there really nothing to replace the deprecated PRE_INSTALL_SCRIPT
property?
Thanks,
David
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
