Hi Eric, > Am 27.06.2019 um 13:06 schrieb Eric Doenges <doen...@mvtec.com>: > > I can't help you with your other issues, but I believe the solution to this > problem is to specify "BUILD_ALWAYS TRUE" in your ExternalProject_Add. From > the documentation for ExternalProject_Add: > Enabling this option forces the build step to always be run. This can be the > easiest way to robustly ensure that the external project’s own build > dependencies are evaluated rather than relying on the default success > timestamp-based method. This option is not normally needed unless developers > are expected to modify something the external project’s build depends on in a > way that is not detectable via the step target dependencies (e.g. SOURCE_DIR > is used without a download method and developers might modify the sources in > SOURCE_DIR).
I’ve applied this option and will see if it helps. thanks, Torsten
signature.asc
Description: Message signed with OpenPGP
-- 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
