[cmake-developers] [CMake 0016034]: Completely wrong FindGettext documentation

2016-03-24 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=16034 == Reported By:Tatsuyuki Ishi Assigned To:

[Cmake-commits] CMake branch, master, updated. v3.5.1-317-g484d7ca

2016-03-24 Thread Kitware Robot
_VERSION_MINOR 5) -set(CMake_VERSION_PATCH 20160324) +set(CMake_VERSION_PATCH 20160325) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, maint, updated. v3.5.1

2016-03-24 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, maint has been updated via 64130a7e793483e24c1d68bdd234f81d5edb2d51 (commit) via

[cmake-developers] [ANNOUNCE] CMake 3.5.1 available for download

2016-03-24 Thread Robert Maynard
We are pleased to announce that CMake 3.5.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.5.1 since 3.5.0: Ben

[CMake] [ANNOUNCE] CMake 3.5.1 available for download

2016-03-24 Thread Robert Maynard
We are pleased to announce that CMake 3.5.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.5.1 since 3.5.0: Ben

[Cmake-commits] CMake annotated tag, v3.5.1, created. v3.5.1

2016-03-24 Thread Robert Maynard
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 annotated tag, v3.5.1 has been created at 22da5dc5346a084bebe512eb43365460d53188ac (tag) tagging

Re: [CMake] Two phase install?

2016-03-24 Thread Scott Aron Bloom
I am not using a dashboard.. What I found is this.. When running a test from a VCXProj system, CMake sets up the custom command as follows Ctest . -C $(Configuration) The $(Configuration) is a visual studio/devenv variable, that is set by the system baed on the current configuration.

Re: [CMake] Cmake 3.5.0 and Fortran submodule cannot be built

2016-03-24 Thread Brad King
On 03/24/2016 03:29 PM, olusegun ogunbade wrote: > [ 33%] Building Fortran object src/CMakeFiles/foo.dir/m_point.f90.o > Error copying Fortran module "mod/procedure". Tried "mod/PROCEDURE.mod" and > "mod/procedure.mod". Thanks for the example. The problem is that the syntax MODULE

Re: [CMake] Two phase install?

2016-03-24 Thread David Cole via CMake
Are you running a dashboard script (ctest -S script) when this happens? Or calling ctest directly with other arguments? If you are running a -S script, you can specify the configuration to build and test in the script itself with the CTEST_CONFIGURATION_TYPE script variable. Read the docs here on

Re: [CMake] Cmake 3.5.0 and Fortran submodule cannot be built

2016-03-24 Thread olusegun ogunbade
Hi All Please find attached a tar file containing the source code. The build process and encountered error are: ogunbog@JesusIsLord:~/work/fortran/point/build$ cmake .. -- The Fortran compiler identification is GNU 6.0.0 -- Check for working Fortran compiler: /home/ogunbog/bin/gfc6u4 --

Re: [CMake] Two phase install?

2016-03-24 Thread Scott Aron Bloom
-Original Message- From: Hendrik Sattler [mailto:p...@hendrik-sattler.de] Sent: Thursday, March 24, 2016 3:54 AM To: Alan W. Irwin; Scott Aron Bloom Cc: cmake@cmake.org Subject: Re: [CMake] Two phase install? Am 24. März 2016 10:14:40 MEZ, schrieb "Alan W. Irwin"

Re: [CMake] Cmake 3.5.0 and Fortran submodule cannot be built

2016-03-24 Thread Damian Rouson
I hope we’ll see CMake support for submodules soon. Submodules are now supported by released versions of the Cray, IBM, and Intel compilers and by the pre-release GNU Fortran compiler version 6.0.0, which is expected to release in mid-April. Damian On Mar 23, 2016, at 1:12 PM, Brad King

[Cmake-commits] CMake branch, release, updated. v3.5.0-17-g64130a7

2016-03-24 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, release has been updated via 64130a7e793483e24c1d68bdd234f81d5edb2d51 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.5.0-333-gb8268fa

2016-03-24 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 b8268facb81be685df9621a7c7337ce256e60ee5 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-667-gfed3934

2016-03-24 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 fed393454c55d27d972862be9f5e2df8c0a35220 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.5.0-16-g277b756

2016-03-24 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, release has been updated via 277b7567f747bbfd8658a395da8eba79a2e01037 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-665-gb190272

2016-03-24 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 b190272c5a65fb4c6d2a61c4d63d429b2bd253b9 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-331-g456d89f

2016-03-24 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 456d89f7244ee985198531815bac0e8110d1d614 (commit) via

Re: [CMake] CMAKE_SIZEOF_VOID_P is unset when building libgit2 on Windows

