[cmake-developers] [CMake 0014640]: PRIVATE linking with target_link_libraries propagates usage requirements for static libraries

2013-12-09 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14640 == Reported By:Arunmozhi Assigned To:

Re: [cmake-developers] Converting cmake_parse_arguments to a builtin command

2013-12-09 Thread Brad King
On 12/06/2013 04:42 PM, Matthew Woehlke wrote: An advantage of keeping the name is that existing callers get the speed-up immediately. Furthermore there will be less code left in the old module to maintain. I think that is still true if the module just wraps the new function? Yes, I think

Re: [cmake-developers] Review Request: Topic ExternalProject-independent-step-targets

2013-12-09 Thread Brad King
On 12/09/2013 07:51 AM, Daniele E. Domenichelli wrote: And then adding an explicit dependency for each project that requires it add_dependency(${proj}-download SetupLocalXXXRepository) ...but again this requires the existing cases to be modified and no longer tests that they work without

Re: [CMake] [CMAKE] Getting compilation date through CMake

2013-12-09 Thread Jon Haitz Legarreta
BTW, just for other newbies, I think my mistake was that I took another external command example literally: EXECUTE_PROCESS( COMMAND svnversion -nc ${sourceDir} OUTPUT_VARIABLE _out_svnversion ) Now I guess the above works (without invoking the command prompt) because a

Re: [CMake] [CMAKE] Getting compilation date through CMake

2013-12-09 Thread Jakub Zakrzewski
Hi, I only wanted to warn you, that windows date command output is locale-specific, so you may get into trouble if you want to use it as anything else than a string literal. From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Jon Haitz Legarreta Sent: Montag, 9.

Re: [CMake] [CMAKE] Getting compilation date through CMake

2013-12-09 Thread Jon Haitz Legarreta
Thanks for the tip Jakub. BTW, I just realized that the [OUTPUT_STRIP_TRAILING_WHITESPACE] option of EXECUTE_PROCESS has the same effect of the regex I wrote to strip the trailing linebreaks. Regards, JON HAITZ On 9 December 2013 09:46, Jakub Zakrzewski jzakrzew...@e2e.ch wrote: Hi, I

[CMake] 32/64 bit flag

2013-12-09 Thread pellegrini
Dear CMakers, I have to build cmake files for a Fortran project using ifort compiler on Windows, linux and macos platform. That project will be linked to Winteracter Fortran library whose installation paths are different depending on the 32 or 64 bit versions. Is there a way to automatically

Re: [CMake] 32/64 bit flag

2013-12-09 Thread Eric Noulard
2013/12/9 pellegrini pellegr...@ill.fr: Dear CMakers, I have to build cmake files for a Fortran project using ifort compiler on Windows, linux and macos platform. That project will be linked to Winteracter Fortran library whose installation paths are different depending on the 32 or 64 bit

Re: [CMake] 32/64 bit flag

2013-12-09 Thread pellegrini
On 12/9/2013 1:26 PM, Eric Noulard wrote: 2013/12/9 pellegrini pellegr...@ill.fr: Dear CMakers, I have to build cmake files for a Fortran project using ifort compiler on Windows, linux and macos platform. That project will be linked to Winteracter Fortran library whose installation paths are

Re: [CMake] 32/64 bit flag

2013-12-09 Thread Eric Noulard
2013/12/9 pellegrini pellegr...@ill.fr: Thanks Eric for the hint. I read some time ago some stuffs about the CMAKE_SIZEOF_VOID_P variable but unfortunately, in the present case, the problem is a bit different. It can be for example that on a 64 bit machine, I would like to use the 32 bit

Re: [CMake] 32/64 bit flag - solved

2013-12-09 Thread pellegrini
On 12/9/2013 2:34 PM, Eric Noulard wrote: 2013/12/9 pellegrini pellegr...@ill.fr: Thanks Eric for the hint. I read some time ago some stuffs about the CMAKE_SIZEOF_VOID_P variable but unfortunately, in the present case, the problem is a bit different. It can be for example that on a 64 bit

[CMake] Proper behaviour and use of CMAKE_INSTALL_* variables

