[cmake-developers] [CMake 0015113]: TARGET_BASE is generated wrong in case of up-leading path

2014-08-27 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15113 == Reported By:raspy Assigned To:

Re: [cmake-developers] [PATCH] New module: FindIce.cmake

2014-08-27 Thread Roger Leigh
On Fri, Aug 22, 2014 at 11:17:05AM +0100, Roger Leigh wrote: On Thu, Aug 21, 2014 at 02:47:24PM +0200, Rolf Eike Beer wrote: Roger Leigh wrote: On Sun, Aug 17, 2014 at 05:22:38PM +0100, Roger Leigh wrote: On Sun, Aug 17, 2014 at 05:50:58PM +0200, Rolf Eike Beer wrote: Am Sonntag,

Re: [CMake] Need to know the ASM flag that needs to be modified in cmake

2014-08-27 Thread Petr Kmoch
Hi Ravi, I've never used ASM_MASM (or any other language beside C, CXX and Fortran), but if it follows normal CMake language rules, the following variables should exist: CMAKE_ASM_MASM_FLAGS CMAKE_ASM_MASM_FLAGS_CONFIG (where CONFIG is a placeholder for uppercase configuration name). See the

Re: [CMake] Global dependency

2014-08-27 Thread Petr Kmoch
Hi Jonas. As a hacky solution, you could override add_library() and add_executable(), like this: function(add_library targetName) _add_library(${targetName} ${ARGN}) add_dependencies(${targetName} BuildInfoDateTime) endfunction() Petr On Wed, Aug 27, 2014 at 5:44 AM, Jonas Lippuner

Re: [CMake] Global dependency

2014-08-27 Thread Jonas Lippuner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Petr, Thanks! This works. Best, Jonas - Original Message Subject: Re: [CMake] Global dependency From: Petr Kmoch petr.km...@gmail.com To: Jonas Lippuner jo...@lippuner.ca CC: cmake@cmake.org cmake@cmake.org Date: Tue 26 Aug

[CMake] compilation order dependencies,

2014-08-27 Thread Łukasz Tasz
Dear experts, I hit the wall again with order of compilation in generated Makefiles, Uscase: add_library(foo ${foosources}) add_library(bar ${barsources}) add_library... ... ... add_executable(foo_exe main.cpp) target_link_libraries(foo_exe foo bar ... ... ...) while libs objects will be

Re: [CMake] compilation order dependencies,

2014-08-27 Thread Petr Kmoch
Hi Lukasz. I believe you could put `main.cpp` into an object library: add_library(foo ${foosources}) add_library(bar ${barsources}) add_library... ... ... add_library(main_sources OBJECT main.cpp) add_executable(foo_exe $TARGET_OBJECTS:main_sources) target_link_libraries(foo_exe foo bar ... ...

Re: [CMake] Need to know the ASM flag that needs to be modified in cmake

2014-08-27 Thread Ravi Raman
Hi, Thanks Petr for your comments. We had already tried this approach. But it did not work. We set the option “/D _WIN64” in CMAKE_ASM_MASM_FLAGS but it has no impact on the execution of ml64.exe. ml64.exe execution always shows only the following options i.e. does not include “/D _WIN64”.

[CMake] Fail target if buildtype is not RelWithDebInfo

2014-08-27 Thread Thomas Sondergaard
Hi, I have a custom target that is only enabled on Windows and it only works with buildtype RelWithDebInfo. When a developer accidentally runs it under a different configuration it doesn't fail in a very obvious way, and I'd like to improve that, if possible. I am using the Visual Studio 12

Re: [CMake] Fail target if buildtype is not RelWithDebInfo

2014-08-27 Thread Petr Kmoch
Hi Thomas, you should be able to make this work using the variable CMAKE_CFG_INTDIR: if (WIN32) add_custom_target(msi-installer COMMAND IF NOT ${CMAKE_CFG_INTDIR} == RELWITHDEBINFO (echo msi-installer only works for build type RELWITHDEBINFO exit 1) COMMAND ...) endif() Petr On

Re: [CMake] Fail target if buildtype is not RelWithDebInfo

2014-08-27 Thread Thomas Sondergaard
Thanks Petr, It works. I ended up having to make it slightly more complicated to also work with the Ninja generator, but CMAKE_CFG_INTDIR was exactly what I was looking for. Thanks, Thomas On 2014-08-27 13:48, Petr Kmoch wrote: Hi Thomas, you should be able to make this work using the

[CMake] CMake hangs

2014-08-27 Thread Phil Smith
For a long time, we've been stuck on CMake 2.8 because later versions silently hang for us. This is doing in-source builds, which I know are considered Evil, but we can't move off them yet. We had another problem (see my earlier posts with Subject: Dependency weirdness) that turned out to be

[CMake] linking with libstdc++ statically

2014-08-27 Thread victor.zverov...@gmail.com
Hello, I am trying to link an application with libstdc++ statically on Linux and OS X. The first attempt was to add -static-libstdc++ to CMAKE_EXE_LINKER_FLAGS: set(CMAKE_EXE_LINKER_FLAGS ${CMAKE_EXE_LINKER_FLAGS} -static-libstdc++) This works on Linux with GCC, but Clang gives the following

[Cmake-commits] CMake branch, next, updated. v3.0.1-5037-g79e24c9

2014-08-27 Thread Nils Gladitz
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, next has been updated via 79e24c9ca3cf87a9302463517aa1728f3191e9ae (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5039-g2ca60fe

2014-08-27 Thread Nils Gladitz
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, next has been updated via 2ca60fe320a698b12b43cfa9f1fca565f072a2f2 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5041-g250c4d4

2014-08-27 Thread Chuck Atkins
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, next has been updated via 250c4d44680295e0210dd78b20bb093f1771ffb6 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.1-1761-g869e1a4

2014-08-27 Thread Brad King
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 869e1a4618db925e3c06746dfaba43241435d129 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.1-1763-g3d95b39

2014-08-27 Thread Brad King
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 3d95b3979782b05a2227bd3aa081667b100bd30d (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5046-gf35fb48

2014-08-27 Thread Brad King
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, next has been updated via f35fb48df07d557ffe883962cf8c56458e583d96 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5048-gcd0500a

2014-08-27 Thread Nils Gladitz
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, next has been updated via cd0500a9b401ce035f8f711f0bdef54de3d9ca06 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5050-g42d0d44

2014-08-27 Thread Nils Gladitz
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, next has been updated via 42d0d445199bd735a39d7b86fa1e6375ad17bbe0 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5052-g9481827

2014-08-27 Thread Brad King
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, next has been updated via 948182700bccec42f8c68251df75e4cadcc663a4 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5054-g1d3660f

2014-08-27 Thread Brad King
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, next has been updated via 1d3660f1e5a4447dabea31cc05a0d02e7dc64f22 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5056-g8219c2a

2014-08-27 Thread Nils Gladitz
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, next has been updated via 8219c2a9733dd9dba58b26e6e362fa3fd043bc59 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5058-g98f6998

2014-08-27 Thread Nils Gladitz
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, next has been updated via 98f69986160c9fd2788403e045b97c31d201d7b2 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.1-5060-ge210e5a

2014-08-27 Thread Brad King
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, next has been updated via e210e5ac17af28e1066f155851a280d893c4eee1 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.1-1764-g8785d05

2014-08-27 Thread Kitware Robot
20140827) +set(CMake_VERSION_PATCH 20140828) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake