I'm working within a very large project on a python script. The script gets passed through configure_file to replace some @VAR@ strings with some file paths that are defined when cmake is run; this generates the final script. The side effect is that whenever I modify the file and run make, it re-runs cmake to regenerate the build system, and that cascades into all sorts of other things that are completely orthogonal to the script being rebuilt. Is there some more appropriate alternative to configure_file that should be used instead? Thanks for your expert advice!
--
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: http://public.kitware.com/mailman/listinfo/cmake