2013-12-09 Thread Mojca Miklavec
Dear list members, I often like or need to install two versions of the same software. Ideally the software should put its files by default to $prefix/include/$NAME/*.h $prefix/lib/$NAME/*.dylib ... ($prefix = $CMAKE_INSTALL_PREFIX) and in order to be able to install multiple versions

Re: [CMake] Proper behaviour and use of CMAKE_INSTALL_* variables

2013-12-09 Thread Andreas Pakulat
Hi, On Mon, Dec 9, 2013 at 3:50 PM, Mojca Miklavec mojca.miklavec.li...@gmail.com wrote: Dear list members, I often like or need to install two versions of the same software. Ideally the software should put its files by default to $prefix/include/$NAME/*.h

Re: [CMake] Proper behaviour and use of CMAKE_INSTALL_* variables

2013-12-09 Thread Mojca Miklavec
On Mon, Dec 9, 2013 at 4:52 PM, Andreas Pakulat wrote: Hi, On Mon, Dec 9, 2013 at 3:50 PM, Mojca Miklavec wrote: Dear list members, I often like or need to install two versions of the same software. Ideally the software should put its files by default to $prefix/include/$NAME/*.h

[CMake] Building Matlab MEX files - a solution?

2013-12-09 Thread Williams, Norman K
I've been working on a project which requires building. After coming up with a brittle, overcomplicated way to use Matlab's MEX script to compile mex files, it occurred to me that I could simplify things by using the output of the MEX script. To that end, I wrote this. It seems to work great on

Re: [CMake] Windows XP + CMake + VS2013

2013-12-09 Thread Andrey Upadyshev
Hi Stefan, You should add CMake command option *-T vc120_xp* BR, Andrey Upadyshev On Sun, Dec 8, 2013 at 7:22 PM, Stefan Fendt ste...@sfendt.de wrote: Hi, I'm using CMake 2.8.12 together with MSVC 2013 and need to produce a binary which is (still) compatible with Windows XP SP3. If I'm

Re: [CMake] How to find/run external host executables when using cross compiling

2013-12-09 Thread Eric Wing
On 12/4/13, Eric Wing ewmail...@gmail.com wrote: I'm currently trying to port a rather large, complex project to Android. It has an existing CMake project so I'm trying to leverage that. I've taken and enhanced one of the Android-CMake toolchains I've found. This particular project I'm

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6113-gebe82f4

2013-12-09 Thread Daniele E . Domenichelli
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 ebe82f456fb79bc321aee307ee24da4b735095f2 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6115-gd85206a

2013-12-09 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 d85206a21fcdeec9995d92530f5c66cf9ffd601b (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6117-gac10554

2013-12-09 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 ac1055496fd2a905bb7b273d4bd44d7587958082 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.1-902-g5026696

2013-12-09 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 5026696fcc79e1ec4b1f40069566614852b4c312 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.1-895-gcedf03b

2013-12-09 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 cedf03b30711a1d93f00eaed0b92dc3538ec660d (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.1-897-g1c95ec6

2013-12-09 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 1c95ec6316e5f8b411abf79dbf5d4c6f85faf2f2 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.1-899-g1ab140e

2013-12-09 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 1ab140ef8f4be77503f59f25d6e2a036d0f44ca2 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.1-904-g330af68

2013-12-09 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 330af68ed4eca375160b31aefd71bd6ea11b586f (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6125-gc32326c

2013-12-09 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 c32326caa94bfe3ae5910270c62740f891201f1f (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6123-g5b66514

2013-12-09 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 5b66514165284f395f6f694b12c4c79b268c2600 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6127-gaa8e2a9

2013-12-09 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 aa8e2a9bd9cd4f227602798f77a8452252f47b7b (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6129-g2d35d00

2013-12-09 Thread Stephen Kelly
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 2d35d005e98784eafb2e530e528e08da3733ec46 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6131-gf3ccb10

2013-12-09 Thread Daniele E . Domenichelli
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 f3ccb10eee8f1ac0ad2d9f88c93d7eddbdf02172 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6133-g4213f09

2013-12-09 Thread Daniele E . Domenichelli
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 4213f09b7f048e906a4eca2f623416533ef3c046 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6135-g77a2987

2013-12-09 Thread Zack Galbreath
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 77a2987069bd75b79eef1b6a611da14c4161dd96 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6137-g8542dd9

2013-12-09 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 8542dd9c468d2ca6171b033e69320f1bd6c0efdd (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.12.1-6139-g675d9d1

2013-12-09 Thread Stephen Kelly
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 675d9d1ae559a4582c3f2759555f4f1368b638ff (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.12.1-905-ga2489ce

2013-12-09 Thread Kitware Robot
Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 8cd4750..ec3aadd 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -2,5 +2,5 @@ set(CMake_VERSION_MAJOR 2) set(CMake_VERSION_MINOR 8) set(CMake_VERSION_PATCH 12) -set(CMake_VERSION_TWEAK 20131209