configure_file() only copies changed files, so that *must* trigger a rebuild of all dependent files.
Michael On 17.02.2011, at 14:37, Carminati Federico <[email protected]> wrote: > Thanks John, > Indeed there is one and this is certainly part of the problem. We also found > out that using "configure_file" to copy files can generate large rebuild of > the entire makefile structure. We will have to look into this. Best regards, > > Federico Carminati > CERN-PH > 1211 Geneva 23 > Switzerland > Tel: +41 22 76 74959 > Fax: +41 22 76 68505 > Mobile: +41 76 487 4843 > > > > On 17 Feb 2011, at 14:05, John Drescher wrote: > >>> apologies for the stupid question. I have a large project and at times a >>> change triggers unexpected consequences, i.e. very large recompilations, >>> rebuild of the cmake makefiles and so on. Is there a way in cmake to >>> understand why things happens? I mean which chain of dependencies causes a >>> given action to be taken? It would be for me very interesting to understand >>> something more about the dependencies in my project, to be able to reduce >>> them. Thanks and best regards, >>> >> Are you generating header files in CMake? If so these change on every >> invocation of CMake? And is a lot of your project dependent on these >> header files? >> >> John > > _______________________________________________ > 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 _______________________________________________ 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
