The following issue has been SUBMITTED. ====================================================================== http://www.cmake.org/Bug/view.php?id=13582 ====================================================================== Reported By: Boian Petkantchin Assigned To: ====================================================================== Project: CMake Issue ID: 13582 Category: CMake Reproducibility: always Severity: minor Priority: normal Status: new ====================================================================== Date Submitted: 2012-10-10 04:47 EDT Last Modified: 2012-10-10 04:47 EDT ====================================================================== Summary: configure_file: change in the generated config file does not triger regeneration on make Description: We have a project, which generates a configuration file. If the file is changed outside of CMake and then a make is issued, the configuration file is not regenerated. On the other hand, if cmake is issued in the binary directory, the configuration file is freshly regenerated. Shouldn't the generated config file be monitored for an outside change and regenerated if needed? After all, it is almost like another target during the build process. ======================================================================
Issue History Date Modified Username Field Change ====================================================================== 2012-10-10 04:47 Boian PetkantchinNew Issue ====================================================================== -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers