Re: [CMake] FindCuda compiler flag problems

The issue is that nvcc doesn't accept host compiler flags that are C++ only. It does understand a version of the command directly (-std c++11). There should be a fix for this in TOT. See if you can grab a nightly and test it out. James On Mon, May 11, 2015 at 10:54 AM, Wesley Smith wrote: >

Re: [CMake] Tiny cmake question

On Mon, May 11, 2015 at 3:05 PM, Alexey Petruchik < alexey.petruc...@gmail.com> wrote: > Is it possible to rewrite: > > if (${OPENSSL_FOUND}) > option(USE_OUR_OWN_MD5 "Build using own md5 implementation" OFF) > else() > option(USE_OUR_OWN_MD5 "Build using own md5 implementation" ON) > endif() > >

[CMake] Tiny cmake question

Is it possible to rewrite: if (${OPENSSL_FOUND}) option(USE_OUR_OWN_MD5 "Build using own md5 implementation" OFF) else() option(USE_OUR_OWN_MD5 "Build using own md5 implementation" ON) endif() in one line? Something like: option(USE_OUR_OWN_MD5 "Build using own md5 implementation" NOT OPENSSL_FO

Re: [CMake] install/strip target doesn't exist?

yes. running strip on DLLs can take a 24k dll and make it 10k. https://drive.google.com/folderview?id=0B812EYiKwtkkfkc5bDI1RUZOaEtyV1VicUpva0Nkd09pN2V2YjFCODdNajRYNWRWZ2psZkE It has a lot of extra data even building with CMAKE_BUILD_TYPE=release On Mon, May 11, 2015 at 10:36 AM, Hendrik Sattl

Re: [CMake] install/strip target doesn't exist?

Am 11. Mai 2015 18:46:13 MESZ, schrieb J Decker : >command: > cmake.exe --build . --config "release" --target "install/strip" -- >output: > mingw32-make.exe: *** No rule to make target 'install\strip'. Stop. > >It reverses the slash? >install doesn't always strip? >does package strip? Is ther

[CMake] FindCuda compiler flag problems

Hi, I'm trying to compile w/ CUDA on Centos6 using Cuda7 and C++11. When I have host propagate flags on, the CXX flags get mangles with escapes like this: ,\"-fPIE\",\"--std=c++11\",\"-DGLM_FORCE_RADIANS\",\"-g\" which causes a ton of errors. If I turn host propagate flags off, I then have to

[CMake] install/strip target doesn't exist?

command: cmake.exe --build . --config "release" --target "install/strip" -- output: mingw32-make.exe: *** No rule to make target 'install\strip'. Stop. It reverses the slash? install doesn't always strip? does package strip? -- Powered by www.kitware.com Please keep messages on-topic and c

Re: [CMake] Switching configuration to icc

I am very much thankful Cole, Gobbi, Wherry and Tom for your valuable suggestions. It worked like a charm with the following syntax: [Inside Build Directory] > env CC=icc CXX=icpc ccmake [path-to-source-directory] -Wno-dev -- Sincerely Rahul Kumar Soni

Re: [CMake] CHECK_C_SOURCE_COMPILES and include_directories

* Rolf Eike Beer: >> > CMAKE_REQUIRED_INCLUDES = list of include directories >> >> I saw that, but I thought this happens behind the scenes. Do I have >> to set this variable in addition to the include_directories directive? > > Yes, include_directories() only affects target, i.e. add_executabl