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 b
Thanks, setting the global variable solved my issue.
-Matt
> On Oct 13, 2015, at 10:46 AM, Johannes Zarl-Zierl
> wrote:
>
> Hi,
>
> CXX_STANDARD is a target property, not a global one. You can either set
> CXX_STANDARD for every target that needs it, or set it globally by changing
> the def
Hi,
CXX_STANDARD is a target property, not a global one. You can either set
CXX_STANDARD for every target that needs it, or set it globally by changing
the default value.
You can do the latter by setting the variable CMAKE_CXX_STANDARD before
defining any target that depends on it:
set(CMAKE
I would also like to know this, right now I do this and it works, but
it produced warnings on MSVC, so I did this nasty patch:
if(WIN32)
if(MINGW)
SET(CMAKE_CXX_FLAGS "-mwindows -std=c++11")
endif()
else()
SET(CMAKE_CXX_FLAGS "-std=c++11")
endif()
however doing just the SE
I have the following two lines in my CMakeLists.txt
set_property(GLOBAL PROPERTY CXX_STANDARD 11)
set_property(GLOBAL PROPERTY CXX_STANDARD_REQUIRED)
However when compiling some of my source files, the -std=c++11 flag is not
added.
Just for good measure I added:
target_compile_features(my_targe
Yeah, I thought about this method yesterday, but I'm not really excited
about this approach. It adds yet another variable for the configuration
that doesn't really match the others. Granted the behavior of the other
FindCUDA options allow setting it before the first FindCUDA invocation, so
there
Maybe we could make the FindCUDA script check if the caller defined that
variable prior to any inclusion. If the user did, then FindCUDA should
respect the caller choice.
Something like that would make the trick:
if(NOT DEFINED CUDA_USE_STATIC_CUDA_RUNTIME_FORCED)
if(DEFINED CUDA_USE_STATIC_CUDA
Dan Liew wrote:
> Hi,
>
>
>> - If not, what is the best/official way to get exact control over the
>> compiler and linker options used?
>
> I had to do something similar recently where I didn't want
> ``-DNDEBUG`` to be in any of the configurations.
>
> I used ``CMAKE_USER_MAKE_RULES_OVERRIDE
Hi,
> - If not, what is the best/official way to get exact control over the compiler
> and linker options used?
I had to do something similar recently where I didn't want
``-DNDEBUG`` to be in any of the configurations.
I used ``CMAKE_USER_MAKE_RULES_OVERRIDE `` to set the path to file
contain
