Hi, I was wondering if the official advice on re-running ‘configure_file’ has evolved? There’s some answers on StackOverflow about using custom targets / commands to force it but they seem … ugly.
Essentially I want configure_file to re-run each build - I still want the ‘only update the timestamp on the output file to change if the file is really changed’ logic, otherwise I could use file(WRITE). (I have some variables, expanded in the foo.in file which is the input to configure_file, which change fairly often but not every build, so I’d like to use configure_file to check these variables each build, but only touch/modify <output>.h when the variables really did change) Kind regards, James
smime.p7s
Description: S/MIME cryptographic signature
-- 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
