[Cmake-commits] CMake branch, master, updated. v3.8.1-1060-g17981e0

_VERSION_MINOR 8) -set(CMake_VERSION_PATCH 20170505) +set(CMake_VERSION_PATCH 20170506) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Release flags on one target in debug build type

On 5 May 2017 at 19:45, Konstantin Tokarev wrote: > Hello, > > Is there any clear way to build specific target in "Debug" mode with flags > that it would have in "Release"? > > In particular, build this specific target without effect of > CMAKE_CXX_FLAGS_DEBUG and

Re: [CMake] Release flags on one target in debug build type

05.05.2017, 23:22, "Michael Ellery" : >>  On May 5, 2017, at 11:45 AM, Konstantin Tokarev wrote: >> >>  Hello, >> >>  Is there any clear way to build specific target in "Debug" mode with flags >> that it would have in "Release"? >> >>  In particular,

Re: [CMake] Release flags on one target in debug build type

> On May 5, 2017, at 11:45 AM, Konstantin Tokarev wrote: > > Hello, > > Is there any clear way to build specific target in "Debug" mode with flags > that it would have in "Release"? > > In particular, build this specific target without effect of > CMAKE_CXX_FLAGS_DEBUG

[CMake] Release flags on one target in debug build type

Hello, Is there any clear way to build specific target in "Debug" mode with flags that it would have in "Release"? In particular, build this specific target without effect of CMAKE_CXX_FLAGS_DEBUG and CMAKE_C_FLAGS_DEBUG, while preserving flags added by target_compile_options -- Regards,

Re: [CMake] setting environment variable for ctest

Use the ENVIRONMENT property of your tests (see https://cmake.org/cmake/help/v3.7/prop_test/ENVIRONMENT.html). On 05/05/2017, 16:29, "CMake on behalf of Juan E. Sanchez" wrote: Hello, It appears that when I invoke

Re: [CMake] setting environment variable for ctest

It this possible to set for all tests as one line? This would require changing dozens of tests. Regards, Juan On 5/5/17 9:31 AM, CHEVRIER, Marc wrote: Use the ENVIRONMENT property of your tests (see https://cmake.org/cmake/help/v3.7/prop_test/ENVIRONMENT.html). On 05/05/2017, 16:29,

[CMake] setting environment variable for ctest

Hello, It appears that when I invoke ctest through cmake, the environment variables I export from my bash shell are being ignored: DYLD_INSERT_LIBRARIES PATH Is there a way to tell cmake to pass the user environment all the way down to the environment for my tested application. This is on

[CMake] Does JOB_POOL_[COMPILE|LINK] work with custom_target?

Hi all, We have a bunch of custom_target and a subset of them should be run in sequence. So we tried to define: set_property(GLOBAL PROPERTY JOB_POOLS exclusive=1) and then: set_property(TARGET my_custom_target PROPERTY JOB_POOL_COMPILE exclusive) set_property(TARGET my_custom_target PROPERTY

[Cmake-commits] CMake branch, master, updated. v3.8.1-1059-ge1ae739

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e1ae739e1f4b868dffcb4a08cfacde3680dca3aa (commit) via

Re: [CMake] Circular dependencies with Ninja, not with Unix Makefiles

Well, in my real case this happens even with out-of-source builds, which also occurs in the test case if I change: set (OUT ${CMAKE_BINARY_DIR}/ext) in ext/CMakeLists.txt. Sure, I can avoid it by renaming the file or target, but I thought this is something that could be avoided by either (a)

Re: [CMake] avoiding finding system libraries (motivation is superbuilds)

Have you tried using CMAKE_PREFIX_PATH instead of CMAKE_INSTALL_PREFIX? On Thu, May 4, 2017 at 5:13 PM, Kris Thielemans wrote: > Hi > > > > Short question: if we have a library/include files installed both in the > usual system locations and outside, how do we

Re: [CMake] Circular dependencies with Ninja, not with Unix Makefiles

Hi, This is caused by doing an in source build and thereby causing the issue. The custom command is outputting a file called 'foo', which is also the chosen name of a target in the ninja file. All of this results in ninja conflating the two and causing a circular dependency. Your options are to