2016-03-24 Thread Brad King
On 03/24/2016 11:28 AM, Sebastian Schuberth wrote: > Configuring libgit2 fails as CMake does not set CMAKE_SIZEOF_VOID_P > (nor CMAKE_C_SIZEOF_DATA_PTR), see the attached CMakeCCompiler.cmake file. > > I tried to search CMake's source code to find out how the value of > @CMAKE_C_SIZEOF_DATA_PTR@

[CMake] CMAKE_SIZEOF_VOID_P is unset when building libgit2 on Windows

2016-03-24 Thread Sebastian Schuberth
Hi, I'm having a similar problem as mention in the old thread at [1]. In my case, I'm on Windows 8.1 64-bit trying to build the rugged [2] gem, which depends on libgit2, which uses CMake. Configuring libgit2 fails as CMake does not set CMAKE_SIZEOF_VOID_P (nor CMAKE_C_SIZEOF_DATA_PTR), see

[Cmake-commits] CMake branch, next, updated. v3.5.0-663-gefb0839

2016-03-24 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 efb0839989bdcbab047aabe37825d40e328d0ecb (commit) via

Re: [CMake] execute_process seems to execute in parallel and also only shows output of last command

2016-03-24 Thread Nils Gladitz
On 03/24/2016 12:58 PM, xyzdra...@fastmail.fm wrote: The CMake 3.5.0 documentation specifies the execute_process command like this: execute_process(COMMAND [args1...]] [COMMAND [args2...] [...]] [WORKING_DIRECTORY ] [...] )

[Cmake-commits] CMake branch, next, updated. v3.5.0-653-g52485db

2016-03-24 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 52485db76cef8bc24c8f11060234bded6d602060 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-651-gdc16110

2016-03-24 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 dc161109dbca44ee48b4a1b2a7cf1936ffa5aace (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-312-g59f53f7

2016-03-24 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 59f53f7422818f3ccad8518ab0863de6bb7fd293 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-310-g3252e6e

2016-03-24 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 3252e6e0755c04b062d18c574470db72f00ba372 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-321-g917d49e

2016-03-24 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 917d49ed93b7b43ac3508dbd81f0645433880724 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-323-g6d36fc8

2016-03-24 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 6d36fc8341aa7361a5786e78a19d9bab71ee42d2 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-317-g5b2acf6

2016-03-24 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 5b2acf6c1c904df96bd0031c9469e61118da5200 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-645-gefe4b5c

2016-03-24 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 efe4b5ca9b3223a816ebe63a8280cb92cc72ee42 (commit) via

[CMake] add_definitions: if option contains space and using FindCUDA, it won't get added to compiler call

2016-03-24 Thread xyzdragon
Here is a minimal working-example without FindCUDA: main.cpp: int main(void){ return 0; } CMakeLists.txt: cmake_minimum_required(VERSION 3.5) add_definitions( "-D USE_FEATURE" ) add_library( mimi main.cpp ) target_link_libraries( mimi ) the output will be:

[CMake] execute_process seems to execute in parallel and also only shows output of last command

2016-03-24 Thread xyzdragon
I'm using cmake --version cmake version 3.5.0 # First let me tell you, what I wanted to achieve: I wanted to recursively build some submodule, if that makes sense or not should be the matter here: execute_process( COMMAND cmake .. COMMAND make

Re: [CMake] Two phase install?

2016-03-24 Thread Hendrik Sattler
Am 24. März 2016 10:14:40 MEZ, schrieb "Alan W. Irwin" : >On 2016-03-24 03:59- Scott Aron Bloom wrote: > >> That method does NOT work with windows... And since the visual >studio project has the external as a single command, (not sure if its >calling nmake or the

Re: [CMake] Two phase install?

2016-03-24 Thread Alan W. Irwin
On 2016-03-24 03:59- Scott Aron Bloom wrote: That method does NOT work with windows... And since the visual studio project has the external as a single command, (not sure if its calling nmake or the new build cmd) the proeject is not run in parallel. I am pretty sure

Re: [cmake-developers] CPackRPM not dealing correctly with symlinks

2016-03-24 Thread Attila Krasznahorkay
Hi Domen, Unfortunately I can't seem to create an easy-to-package example for the issue. Since it seems that the file given to the install(...) command has to be in a "very different place" than the source or binary directories for the issue to come up. (My guess is that if the file shares

[Cmake-commits] CMake branch, next, updated. v3.5.0-642-g89b6090

2016-03-24 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 89b60904cdd2d27cd9dbeea919b267522524702d (commit) via

Re: [cmake-developers] Patch to only consider build dependencies between files in the source directory

2016-03-24 Thread Attila Krasznahorkay
Hi Brad, Thanks! Looks good. Cheers, Attila > On 23 Mar 2016, at 19:05, Brad King wrote: > > On 03/22/2016 08:23 AM, Attila Krasznahorkay wrote: >> Here is my next attempt. ;-) Hopefully I'm at least getting closer... > > Thanks. Applied with minor tweaks: