Re: [CMake] cmp0065

2016-07-06 Thread David Cole via CMake
Seems like you ought to be able to avoid this warning just by setting ENABLE_EXPORTS to 0 or 1 ... If you're going to require 3.0, then use 3.0. If you're going to use 3.5, then add the property to squelch the warning and get the behavior you want. D On Wednesday, July 6, 2016, J Decker

Re: [CMake] cmp0065

2016-07-06 Thread J Decker
M:/tmp/cmake_cmp0065/CMakeLists.txt(1): cmake_minimum_required(VERSION 3.0 ) M:/tmp/cmake_cmp0065/CMakeLists.txt(2): project(cmake-test ) M:/tmp/cmake_cmp0065/CMakeLists.txt(3): add_executable(myExe main.c ) M:/tmp/cmake_cmp0065/CMakeLists.txt(4): target_compile_definitions(myExe PRIVATE

Re: [CMake] cmp0065

2016-07-06 Thread Johannes Zarl
Hi, On Wednesday 06 July 2016 08:43:44 you wrote: > > #if defined(WIN32) > > #endif > > not WIN32 that way... as in add_executable( something WIN32 ... ) (or not > WIN32) I'm not sure I can follow. I thought you want to have compile time definitions like "-DSOMETHING" for GCC or "/DSOMETHING"

Re: [CMake] cmp0065

2016-07-06 Thread Johannes Zarl-Zierl
Hi, On Tuesday 05 July 2016 23:46:16 J Decker wrote: > https://cmake.org/cmake/help/v3.4/policy/CMP0065.html > while I like the idea it suggests, I don't use the flags for -rdynamic so > this is meaningless to me I'm not sure I understood you correctly, but if the policy is meaningless to you,