No subject

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.

--0016e64bb9061281bc048df4e83b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br>From my current research into this problem it looks like the issue can =
be traced to=A0 these lines in FindCuda.cmake<br><br>--snip--<br>=A0 # Get =
the list of definitions from the directory property<br>=A0 get_directory_pr=
operty(CUDA_NVCC_DEFINITIONS COMPILE_DEFINITIONS)<br>
message( &quot;CUDA_NVCC_DEFINITIONS =3D ${CUDA_NVCC_DEFINITIONS}&quot; )<b=
r><br>=A0 if(CUDA_NVCC_DEFINITIONS)<br>=A0=A0=A0 foreach(_definition ${CUDA=
_NVCC_DEFINITIONS})<br>=A0=A0=A0=A0=A0 list(APPEND nvcc_flags &quot;-D${_de=
finition}&quot;)<br>
=A0=A0=A0 endforeach()<br>=A0 endif()<br>message( &quot;nvcc_flags =3D ${nv=
cc_flags}&quot; )<br>--end snip--<br><br>output from cmake as a result of a=
dded message line in Find.Cuda.<br><br>-- snip --<br>CUDA_NVCC_DEFINITIONS =
=3D=20
gpuReconPlugin_EXPORTS=3Dyes;GPU_RECON=3Dyes;CUDADeviceProperties_DLLExport=
=3Dyes;GPU_RECON=3Dyes;CUDADeviceProperties_DLLExport=3Dyes;CPU_RECON=3Dyes=
<br>
nvcc_flags =3D=20
-m64;-DgpuReconPlugin_EXPORTS=3Dyes;-DGPU_RECON=3Dyes;-DCUDADevicePropertie=
s_DLLExport=3Dyes;-DGPU_RECON=3Dyes;-DCUDADeviceProperties_DLLExport=3Dyes;=
-DCPU_RECON=3Dyes<br>
-- end snip --<br><br>note the use of get_directory property.=A0 Have I men=
tioned to anyone lately why I can&#39;t understand CMake&#39;s (poor)=A0 de=
sign choice in correlating directory structure to target build specificatio=
n. 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 base=
d on the same source using diffrent compiler defined.=A0=A0 I have reached =
a state of boondogglement.<br>
<br><br><br>

--0016e64bb9061281bc048df4e83b--