On 2009-12-30 12:30-0800 Talin wrote:
That is more along the lines of what I was looking for. Thanks! :) One further question: Using the technique you describe, the dependency file will need to be regenerated each time a source file changes - i.e. if I add a new "import" statement to a source file, the list of dependencies will change, which will require the dependency file to be rebuilt. Can that rebuild happen as part of the normal build, or can that only be done at CMake time?
Good question. The dependency information is used by CMake (at CMake time) to configure a custom command to be run at build time with the correct dependencies. Thus, the answer to your question must be that build time is too late to collect the dependency information used by CMake. Instead, you must do that at CMake time like I outlined. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ _______________________________________________ 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
