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?
Thx......John
On 10/14/15 6:45 AM, Nils Gladitz wrote:
On 14.10.2015 02:01, John Cary wrote:
For future reference, one can determine what triggered the
reconfigure by doing
make install VERBOSE=1
It appears not to be enough to have configured with
-DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE.
In our case, for reasons we have not yet figured out, the depend
file for a particular .cu.o object built for a test was what was newer
and causing the rebuild. For so-far not understood reasons, this
I am guessing the behaviour has nothing to do with the "install"
target but rather the default "all" target which "install" depends on
as well.
Hence you should see the same behaviour when running plain "make" twice.
FindCUDA.cmake forces reconfiguration so dependencies generated at
build time can be reprocessed:
https://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindCUDA.cmake;h=1fc582fae0dee409fca05af6c331c7377596bb7d;hb=refs/heads/master#l396
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
