>From my current research into this problem it looks like the issue can be
traced to these lines in FindCuda.cmake
--snip--
# Get the list of definitions from the directory property
get_directory_property(CUDA_NVCC_DEFINITIONS COMPILE_DEFINITIONS)
message( "CUDA_NVCC_DEFINITIONS = ${CUDA_NVCC_DEFINITIONS}" )
if(CUDA_NVCC_DEFINITIONS)
foreach(_definition ${CUDA_NVCC_DEFINITIONS})
list(APPEND nvcc_flags "-D${_definition}")
endforeach()
endif()
message( "nvcc_flags = ${nvcc_flags}" )
--end snip--
output from cmake as a result of added message line in Find.Cuda.
-- snip --
CUDA_NVCC_DEFINITIONS =
gpuReconPlugin_EXPORTS=yes;GPU_RECON=yes;CUDADeviceProperties_DLLExport=yes;GPU_RECON=yes;CUDADeviceProperties_DLLExport=yes;CPU_RECON=yes
nvcc_flags =
-m64;-DgpuReconPlugin_EXPORTS=yes;-DGPU_RECON=yes;-DCUDADeviceProperties_DLLExport=yes;-DGPU_RECON=yes;-DCUDADeviceProperties_DLLExport=yes;-DCPU_RECON=yes
-- end snip --
note the use of get_directory property. Have I mentioned to anyone lately
why I can't understand CMake's (poor) design choice in correlating
directory structure to target build specification. It would appear to me
from this (if unmodified) that I must create a new directory in order to get
CMake to build 2 dlls in the same directory based on the same source using
diffrent compiler defined. I have reached a state of boondogglement.
_______________________________________________
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
