Hello, I am trying to create CMake-based build system for a program that uses both C and Fortran source files. While expanding the CMakeLists.txt files to include a custom build step for one C header file, I stumbled on something I do not understand.
The makefiles generated from my first versions did not seem to include any dependencies from #include (the file "depend.make" was simply a dummy). When I added my custom build step, I had great difficulty to get the dependencies right. The file "depend.make" remained empty. Then I added a call to set_source_files_properties() to explicitly set the dependency on that one header file and now I see that _all_ C files in the project are listed there. So, my question: is it the set_source_files_properties() command that turns on this scanning? Is there a more explicit way (I want to have this scanning turned on regardless of any explicit dependencies I need). I am using CMake 2.8 Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. _______________________________________________ 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://www.cmake.org/mailman/listinfo/cmake
