The cpp file dependency is generator specific. CMake supports cpp file dependency for Makefiles only. The solution we have works for any generator.
The dependencies could be generated at configure time, and I have a local version used internally where I work that does this, but it's not a cure-all. This is a complex issue that I've gone into in the past on the list. I hope at some future point this can be made better. On Mon, Oct 19, 2015 at 10:55 AM JR Cary <c...@txcorp.com> wrote: > Thanks for the response, James. Our workaround finally > was to do "make install/fast". > > A colleague pointed out that there is a bug report, > https://cmake.org/Bug/view.php?id=15801, > likely related to this. > > Is there something about CUDA that requires dependency generation > at build time? (I am used to the standard of "#include <foo>" following > that can be done before any build.) > > It would be nice if the CUDA dependency generation worked like regular > cpp file dependency generation so that cmake would be run only upon > change of files and that otherwise it did not have to be turned off > completely. > > Thanks! > > ....John > > On 10/18/15 10:03 PM, James Bigler wrote: > > This could be caused by CUDA generating dependencies and then needing to > load them at the next configure step. > > For our automated builds, where we don't rely on dependencies during > development (e.g. build one main target from scratch then throw it away), > we set the CMAKE_SUPPRESS_REGENERATION option to TRUE. This will prevent > CMake from configuring during the build. You can still configure manually > by running cmake. > > James > > On Wed, Oct 14, 2015 at 7:04 AM, Nils Gladitz <nilsglad...@gmail.com> > wrote: > >> On 14.10.2015 14:51, JR Cary wrote: >> >>> Thanks for your response. This is a big headache for us, as it slows >>> down >>> our builds tremendously. >>> >>> Is there any way to prevent or control this behavior? >>> >> >> I don't see how. You could modify the module itself I suppose but I'd >> expect that to break incremental builds. >> >> >> Nils >> -- >> >> 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 >> > > >
-- 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
