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
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
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
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
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
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
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
In our use of cmake on a particular project, we noticed that
after building the project, upon invoking "make install", the
build starts all over again. Hence we are building the project
twice.
It seems that this is occurring because nearly everything depends
on the target,
