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

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16034 
== 
Reported By:Tatsuyuki Ishi
Assigned To:
== 
Project:CMake
Issue ID:   16034
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   high
Status: new
== 
Date Submitted: 2016-03-25 00:42 EDT
Last Modified:  2016-03-25 00:42 EDT
== 
Summary:Completely wrong FindGettext documentation
Description: 
I found out that FindGettext module's document is not only confusing but
completely wrong.

The documentation says:
# GETTEXT_CREATE_TRANSLATIONS ( outputFile [ALL] file1 ...  fileN )
#
# ::
#
# This will create a target "translations" which will convert the
# given input po files into the binary output mo file. If the
# ALL option is used, the translations will also be created when
# building the default target.

What it does:
Process given po files, one by one, expected usage is one po per language.
The outputFile parameter is actually for the gettext package name, internal
codes expects package.pot passed.
And also it implicitly creates install target, without any description.

Other functions' documentation are also confusing, I hope you rewrite these.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-25 00:42 Tatsuyuki Ishi New Issue
==

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

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

[Kitware Robot]

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  484d7ca0e0660f3a5573e83c917f8a7dc6c4e183 (commit)
  from  b8268facb81be685df9621a7c7337ce256e60ee5 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=484d7ca0e0660f3a5573e83c917f8a7dc6c4e183
commit 484d7ca0e0660f3a5573e83c917f8a7dc6c4e183
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Fri Mar 25 00:01:06 2016 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Fri Mar 25 00:01:06 2016 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 37e2b54..2377831 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_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/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  277b7567f747bbfd8658a395da8eba79a2e01037 (commit)
   via  c61040282557ba268e144ffa5e2d1935b5991d8d (commit)
   via  f77ad2c736061718c870dc09255efd9dea259d0d (commit)
   via  72a97b7a761b46fd1668e3ae81dd9322972f4cb3 (commit)
   via  2c3b8a1cd801a8c3c5331d8345bf8ed6d9e38595 (commit)
   via  6f4f90548353d9e329bd4ddb2f7492788f28f0e1 (commit)
   via  d9857c84574a8bd5c2d6739580fa98b6b2f8cefc (commit)
   via  d84ba668d7dd77ac38b3795f92e4ef0f894c696e (commit)
   via  1b034123e77ce50d618eeaa7cf800f7303dccb51 (commit)
   via  7b990e82c523772e8e40911812e6f896c0529e84 (commit)
   via  15a5653ea6cfc3b26634d3a5cea483e5a9ddd97a (commit)
   via  c718070c0887e1c429d6ae4b717c006236c32736 (commit)
   via  4ea249a387e808fa3d6c1f4648df7e094cf0d8a7 (commit)
   via  e3fc2899c89fb075a695d6140eaadf11db85d96c (commit)
   via  44bbd2a65c0d2a405b70b96c3d643ce4b5eb82f4 (commit)
   via  e2f387fabbf6af8665b88b8933ef5ed5cb59 (commit)
  from  b369959eb55dbea601315530185cb480c922cc77 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Modules/CMakeIOSInstallCombined.cmake  |   12 +-
 Modules/FindBoost.cmake|   14 +--
 Modules/FindCUDA.cmake |7 +-
 Modules/FindPkgConfig.cmake|2 +-
 Source/CMakeLists.txt  |   15 +++-
 Source/CMakeVersion.cmake  |2 +-
 Source/CPack/cmCPackDragNDropGenerator.cxx |   25 +---
 Source/QtDialog/CMakeLists.txt |1 +
 Source/cmMakefile.cxx  |   23 +++---
 Source/cmVariableWatch.cxx |4 +++-
 Source/cmVariableWatch.h   |2 +-
 .../FindPkgConfig_cache_variables.cmake|   11 +
 Tests/RunCMake/XcodeProject/RunCMakeTest.cmake |   20 
 ...OSInstallCombinedSingleArch-install-check.cmake |   25 
 .../XcodeIOSInstallCombinedSingleArch.cmake|   19 +++
 15 files changed, 146 insertions(+), 36 deletions(-)
 create mode 100644 
Tests/RunCMake/XcodeProject/XcodeIOSInstallCombinedSingleArch-install-check.cmake
 create mode 100644 
Tests/RunCMake/XcodeProject/XcodeIOSInstallCombinedSingleArch.cmake


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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 Boeckel (1):
  FindPkgConfig: set correctly named variables in cache (#15903)

Brad King (4):
  cmake-gui: Populate CFBundleIdentifier in our Info.plist file (#16023)
  CPack: Avoid using OS X CoreServices if compiler fails on header (#16021)
  FindCUDA: Fix regression in separate compilation (#16027)
  CMake 3.5.1

Roger Leigh (1):
  FindBoost: Tolerate missing indirect dependencies (#16013)

Ruslan Baratov (1):
  Fix iOS combined feature for single architecture targets

Sean McBride (1):
  CPack: Avoid requiring Carbon framework on OS X (#16021)

Yves Frederix (1):
  Avoid occasional use-after-free when a variable watch is executed
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[CMake] [ANNOUNCE] CMake 3.5.1 available for download

[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 Boeckel (1):
  FindPkgConfig: set correctly named variables in cache (#15903)

Brad King (4):
  cmake-gui: Populate CFBundleIdentifier in our Info.plist file (#16023)
  CPack: Avoid using OS X CoreServices if compiler fails on header (#16021)
  FindCUDA: Fix regression in separate compilation (#16027)
  CMake 3.5.1

Roger Leigh (1):
  FindBoost: Tolerate missing indirect dependencies (#16013)

Ruslan Baratov (1):
  Fix iOS combined feature for single architecture targets

Sean McBride (1):
  CPack: Avoid requiring Carbon framework on OS X (#16021)

Yves Frederix (1):
  Avoid occasional use-after-free when a variable watch is executed
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

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

[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  64130a7e793483e24c1d68bdd234f81d5edb2d51 (commit)
  replaces  v3.5.0
 tagged by  Brad King
on  Thu Mar 24 12:42:14 2016 -0400

- Log -
CMake 3.5.1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAABAgAGBQJW9BjmAAoJEC0s7xA0khaE7qgP/26J6KhQcLaxc010HuFZOPwz
EDJTGSBRdfisUdXDBKWdHMJ1LmFWAICbCzMvHsdGwICeRS9LeRlNyQ8RN2u/Wi9h
NFC2DgNSfT3/Sk1ZoKk7/hSSqgnnYZp86J4f+2Xo1ArgBVJI52EpsIw0uyoviZyh
0bOrJ3Jpe9I9pQNyXHliO0GSQwvPCB1U1y85z9M/60IuMLFuozE0j9XLTDzVUEud
Ow4wz/va4/N51b2rkQM42+m5nRQ1Hy5xhVCo10n+snwj/ZR51laxBbLqWZAzqs3c
y50+p4cDRSzAXRGcBdJhzm3ndDs8hFSCjbB2uUva4vcDVgqrichKFzOkMZNtbSy+
pRfuBqdV4k+B2qHIFTMU9h4Q5pSHveHaF/RyBMJBbbApiCxzsguA67SWcM6o792X
HS1BQEkxj9OFECSEnOF03+A3rVU5tO0qsKgnw0iXlBiIIZ0xOBVkGAx0/9Ew1nWV
pNY8VLGBIDOoX+w2/0h4lHiLu0TIRoXRVxb9ngwIv8oWjUc4SAAbMiWbVJGfAnws
xkTty+/8vRIWsedJP+deIl2kXGvUus8W7qufS6VIyK22vb1L16uqD4IzPEU++p7V
m3VdjAN4y+8ZwnQbi8lKQkSOnDy/21vIA2ZZ0FuRwjYGtUBUFFFXev7JyW3RPCy5
qx3fzuFq78LFKEvy+I3j
=icPY
-END PGP SIGNATURE-

Ben Boeckel (1):
  FindPkgConfig: set correctly named variables in cache (#15903)

Brad King (12):
  Merge branch 'FindBoost-optional-indirect-depends' into release
  Merge branch 'ios-install-combined-one-arch' into release
  Merge branch 'cpack-osx-no-carbon' into release
  cmake-gui: Populate CFBundleIdentifier in our Info.plist file (#16023)
  Merge branch 'cmake-gui-osx-identifier' into release
  CPack: Avoid using OS X CoreServices if compiler fails on header (#16021)
  Merge branch 'cpack-osx-optional-CoreServices' into release
  Merge branch 'fix-repeat-pkg-config' into release
  FindCUDA: Fix regression in separate compilation (#16027)
  Merge branch 'FindCUDA-verbatim' into release
  Merge branch 'fix-variable_watch-reallocation' into release
  CMake 3.5.1

Roger Leigh (1):
  FindBoost: Tolerate missing indirect dependencies (#16013)

Ruslan Baratov (1):
  Fix iOS combined feature for single architecture targets

Sean McBride (1):
  CPack: Avoid requiring Carbon framework on OS X (#16021)

Yves Frederix (1):
  Avoid occasional use-after-free when a variable watch is executed

---


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [CMake] Two phase install?

[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.

However, when running cmake via a "super project" to a "subordinate external 
project" (sorry if my nomenclature is wrong), it runs without the -C option.

Using a custom TEST_COMMAND doesn’t help in the ExternalProject_Add command, 
because for windows VS multi-config setups, the current configuration isn’t 
known as a CMAKE variable at the proper time

So I descided to just "hard code" it in, like you suggested.
Scott

-Original Message-
From: David Cole [mailto:dlrd...@aol.com] 
Sent: Thursday, March 24, 2016 12:30 PM
To: Scott Aron Bloom
Cc: Hendrik Sattler; Alan W. Irwin; cmake@cmake.org
Subject: Re: [CMake] Two phase install?

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 the ctest_build and ctest_test
steps: https://cmake.org/cmake/help/v3.5/manual/ctest.1.html#ctest-build-step

The ctest_build command also takes a "CONFIGURATION" argument directly, but 
surprisingly, the ctest_test command does not seem to have that arg. 
https://cmake.org/cmake/help/v3.5/command/ctest_build.html
and https://cmake.org/cmake/help/v3.5/command/ctest_test.html

If you're not calling a -S script, I'm not sure how else you can do it besides 
passing "-C Release" on the command line...


HTH,
David C.



On Thu, Mar 24, 2016 at 2:09 PM, Scott Aron Bloom  wrote:
>
>
> -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" 
> :
>>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 ExternalProject_Add only works with generators 
>>associated with build commands you can run from the command line such 
>>as make, nmake, jom, ninja, etc..  So, for MSVC the way you arrange 
>>that is avoid all the visual studio generators, and instead use one of 
>>"NMake Makefiles", "NMake Makefiles JOM", or "Ninja".
>
> No. Just as with cmake-generated solutions, you can build those on the 
> command line using msbuild or devenv, the one used by cmake depends on the 
> cmake version. You can even use cmake itself to trigger the right build 
> command for those. Parallel building must be enabled by hand when using 
> msbuild. For devenv, the setting from the IDE is used.
>
> HS
> 
>
> The final hurdle Im hitting.  When ctest is run, on windows I get the 
> complaint that the configuration is not set.
>
> Is there any way to set the -C option to ctest?
>
> Scott
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

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

[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 PROCEDURE point_dist

tricks CMake into parsing "MODULE PROCEDURE" as if it were
a declaration of a module called "procedure".  Unfortunately
this is not just a matter of excluding that name because it
also appears to be valid to really define a module named
"procedure".

I still need to look into this further to determine how to
fix it.  CMake's approximate Fortran parser will need to be
updated to account for submodule syntax.

-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Two phase install?

[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 the ctest_build and ctest_test
steps: https://cmake.org/cmake/help/v3.5/manual/ctest.1.html#ctest-build-step

The ctest_build command also takes a "CONFIGURATION" argument
directly, but surprisingly, the ctest_test command does not seem to
have that arg. https://cmake.org/cmake/help/v3.5/command/ctest_build.html
and https://cmake.org/cmake/help/v3.5/command/ctest_test.html

If you're not calling a -S script, I'm not sure how else you can do it
besides passing "-C Release" on the command line...


HTH,
David C.



On Thu, Mar 24, 2016 at 2:09 PM, Scott Aron Bloom  wrote:
>
>
> -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" 
> :
>>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 ExternalProject_Add only works with generators
>>associated with build commands you can run from the command line such
>>as make, nmake, jom, ninja, etc..  So, for MSVC the way you arrange
>>that is avoid all the visual studio generators, and instead use one of
>>"NMake Makefiles", "NMake Makefiles JOM", or "Ninja".
>
> No. Just as with cmake-generated solutions, you can build those on the 
> command line using msbuild or devenv, the one used by cmake depends on the 
> cmake version. You can even use cmake itself to trigger the right build 
> command for those. Parallel building must be enabled by hand when using 
> msbuild. For devenv, the setting from the IDE is used.
>
> HS
> 
>
> The final hurdle Im hitting.  When ctest is run, on windows I get the 
> complaint that the configuration is not set.
>
> Is there any way to set the -C option to ctest?
>
> Scott
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

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

[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 
-- Check for working Fortran compiler: /home/ogunbog/bin/gfc6u4  -- works 
-- Detecting Fortran compiler ABI info 
-- Detecting Fortran compiler ABI info - done 
-- Checking whether /home/ogunbog/bin/gfc6u4 supports Fortran 90 
-- Checking whether /home/ogunbog/bin/gfc6u4 supports Fortran 90 -- yes 
-- Configuring done 
-- Generating done 
-- Build files have been written to: /home/ogunbog/work/fortran/point/build 
ogunbog@JesusIsLord:~/work/fortran/point/build$ l 
CMakeCache.txt  CMakeFiles/  cmake_install.cmake  Makefile  mod/  src/ 
ogunbog@JesusIsLord:~/work/fortran/point/build$ l mod/ 
ogunbog@JesusIsLord:~/work/fortran/point/build$ make 
Scanning dependencies of target foo 
[ 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". 
make[2]: *** [src/CMakeFiles/foo.dir/m_point.f90.o.provides.build] Error 1 
make[1]: *** [src/CMakeFiles/foo.dir/all] Error 2 
make: *** [all] Error 2 
ogunbog@JesusIsLord:~/work/fortran/point/build$ l mod/ 
m_point.mod  m_point@point_a.smod  m_point.smod 



A major benefit of submodules is that if a change is made to one, only it and 
its descendants are affected. Thus, it avoid unnecessary recompilation cascades.

Regards
Prince

===
Prince Olusegun G. Ogunbade
School Address  Postal Address
Dept. of Physics P O Box 
11646
University of Pretoria The Tramshed
Pretoria 0002Pretoria 
0126
Republic of South Africa Republic of 
South Africa

Telephone:

+27 (0)12 420 3114 (School)
+27 (0)74 539 7920 (Mobile)

E-mail:

pogo...@hotmail.com
pogo...@tuks.co.za
jilf...@yahoo.com


From: Brad King 
Sent: Wednesday, March 23, 2016 10:12 PM
To: olusegun ogunbade
Cc: Arjen Markus; cmake@cmake.org
Subject: Re: [CMake] Cmake 3.5.0 and Fortran submodule cannot be built

On 03/23/2016 11:41 AM, Arjen Markus wrote:
> Fortran submodules are contained in a file with the extension
> .smod instead of .mod. At least for Intel Fortran. It may very
> well be that this feature is not yet supported by CMake.
[snip]
>> Error copying Fortran module "mod/function".
>> Tried "mod/FUNCTION.mod" and "mod/function.mod".
>>
>> Does recent cmake support Fortran submodule?

CMake has not been taught about Fortran submodules.  I'm not
very familiar with them either.

Do submodules affect the order in which sources need to be
compiled as modules do?

Please provide a small example project demonstrating use of
submodules and showing the error above.

Thanks,
-Brad



point.tar
Description: point.tar
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Two phase install?

[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" 
:
>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 ExternalProject_Add only works with generators 
>associated with build commands you can run from the command line such 
>as make, nmake, jom, ninja, etc..  So, for MSVC the way you arrange 
>that is avoid all the visual studio generators, and instead use one of 
>"NMake Makefiles", "NMake Makefiles JOM", or "Ninja".

No. Just as with cmake-generated solutions, you can build those on the command 
line using msbuild or devenv, the one used by cmake depends on the cmake 
version. You can even use cmake itself to trigger the right build command for 
those. Parallel building must be enabled by hand when using msbuild. For 
devenv, the setting from the IDE is used.

HS


The final hurdle Im hitting.  When ctest is run, on windows I get the complaint 
that the configuration is not set.

Is there any way to set the -C option to ctest?

Scott
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

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

[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  wrote:
> 
> On 03/23/2016 11:41 AM, Arjen Markus wrote:
>> Fortran submodules are contained in a file with the extension
>> .smod instead of .mod. At least for Intel Fortran. It may very
>> well be that this feature is not yet supported by CMake.
> [snip]
>>> Error copying Fortran module "mod/function".
>>> Tried "mod/FUNCTION.mod" and "mod/function.mod".
>>> 
>>> Does recent cmake support Fortran submodule?
> 
> CMake has not been taught about Fortran submodules.  I'm not
> very familiar with them either.
> 
> Do submodules affect the order in which sources need to be
> compiled as modules do?
> 
> Please provide a small example project demonstrating use of
> submodules and showing the error above.
> 
> Thanks,
> -Brad
> 
> -- 
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake


Damian Rouson, Ph.D., P.E.
President, Sourcery Institute
http://www.sourceryinstitute.org
+1-510-600-2992 (mobile)

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

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

[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  277b7567f747bbfd8658a395da8eba79a2e01037 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  64130a7e793483e24c1d68bdd234f81d5edb2d51 (commit)
  from  456d89f7244ee985198531815bac0e8110d1d614 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  b8268facb81be685df9621a7c7337ce256e60ee5 (commit)
  from  b190272c5a65fb4c6d2a61c4d63d429b2bd253b9 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fed393454c55d27d972862be9f5e2df8c0a35220
commit fed393454c55d27d972862be9f5e2df8c0a35220
Merge: b190272 b8268fa
Author: Brad King 
AuthorDate: Thu Mar 24 12:43:10 2016 -0400
Commit: Brad King 
CommitDate: Thu Mar 24 12:43:10 2016 -0400

Merge branch 'master' into next


---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  c61040282557ba268e144ffa5e2d1935b5991d8d (commit)
   via  f77ad2c736061718c870dc09255efd9dea259d0d (commit)
   via  72a97b7a761b46fd1668e3ae81dd9322972f4cb3 (commit)
   via  2c3b8a1cd801a8c3c5331d8345bf8ed6d9e38595 (commit)
   via  6f4f90548353d9e329bd4ddb2f7492788f28f0e1 (commit)
   via  d9857c84574a8bd5c2d6739580fa98b6b2f8cefc (commit)
   via  d84ba668d7dd77ac38b3795f92e4ef0f894c696e (commit)
   via  1b034123e77ce50d618eeaa7cf800f7303dccb51 (commit)
   via  7b990e82c523772e8e40911812e6f896c0529e84 (commit)
   via  15a5653ea6cfc3b26634d3a5cea483e5a9ddd97a (commit)
   via  c718070c0887e1c429d6ae4b717c006236c32736 (commit)
   via  4ea249a387e808fa3d6c1f4648df7e094cf0d8a7 (commit)
   via  e3fc2899c89fb075a695d6140eaadf11db85d96c (commit)
  from  44bbd2a65c0d2a405b70b96c3d643ce4b5eb82f4 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Modules/CMakeIOSInstallCombined.cmake  |   12 +-
 Modules/FindCUDA.cmake |7 +-
 Modules/FindPkgConfig.cmake|2 +-
 Source/CMakeLists.txt  |   15 +++-
 Source/CPack/cmCPackDragNDropGenerator.cxx |   25 +---
 Source/QtDialog/CMakeLists.txt |1 +
 Source/cmMakefile.cxx  |   23 +++---
 Source/cmVariableWatch.cxx |4 +++-
 Source/cmVariableWatch.h   |2 +-
 .../FindPkgConfig_cache_variables.cmake|   11 +
 Tests/RunCMake/XcodeProject/RunCMakeTest.cmake |   20 
 ...OSInstallCombinedSingleArch-install-check.cmake |   25 
 .../XcodeIOSInstallCombinedSingleArch.cmake|   19 +++
 13 files changed, 133 insertions(+), 33 deletions(-)
 create mode 100644 
Tests/RunCMake/XcodeProject/XcodeIOSInstallCombinedSingleArch-install-check.cmake
 create mode 100644 
Tests/RunCMake/XcodeProject/XcodeIOSInstallCombinedSingleArch.cmake


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  456d89f7244ee985198531815bac0e8110d1d614 (commit)
  from  efb0839989bdcbab047aabe37825d40e328d0ecb (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b190272c5a65fb4c6d2a61c4d63d429b2bd253b9
commit b190272c5a65fb4c6d2a61c4d63d429b2bd253b9
Merge: efb0839 456d89f
Author: Brad King 
AuthorDate: Thu Mar 24 12:40:14 2016 -0400
Commit: Brad King 
CommitDate: Thu Mar 24 12:40:14 2016 -0400

Merge branch 'master' into next


---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  277b7567f747bbfd8658a395da8eba79a2e01037 (commit)
   via  f77ad2c736061718c870dc09255efd9dea259d0d (commit)
   via  2c3b8a1cd801a8c3c5331d8345bf8ed6d9e38595 (commit)
   via  d9857c84574a8bd5c2d6739580fa98b6b2f8cefc (commit)
   via  1b034123e77ce50d618eeaa7cf800f7303dccb51 (commit)
   via  15a5653ea6cfc3b26634d3a5cea483e5a9ddd97a (commit)
   via  4ea249a387e808fa3d6c1f4648df7e094cf0d8a7 (commit)
  from  6d36fc8341aa7361a5786e78a19d9bab71ee42d2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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@ is determined in CMakeCCompiler.cmake.in,
> but I failed. Does anyone have suggestions on how to debug this further,
> or what the possible root causes might be?

It is supposed to be done here:

 
https://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CMakeDetermineCompilerABI.cmake;hb=v3.5.0#l23
 
https://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CMakeCCompilerABI.c;hb=v3.5.0

The try_compile produces a binary file that encodes strings with the
information.  Then we use file(STRINGS) to parse the strings right out
of the binary.  The INFO:sizeof_dptr[...] string contains the size of
data pointer types.

Check CMakeFiles/CMake{Output,Error}.log to see if anything went wrong
with that step that was logged.  Otherwise you can add debugging code.

-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[CMake] CMAKE_SIZEOF_VOID_P is unset when building libgit2 on Windows

[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 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@ is determined in CMakeCCompiler.cmake.in, but I 
failed. Does anyone have suggestions on how to debug this further, or what the 
possible root causes might be?

Versions I'm using:
cmake version 3.5.0
ruby 2.2.3p173 (2015-08-18 revision 51636) [x64-mingw32]
rugged-0.24.0
Ruby-DevKit

[1] 
http://cmake.3232098.n2.nabble.com/Properly-Detecting-Win64-tp5932689p6288785.html
[2] https://github.com/libgit2/rugged
[3] https://github.com/libgit2/libgit2

Regards,
Sebastian
set(CMAKE_C_COMPILER "C:/Ruby-DevKit/mingw/bin/gcc.exe")
set(CMAKE_C_COMPILER_ARG1 "")
set(CMAKE_C_COMPILER_ID "GNU")
set(CMAKE_C_COMPILER_VERSION "4.7.2")
set(CMAKE_C_COMPILER_WRAPPER "")
set(CMAKE_C_STANDARD_COMPUTED_DEFAULT "90")
set(CMAKE_C_COMPILE_FEATURES 
"c_function_prototypes;c_restrict;c_variadic_macros;c_static_assert")
set(CMAKE_C90_COMPILE_FEATURES "c_function_prototypes")
set(CMAKE_C99_COMPILE_FEATURES "c_restrict;c_variadic_macros")
set(CMAKE_C11_COMPILE_FEATURES "c_static_assert")

set(CMAKE_C_PLATFORM_ID "MinGW")
set(CMAKE_C_SIMULATE_ID "")
set(CMAKE_C_SIMULATE_VERSION "")

set(CMAKE_AR "C:/Ruby-DevKit/mingw/bin/ar.exe")
set(CMAKE_RANLIB "C:/Ruby-DevKit/mingw/bin/ranlib.exe")
set(CMAKE_LINKER "C:/Ruby-DevKit/mingw/bin/ld.exe")
set(CMAKE_COMPILER_IS_GNUCC 1)
set(CMAKE_C_COMPILER_LOADED 1)
set(CMAKE_C_COMPILER_WORKS TRUE)
set(CMAKE_C_ABI_COMPILED FALSE)
set(CMAKE_COMPILER_IS_MINGW 1)
set(CMAKE_COMPILER_IS_CYGWIN )
if(CMAKE_COMPILER_IS_CYGWIN)
  set(CYGWIN 1)
  set(UNIX 1)
endif()

set(CMAKE_C_COMPILER_ENV_VAR "CC")

if(CMAKE_COMPILER_IS_MINGW)
  set(MINGW 1)
endif()
set(CMAKE_C_COMPILER_ID_RUN 1)
set(CMAKE_C_SOURCE_FILE_EXTENSIONS c;m)
set(CMAKE_C_IGNORE_EXTENSIONS h;H;o;O;obj;OBJ;def;DEF;rc;RC)
set(CMAKE_C_LINKER_PREFERENCE 10)

# Save compiler ABI information.
set(CMAKE_C_SIZEOF_DATA_PTR "")
set(CMAKE_C_COMPILER_ABI "")
set(CMAKE_C_LIBRARY_ARCHITECTURE "")

if(CMAKE_C_SIZEOF_DATA_PTR)
  set(CMAKE_SIZEOF_VOID_P "${CMAKE_C_SIZEOF_DATA_PTR}")
endif()

if(CMAKE_C_COMPILER_ABI)
  set(CMAKE_INTERNAL_PLATFORM_ABI "${CMAKE_C_COMPILER_ABI}")
endif()

if(CMAKE_C_LIBRARY_ARCHITECTURE)
  set(CMAKE_LIBRARY_ARCHITECTURE "")
endif()

set(CMAKE_C_CL_SHOWINCLUDES_PREFIX "")
if(CMAKE_C_CL_SHOWINCLUDES_PREFIX)
  set(CMAKE_CL_SHOWINCLUDES_PREFIX "${CMAKE_C_CL_SHOWINCLUDES_PREFIX}")
endif()




set(CMAKE_C_IMPLICIT_LINK_LIBRARIES "")
set(CMAKE_C_IMPLICIT_LINK_DIRECTORIES "")
set(CMAKE_C_IMPLICIT_LINK_FRAMEWORK_DIRECTORIES "")
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

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

[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  ba8b071d3fb631c7e5a4893627f200a94d84b35e (commit)
   via  64130a7e793483e24c1d68bdd234f81d5edb2d51 (commit)
   via  277b7567f747bbfd8658a395da8eba79a2e01037 (commit)
   via  f77ad2c736061718c870dc09255efd9dea259d0d (commit)
   via  2c3b8a1cd801a8c3c5331d8345bf8ed6d9e38595 (commit)
   via  d9857c84574a8bd5c2d6739580fa98b6b2f8cefc (commit)
   via  1b034123e77ce50d618eeaa7cf800f7303dccb51 (commit)
   via  15a5653ea6cfc3b26634d3a5cea483e5a9ddd97a (commit)
   via  4ea249a387e808fa3d6c1f4648df7e094cf0d8a7 (commit)
  from  52485db76cef8bc24c8f11060234bded6d602060 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=efb0839989bdcbab047aabe37825d40e328d0ecb
commit efb0839989bdcbab047aabe37825d40e328d0ecb
Merge: 52485db ba8b071
Author: Brad King 
AuthorDate: Thu Mar 24 10:01:05 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Mar 24 10:01:05 2016 -0400

Merge topic 'test-release' into next

ba8b071d Merge branch 'release' into test-release
64130a7e CMake 3.5.1
277b7567 Merge branch 'fix-variable_watch-reallocation' into release
f77ad2c7 Merge branch 'FindCUDA-verbatim' into release
2c3b8a1c Merge branch 'fix-repeat-pkg-config' into release
d9857c84 Merge branch 'cpack-osx-optional-CoreServices' into release
1b034123 Merge branch 'cmake-gui-osx-identifier' into release
15a5653e Merge branch 'cpack-osx-no-carbon' into release
4ea249a3 Merge branch 'ios-install-combined-one-arch' into release


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ba8b071d3fb631c7e5a4893627f200a94d84b35e
commit ba8b071d3fb631c7e5a4893627f200a94d84b35e
Merge: 6d36fc8 64130a7
Author: Brad King 
AuthorDate: Thu Mar 24 10:00:18 2016 -0400
Commit: Brad King 
CommitDate: Thu Mar 24 10:00:18 2016 -0400

Merge branch 'release' into test-release


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=64130a7e793483e24c1d68bdd234f81d5edb2d51
commit 64130a7e793483e24c1d68bdd234f81d5edb2d51
Author: Brad King 
AuthorDate: Thu Mar 24 09:56:42 2016 -0400
Commit: Brad King 
CommitDate: Thu Mar 24 09:56:42 2016 -0400

CMake 3.5.1

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 129a882..683da43 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 5)
-set(CMake_VERSION_PATCH 0)
+set(CMake_VERSION_PATCH 1)
 #set(CMake_VERSION_RC 0)

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=277b7567f747bbfd8658a395da8eba79a2e01037
commit 277b7567f747bbfd8658a395da8eba79a2e01037
Merge: f77ad2c c610402
Author: Brad King 
AuthorDate: Wed Mar 23 16:18:08 2016 -0400
Commit: Brad King 
CommitDate: Wed Mar 23 16:18:08 2016 -0400

Merge branch 'fix-variable_watch-reallocation' into release


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f77ad2c736061718c870dc09255efd9dea259d0d
commit f77ad2c736061718c870dc09255efd9dea259d0d
Merge: 2c3b8a1 72a97b7
Author: Brad King 
AuthorDate: Tue Mar 22 11:36:45 2016 -0400
Commit: Brad King 
CommitDate: Tue Mar 22 11:36:45 2016 -0400

Merge branch 'FindCUDA-verbatim' into release


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2c3b8a1cd801a8c3c5331d8345bf8ed6d9e38595
commit 2c3b8a1cd801a8c3c5331d8345bf8ed6d9e38595
Merge: d9857c8 6f4f905
Author: Brad King 
AuthorDate: Mon Mar 21 09:08:25 2016 -0400
Commit: Brad King 
CommitDate: Mon Mar 21 09:08:25 2016 -0400

Merge branch 'fix-repeat-pkg-config' into release


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d9857c84574a8bd5c2d6739580fa98b6b2f8cefc
commit d9857c84574a8bd5c2d6739580fa98b6b2f8cefc
Merge: 1b03412 d84ba66
Author: Brad King 
AuthorDate: Fri Mar 18 11:15:15 2016 -0400
Commit: Brad King 
CommitDate: Fri Mar 18 11:15:15 2016 -0400

Merge branch 'cpack-osx-optional-CoreServices' into release


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1b034123e77ce50d618eeaa7cf800f7303dccb51
commit 1b034123e77ce50d618eeaa7cf800f7303dccb51
Merge: 15a5653 7b990e8
Author: Brad King 
AuthorDate: Thu Mar 17 16:30:00 2016 -0400

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

[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 ]
 [...] )

This mail here clarifies that all commands should be run sequentially:
https://cmake.org/pipermail/cmake/2009-June/030158.html


TLDR; what that mail states is that add_custom_command/add_custom_target 
COMMANDs run in sequence.

You use neither of those.

As stated by the quote  from the execute_process() documentation it runs 
the commands in parallel by design so that each process's output can be 
fed to the next process's input.


Nils
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

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

[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  06b7f5d2cac5e697b503337e870e34b11a592bd1 (commit)
  from  dc161109dbca44ee48b4a1b2a7cf1936ffa5aace (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=52485db76cef8bc24c8f11060234bded6d602060
commit 52485db76cef8bc24c8f11060234bded6d602060
Merge: dc16110 06b7f5d
Author: Zack Galbreath 
AuthorDate: Thu Mar 24 09:25:00 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Mar 24 09:25:00 2016 -0400

Merge topic 'only_change_timeout_once' into next

06b7f5d2 CTest: Only apply the secondary test timeout once


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=06b7f5d2cac5e697b503337e870e34b11a592bd1
commit 06b7f5d2cac5e697b503337e870e34b11a592bd1
Author: Zack Galbreath 
AuthorDate: Wed Mar 23 12:09:41 2016 -0400
Commit: Zack Galbreath 
CommitDate: Wed Mar 23 12:09:41 2016 -0400

CTest: Only apply the secondary test timeout once

This commit fixes a bug in the implementation of the test property
TIMEOUT_AFTER_MATCH.  The new timeout value was being applied
every time a line was output by the test after the match had been
encountered.  Now the new timeout value is only set once.

This commit also improves some output formatting related to this
property.

diff --git a/Source/CTest/cmCTestRunTest.cxx b/Source/CTest/cmCTestRunTest.cxx
index 7f3a077..f329e77 100644
--- a/Source/CTest/cmCTestRunTest.cxx
+++ b/Source/CTest/cmCTestRunTest.cxx
@@ -77,11 +77,13 @@ bool cmCTestRunTest::CheckOutput()
   if ( regIt->first.find(this->ProcessOutput.c_str()) )
 {
 cmCTestLog(this->CTest, HANDLER_VERBOSE_OUTPUT,
+   this->GetIndex() << ": " <<
"Test timeout changed to " <<
this->TestProperties->AlternateTimeout << std::endl);
 this->TestProcess->ResetStartTime();
 this->TestProcess->ChangeTimeout(
   this->TestProperties->AlternateTimeout);
+this->TestProperties->TimeoutRegularExpressions.clear();
 break;
 }
   }

---

Summary of changes:
 Source/CTest/cmCTestRunTest.cxx |2 ++
 1 file changed, 2 insertions(+)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  6d36fc8341aa7361a5786e78a19d9bab71ee42d2 (commit)
   via  917d49ed93b7b43ac3508dbd81f0645433880724 (commit)
   via  5b2acf6c1c904df96bd0031c9469e61118da5200 (commit)
   via  59f53f7422818f3ccad8518ab0863de6bb7fd293 (commit)
   via  3252e6e0755c04b062d18c574470db72f00ba372 (commit)
  from  efe4b5ca9b3223a816ebe63a8280cb92cc72ee42 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dc161109dbca44ee48b4a1b2a7cf1936ffa5aace
commit dc161109dbca44ee48b4a1b2a7cf1936ffa5aace
Merge: efe4b5c 6d36fc8
Author: Brad King 
AuthorDate: Thu Mar 24 08:49:57 2016 -0400
Commit: Brad King 
CommitDate: Thu Mar 24 08:49:57 2016 -0400

Merge branch 'master' into next


---

Summary of changes:


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  4527b9c41680aab191de7f37eca3fa47f1b07478 (commit)
  from  3252e6e0755c04b062d18c574470db72f00ba372 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=59f53f7422818f3ccad8518ab0863de6bb7fd293
commit 59f53f7422818f3ccad8518ab0863de6bb7fd293
Merge: 3252e6e 4527b9c
Author: Brad King 
AuthorDate: Thu Mar 24 08:49:38 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Mar 24 08:49:38 2016 -0400

Merge topic 'FindBoost-xl-compiler'

4527b9c4 FindBoost: Add support for IBM XL compiler


---

Summary of changes:
 Modules/FindBoost.cmake |2 ++
 1 file changed, 2 insertions(+)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  1dc8486b40d9a4885a88fa01573ba7a6e1f0690a (commit)
  from  02166c33dbeae976b2b1d1289c57f2648bb70efd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3252e6e0755c04b062d18c574470db72f00ba372
commit 3252e6e0755c04b062d18c574470db72f00ba372
Merge: 02166c3 1dc8486
Author: Brad King 
AuthorDate: Thu Mar 24 08:49:36 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Mar 24 08:49:36 2016 -0400

Merge topic 'doc-cmake_minimum_required-policy-reset'

1dc8486b Help: Organize and clarify `cmake_minimum_required` documentation


---

Summary of changes:
 Help/command/cmake_minimum_required.rst |   45 ++-
 1 file changed, 27 insertions(+), 18 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  b06e17da7b4137d22ae7cfcf14c6aa3205577822 (commit)
   via  525402450a1ccde0e9187c9613752f728a96149b (commit)
   via  b1e1aa1e6a2aa4c0da9d39f2e9f2a80d093f1dc7 (commit)
  from  5b2acf6c1c904df96bd0031c9469e61118da5200 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=917d49ed93b7b43ac3508dbd81f0645433880724
commit 917d49ed93b7b43ac3508dbd81f0645433880724
Merge: 5b2acf6 b06e17d
Author: Brad King 
AuthorDate: Thu Mar 24 08:49:43 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Mar 24 08:49:43 2016 -0400

Merge topic 'cmake-depend-in-project-only'

b06e17da Help: Add notes for topic 'cmake-depend-in-project-only'
52540245 Tests: Add test for CMAKE_DEPENDS_IN_PROJECT_ONLY variable
b1e1aa1e Makefile: Optionally scan only source and build trees for 
dependencies


---

Summary of changes:
 Help/manual/cmake-variables.7.rst  |1 +
 Help/release/dev/cmake-depend-in-project-only.rst  |6 ++
 Help/variable/CMAKE_DEPENDS_IN_PROJECT_ONLY.rst|   10 
 Source/cmLocalUnixMakefileGenerator3.cxx   |   61 
 Tests/RunCMake/BuildDepends/MakeInProjectOnly.c|2 +
 .../RunCMake/BuildDepends/MakeInProjectOnly.cmake  |   16 +
 .../BuildDepends/MakeInProjectOnly.step1.cmake |3 +
 .../BuildDepends/MakeInProjectOnly.step2.cmake |3 +
 Tests/RunCMake/BuildDepends/RunCMakeTest.cmake |5 ++
 9 files changed, 107 insertions(+)
 create mode 100644 Help/release/dev/cmake-depend-in-project-only.rst
 create mode 100644 Help/variable/CMAKE_DEPENDS_IN_PROJECT_ONLY.rst
 create mode 100644 Tests/RunCMake/BuildDepends/MakeInProjectOnly.c
 create mode 100644 Tests/RunCMake/BuildDepends/MakeInProjectOnly.cmake
 create mode 100644 Tests/RunCMake/BuildDepends/MakeInProjectOnly.step1.cmake
 create mode 100644 Tests/RunCMake/BuildDepends/MakeInProjectOnly.step2.cmake


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  c61040282557ba268e144ffa5e2d1935b5991d8d (commit)
  from  917d49ed93b7b43ac3508dbd81f0645433880724 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6d36fc8341aa7361a5786e78a19d9bab71ee42d2
commit 6d36fc8341aa7361a5786e78a19d9bab71ee42d2
Merge: 917d49e c610402
Author: Brad King 
AuthorDate: Thu Mar 24 08:49:46 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Mar 24 08:49:46 2016 -0400

Merge topic 'fix-variable_watch-reallocation'

c6104028 Avoid occasional use-after-free when a variable watch is executed


---

Summary of changes:
 Source/cmMakefile.cxx  |   23 +++
 Source/cmVariableWatch.cxx |4 +++-
 Source/cmVariableWatch.h   |2 +-
 3 files changed, 19 insertions(+), 10 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  ad140c6e1bb6eda5d17a199304578dbd92bedbad (commit)
   via  f069be054833f465ab469b534fddbc52c5c9913b (commit)
   via  c05ea48545f04dee8666094b0731366b64dfc9ad (commit)
   via  78ec04613063653008f221eed644f1c2566fd900 (commit)
  from  59f53f7422818f3ccad8518ab0863de6bb7fd293 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5b2acf6c1c904df96bd0031c9469e61118da5200
commit 5b2acf6c1c904df96bd0031c9469e61118da5200
Merge: 59f53f7 ad140c6
Author: Brad King 
AuthorDate: Thu Mar 24 08:49:41 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Mar 24 08:49:41 2016 -0400

Merge topic 'vs-startup-project'

ad140c6e VS: Put ALL_BUILD in the PREDEFINED_TARGETS_FOLDER
f069be05 VS: Fix default target support for targets nested inside a folder
c05ea485 VS: Improve unit test macros
78ec0461 VS: Add option to choose the `.sln` startup project (#15578)


---

Summary of changes:
 Help/manual/cmake-properties.7.rst |1 +
 Help/prop_dir/VS_STARTUP_PROJECT.rst   |   12 +++
 Help/release/dev/vs-startup-project.rst|6 
 Source/cmGlobalVisualStudio71Generator.cxx |   22 +++--
 Source/cmGlobalVisualStudioGenerator.cxx   |   34 
 Source/cmGlobalVisualStudioGenerator.h |2 ++
 Tests/RunCMake/CMakeLists.txt  |5 ++-
 Tests/RunCMake/VSSolution/RunCMakeTest.cmake   |6 
 .../RunCMake/VSSolution/StartupProject-check.cmake |5 +++
 Tests/RunCMake/VSSolution/StartupProject.cmake |2 ++
 .../VSSolution/StartupProjectMissing-check.cmake   |5 +++
 .../VSSolution/StartupProjectMissing-stderr.txt|4 +++
 .../VSSolution/StartupProjectMissing.cmake |1 +
 .../StartupProjectUseFolders-check.cmake   |9 ++
 .../VSSolution/StartupProjectUseFolders.cmake  |3 ++
 Tests/RunCMake/VSSolution/solution_parsing.cmake   |   15 +
 16 files changed, 122 insertions(+), 10 deletions(-)
 create mode 100644 Help/prop_dir/VS_STARTUP_PROJECT.rst
 create mode 100644 Help/release/dev/vs-startup-project.rst
 create mode 100644 Tests/RunCMake/VSSolution/StartupProject-check.cmake
 create mode 100644 Tests/RunCMake/VSSolution/StartupProject.cmake
 create mode 100644 Tests/RunCMake/VSSolution/StartupProjectMissing-check.cmake
 create mode 100644 Tests/RunCMake/VSSolution/StartupProjectMissing-stderr.txt
 create mode 100644 Tests/RunCMake/VSSolution/StartupProjectMissing.cmake
 create mode 100644 
Tests/RunCMake/VSSolution/StartupProjectUseFolders-check.cmake
 create mode 100644 Tests/RunCMake/VSSolution/StartupProjectUseFolders.cmake


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

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

[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  ad140c6e1bb6eda5d17a199304578dbd92bedbad (commit)
   via  f069be054833f465ab469b534fddbc52c5c9913b (commit)
  from  89b60904cdd2d27cd9dbeea919b267522524702d (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=efe4b5ca9b3223a816ebe63a8280cb92cc72ee42
commit efe4b5ca9b3223a816ebe63a8280cb92cc72ee42
Merge: 89b6090 ad140c6
Author: Brad King 
AuthorDate: Thu Mar 24 08:44:54 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Mar 24 08:44:54 2016 -0400

Merge topic 'vs-startup-project' into next

ad140c6e VS: Put ALL_BUILD in the PREDEFINED_TARGETS_FOLDER
f069be05 VS: Fix default target support for targets nested inside a folder


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ad140c6e1bb6eda5d17a199304578dbd92bedbad
commit ad140c6e1bb6eda5d17a199304578dbd92bedbad
Author: Taylor Braun-Jones 
AuthorDate: Mon Mar 21 16:05:41 2016 -0400
Commit: Brad King 
CommitDate: Wed Mar 23 13:22:15 2016 -0400

VS: Put ALL_BUILD in the PREDEFINED_TARGETS_FOLDER

diff --git a/Source/cmGlobalVisualStudioGenerator.cxx 
b/Source/cmGlobalVisualStudioGenerator.cxx
index b11b49a..04146fb 100644
--- a/Source/cmGlobalVisualStudioGenerator.cxx
+++ b/Source/cmGlobalVisualStudioGenerator.cxx
@@ -89,19 +89,13 @@ void cmGlobalVisualStudioGenerator::AddExtraIDETargets()
   cmGeneratorTarget* gt = new cmGeneratorTarget(allBuild, gen[0]);
   gen[0]->AddGeneratorTarget(gt);
 
-#if 0
-  // Can't activate this code because we want ALL_BUILD
-  // selected as the default "startup project" when first
-  // opened in Visual Studio... And if it's nested in a
-  // folder, then that doesn't happen.
   //
   // Organize in the "predefined targets" folder:
   //
-  if (this->UseFolderProperty())
+  if (this->UseFolderProperty() && this->GetVersion() > VS71)
 {
 allBuild->SetProperty("FOLDER", this->GetPredefinedTargetsFolder());
 }
-#endif
 
   // Now make all targets depend on the ALL_BUILD target
   for(std::vector::iterator i = gen.begin();

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f069be054833f465ab469b534fddbc52c5c9913b
commit f069be054833f465ab469b534fddbc52c5c9913b
Author: Taylor Braun-Jones 
AuthorDate: Mon Mar 21 16:01:20 2016 -0400
Commit: Brad King 
CommitDate: Wed Mar 23 13:22:15 2016 -0400

VS: Fix default target support for targets nested inside a folder

It's not actually the first target in a `.sln` file that is treated as
the default startup project, but rather the first fully defined target.

diff --git a/Source/cmGlobalVisualStudio71Generator.cxx 
b/Source/cmGlobalVisualStudio71Generator.cxx
index f6796a5..7b51fdf 100644
--- a/Source/cmGlobalVisualStudio71Generator.cxx
+++ b/Source/cmGlobalVisualStudio71Generator.cxx
@@ -97,14 +97,31 @@ void cmGlobalVisualStudio71Generator
   OrderedTargetDependSet orderedProjectTargets(
 projectTargets, this->GetStartupProjectName(root));
 
-  this->WriteTargetsToSolution(fout, root, orderedProjectTargets);
+  // Generate the targets specification to a string.  We will put this in
+  // the actual .sln file later.  As a side effect, this method also
+  // populates the set of folders.
+  std::ostringstream targetsSlnString;
+  this->WriteTargetsToSolution(targetsSlnString, root, orderedProjectTargets);
+
+  // VS 7 does not support folders specified first.
+  if (this->GetVersion() <= VS71)
+{
+fout << targetsSlnString.str();
+}
 
+  // Generate folder specification.
   bool useFolderProperty = this->UseFolderProperty();
   if (useFolderProperty)
 {
 this->WriteFolders(fout);
 }
 
+  // Now write the actual target specification content.
+  if (this->GetVersion() > VS71)
+{
+fout << targetsSlnString.str();
+}
+
   // Write out the configurations information for the solution
   fout << "Global\n";
   // Write out the configurations for the solution
diff --git a/Tests/RunCMake/CMakeLists.txt b/Tests/RunCMake/CMakeLists.txt
index c7fe649..0207753 100644
--- a/Tests/RunCMake/CMakeLists.txt
+++ b/Tests/RunCMake/CMakeLists.txt
@@ -234,7 +234,10 @@ endif()
 
 if("${CMAKE_GENERATOR}" MATCHES "Visual Studio")
   add_RunCMake_test(include_external_msproject)
-  add_RunCMake_test(VSSolution)
+  if("${CMAKE_GENERATOR}" MATCHES "Visual Studio ([789]|10)" AND 

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

[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:

/usr/bin/g++-4.9 -D USE_FEATURE -o CMakeFiles/mimi.dir/main.cpp.o -c
~/cmakeBug/main.cpp

Meaning the option has been correctly added. Note that the space after
`-D` is allowed and completely fine.

Now the CMakeLists.txt with FindCUDA:

cmake_minimum_required(VERSION 3.5)
find_package( CUDA )
add_definitions( "-D USE_FEATURE" )
add_definitions( "-DUSE_FEATURE2" )
SET_SOURCE_FILES_PROPERTIES( main.cpp PROPERTIES
CUDA_SOURCE_PROPERTY_FORMAT OBJ )
cuda_add_library( mimi main.cpp )
target_link_libraries( mimi )

The compile command produced now is:

/usr/bin/nvcc ~/cmakeBug/main.cpp -x=cu -c -o
~/cmakeBug/build/CMakeFiles/mimi.dir//./mimi_generated_main.cpp.o
-ccbin /usr/bin/gcc-4.9 -m64 -DUSE_FEATURE2 -Xcompiler ,\"-g\"
-DNVCC -I/usr/include -I/usr/include

Meaning `-D USE_FEATURE` was silently ignored (resulting in me wondering
for many hours why it just won't work), but `-DUSE_FEATURE2` has been
added correctly.

Note that I also had a similar problem when trying to (admittedly rather
clumsily) adding multiple options:

add_definitions( "-DUSE_FEATURE ${FFTW_DEFINITIONS}" )
add_definitions( "-DUSE_FEATURE" ${FFTW_DEFINITIONS} )

The first version will be completely ignored, but the second version
works fine. I highly think that this is because of the space in the
middle.

I found this bug, because I want to do `add_definitions( "-isystem
/user_system_library" )` in order to implement a workaround for this
bug: https://cmake.org/Bug/view.php?id=14415

Another problem is, that findCUDA ignores all definitions which don't
begin with `-D` I think. at least `add_definition("-isystem/mimi")` will
be ignored. This means I can't test, what happens with paths containing
spaces.

-- 
http://www.fastmail.com - Or how I learned to stop worrying and
  love email again

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

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

[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
 WORKING_DIRECTORY ./submodule )

What I found is that a folder CMakeFiles was created in ./submodule, but
there were no other files in ./submodule, especially no Makefile, which
made the second command quit with an error message:

make: *** No targets specified and no makefile found.  Stop.

# What I expected it to do

The CMake 3.5.0 documentation specifies the execute_process command like
this:

execute_process(COMMAND  [args1...]]
[COMMAND  [args2...] [...]]
[WORKING_DIRECTORY ]
[...] )

This mail here clarifies that all commands should be run sequentially:
https://cmake.org/pipermail/cmake/2009-June/030158.html

# Here is a minimal non-working example

./CMakeLists.txt:
cmake_minimum_required(VERSION 3.5)
execute_process(
COMMAND echo  "test1"
COMMAND touch "test1"
COMMAND sleep 4s
COMMAND echo  "test2"
COMMAND touch "test2"
COMMAND sleep 4s
COMMAND echo  "test4"
)

execute_process(
COMMAND mkdir -p build
)

execute_process(
COMMAND cmake .
COMMAND make
WORKING_DIRECTORY "./build"
)

./build/CMakeLists.txt
cmake_minimum_required(VERSION 3.5)
execute_process(
COMMAND echo  "build/test1"
COMMAND touch "test1"
COMMAND sleep 4s
COMMAND echo  "build/test2"
COMMAND touch "test2"
COMMAND sleep 4s
COMMAND echo  "build/test4"
)

Now make a testrun with `time cmake .`:
test4
make: *** No targets specified and no makefile found.  Stop.
-- Configuring done
-- Generating done
-- Build files have been written to: ~/cmakeExecuteProcessTest

real0m4.141s
user0m0.104s
sys 0m0.016s

After this run the directory structure is as follows (`find . -type f
-exec bash -c 'ls --full-time {}' \;`):

16:40:37.673199038 ./CMakeFiles/feature_tests.bin
17:16:51.452163375 ./CMakeFiles/TargetDirectories.txt
17:16:51.452163375 ./CMakeFiles/Makefile.cmake
16:40:36.757185936
./CMakeFiles/3.5.0/CMakeDetermineCompilerABI_C.bin
16:40:36.429181244 ./CMakeFiles/3.5.0/CMakeSystem.cmake
16:40:37.233192745
./CMakeFiles/3.5.0/CMakeDetermineCompilerABI_CXX.bin
16:40:37.681199152 ./CMakeFiles/3.5.0/CMakeCXXCompiler.cmake
16:40:36.449181531 ./CMakeFiles/3.5.0/CompilerIdC/CMakeCCompilerId.c
16:40:36.485182046 ./CMakeFiles/3.5.0/CompilerIdC/a.out
16:40:36.997189369 ./CMakeFiles/3.5.0/CMakeCCompiler.cmake
16:40:36.517182503
./CMakeFiles/3.5.0/CompilerIdCXX/CMakeCXXCompilerId.cpp
16:40:36.589183533 ./CMakeFiles/3.5.0/CompilerIdCXX/a.out
17:16:51.452163375 ./CMakeFiles/progress.marks
17:16:51.452163375 ./CMakeFiles/cmake.check_cache
16:40:37.677199094 ./CMakeFiles/CMakeOutput.log
17:16:51.452163375 ./CMakeFiles/Makefile2
16:40:36.921188282 ./CMakeFiles/feature_tests.c
16:40:37.537197092 ./CMakeFiles/feature_tests.cxx
16:41:16.213750307 ./CMakeFiles/CMakeDirectoryInformation.cmake
17:16:09.227562260 ./build/CMakeLists.txt
17:16:51.368162180 ./build/CMakeFiles/3.5.0/CMakeSystem.cmake
17:16:51.396162579
./build/CMakeFiles/3.5.0/CompilerIdC/CMakeCCompilerId.c
17:16:51.440163206 ./build/CMakeFiles/3.5.0/CompilerIdC/a.out
17:16:51.452163375 ./build/CMakeFiles/CMakeOutput.log
17:16:45.900084334 ./CMakeLists.txt
16:40:37.685199210 ./CMakeCache.txt
16:41:16.213750307 ./cmake_install.cmake
17:16:47.328104663 ./test1
17:16:47.332104722 ./test2
17:16:51.452163375 ./Makefile

First things to note:

  - ./test1, ./test2 do exist, meaning all commands seem to have run
  - ./build/test1 and ./build/test2 don't exist, meaning `cmake ..`
  didn't run completely
  - only build/CMakeFiles/ exists, but not other files, especially not
  build/Makefile
  - the timestamps of test1 and test2 are definitely not 4s apart,
  meaning it looks like all commands did run in parallel
  - the time needed by CMake is 4s not 8s like it should be if both
  `sleep 4s` commands would have been executed sequentially
  - only "test4" will be printed, meaning the output of all commands
  except the last specified in `execute_process` is ignored

# Further Test:

Changing the order in:

execute_process(
COMMAND cmake .
COMMAND make
WORKING_DIRECTORY "./build"
)

to:

execute_process(
COMMAND make
COMMAND cmake .
WORKING_DIRECTORY "./build"
)

Will make result in a Makefile being created and no error message being
produced by Makefile.
This suggests, that the last command is spawned before the command
before it, 

Re: [CMake] Two phase install?

[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 new build cmd) the proeject is not run in
>parallel.
>
>I am pretty sure ExternalProject_Add only works with generators
>associated with build commands you can run from the command line such
>as make, nmake, jom, ninja, etc..  So, for MSVC the way you arrange
>that is
>avoid all the visual studio generators, and instead use one of
>"NMake Makefiles", "NMake Makefiles JOM", or "Ninja".

No. Just as with cmake-generated solutions, you can build those on the command 
line using msbuild or devenv, the one used by cmake depends on the cmake 
version. You can even use cmake itself to trigger the right build command for 
those. Parallel building must be enabled by hand when using msbuild. For 
devenv, the setting from the IDE is used.

HS

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Two phase install?

[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 ExternalProject_Add only works with generators
associated with build commands you can run from the command line such
as make, nmake, jom, ninja, etc..  So, for MSVC the way you arrange that is
avoid all the visual studio generators, and instead use one of
"NMake Makefiles", "NMake Makefiles JOM", or "Ninja".

Alan

__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

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

[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 some of its path with the build 
directory, CPackRPM uses a different method for dealing with it than if the two 
paths don't share any prefix.)

In our case some files are picked up from a network drive, while the build 
happens (naturally) on a local drive. I can reproduce the issue with a 
CMakeLists.txt file like:

cmake_minimum_required( VERSION 2.8 )
project( CPackRPMLinkProblem )

install( FILES /afs/cern.ch/.../some_link.txt DESTINATION . )

set( CPACK_PACKAGE_RELOCATABLE TRUE )
include( CPack )

As long as the build directory's path name ends up being longer than the path 
name of the file specified in the install(...) command, the RPM building fails. 
As it does for instance here:

http://atlas-computing.web.cern.ch/atlas-computing/links/distDirectory/nightlies/experimentalWebArea/nicos_web_areaCMAKE64BS6G49AnlOpt/NICOS_Log_rel_4/nicos_rpm_build.html

Cheers,
   Attila

> On 23 Mar 2016, at 15:57, Domen Vrankar  wrote:
> 
> As a workaround you could set files that you would like to be excluded
> from symlink relocation with CPACK_RPM_USER_FILELIST or
> CPACK_RPM__USER_FILELIST.
> 
> I'll have a look at how this could be solved for later versions of CPack.
> Do I understand correctly that those errors occur when a symlink is
> pointing to another simlink outside your project?
> Could you please provide a minimal example of all your cases?
> 
> Thanks,
> Domen
> 
> 
> 2016-03-23 14:13 GMT+01:00 Attila Krasznahorkay
> :
>> Hi Brad,
>> 
>> I did. Then I get:
>> 
>> CMake Error at 
>> /afs/cern.ch/work/k/krasznaa/public/cmake/3.5.0/share/cmake-3.5/Modules/CPackRPM.cmake:981
>>  (string):
>> string begin index: 164 is out of range 0 - 156
>> Call Stack (most recent call first):
>> /afs/cern.ch/work/k/krasznaa/public/cmake/3.5.0/share/cmake-3.5/Modules/CPackRPM.cmake:1625
>>  (cpack_rpm_prepare_install_files)
>> /afs/cern.ch/work/k/krasznaa/public/cmake/3.5.0/share/cmake-3.5/Modules/CPackRPM.cmake:1787
>>  (cpack_rpm_generate_package)
>> 
>> You can find the full output here:
>> 
>> http://atlas-computing.web.cern.ch/atlas-computing/links/distDirectory/nightlies/experimentalWebArea/nicos_web_areaCMAKE64BS6G49TrgOpt/NICOS_Log_rel_3/nicos_rpm_build.html
>> 
>> Note that when I tried to build the project in a build area with a shorter 
>> path, then the RPM building succeeded. Just because by chance in that case 
>> in the expression
>> 
>> string(SUBSTRING "${SYMLINK_POINT_}" ${WDR_LEN_} -1 SYMLINK_POINT_WD_)
>> 
>> the work directory length was shorter than the length of the path outside of 
>> the project.
>> 
>> Of course this is the code that we're talking about:
>> 
>> https://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CPackRPM.cmake;h=7ffec136deabb8f28d6293cdc96e43cd4a2af70d;hb=HEAD#l994
>> 
>> Cheers,
>> Attila
>> 
>>> On 23 Mar 2016, at 13:50, Brad King  wrote:
>>> 
>>> On 03/23/2016 08:44 AM, Attila Krasznahorkay wrote:
 CMake Error at /afs/cern.ch/sw/lcg/contrib/CMake/3.3.2/...
>>> 
>>> Please try with CMake 3.5.
>>> 
>>> -Brad
>>> 
>> 

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

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

[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  c70ac0970dde1510322ed3a398f8656e38ae06c8 (commit)
   via  02166c33dbeae976b2b1d1289c57f2648bb70efd (commit)
  from  f6693dca380152ff9bfd2e06daf800de9edf95b1 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=89b60904cdd2d27cd9dbeea919b267522524702d
commit 89b60904cdd2d27cd9dbeea919b267522524702d
Merge: f6693dc c70ac09
Author: Nils Gladitz 
AuthorDate: Thu Mar 24 04:37:58 2016 -0400
Commit: CMake Topic Stage 
CommitDate: Thu Mar 24 04:37:58 2016 -0400

Merge topic 'cpackcomponents-priv-var' into next

c70ac097 CPack: Exclude additional internal variables from CPackConfig.cmake
02166c33 CMake Nightly Date Stamp


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c70ac0970dde1510322ed3a398f8656e38ae06c8
commit c70ac0970dde1510322ed3a398f8656e38ae06c8
Author: Nils Gladitz 
AuthorDate: Thu Mar 24 09:28:41 2016 +0100
Commit: Nils Gladitz 
CommitDate: Thu Mar 24 09:28:41 2016 +0100

CPack: Exclude additional internal variables from CPackConfig.cmake

In v2.8.12.1-654-g7621ad6 I added underscore prefixes to
CPACK_ADDCOMP_(STR|UNAME) to prevent them from being automatically
written to CPackConfig.cmake.

Do the same for CPACK_ADDGRP_(STR|UNAME) and CPACK_INSTTYPE_(STR|UNAME).

diff --git a/Modules/CPackComponent.cmake b/Modules/CPackComponent.cmake
index 96d5609..038a717 100644
--- a/Modules/CPackComponent.cmake
+++ b/Modules/CPackComponent.cmake
@@ -444,60 +444,60 @@ endmacro()
 
 # Macro that adds a component group to the CPack installer
 macro(cpack_add_component_group grpname)
-  string(TOUPPER ${grpname} CPACK_ADDGRP_UNAME)
-  cpack_parse_arguments(CPACK_COMPONENT_GROUP_${CPACK_ADDGRP_UNAME}
+  string(TOUPPER ${grpname} _CPACK_ADDGRP_UNAME)
+  cpack_parse_arguments(CPACK_COMPONENT_GROUP_${_CPACK_ADDGRP_UNAME}
 "DISPLAY_NAME;DESCRIPTION;PARENT_GROUP"
 "EXPANDED;BOLD_TITLE"
 ${ARGN}
 )
 
-  set(CPACK_ADDGRP_STR "\n# Configuration for component group 
\"${grpname}\"\n")
+  set(_CPACK_ADDGRP_STR "\n# Configuration for component group 
\"${grpname}\"\n")
   cpack_append_string_variable_set_command(
-CPACK_COMPONENT_GROUP_${CPACK_ADDGRP_UNAME}_DISPLAY_NAME
-CPACK_ADDGRP_STR)
+CPACK_COMPONENT_GROUP_${_CPACK_ADDGRP_UNAME}_DISPLAY_NAME
+_CPACK_ADDGRP_STR)
   cpack_append_string_variable_set_command(
-CPACK_COMPONENT_GROUP_${CPACK_ADDGRP_UNAME}_DESCRIPTION
-CPACK_ADDGRP_STR)
+CPACK_COMPONENT_GROUP_${_CPACK_ADDGRP_UNAME}_DESCRIPTION
+_CPACK_ADDGRP_STR)
   cpack_append_string_variable_set_command(
-CPACK_COMPONENT_GROUP_${CPACK_ADDGRP_UNAME}_PARENT_GROUP
-CPACK_ADDGRP_STR)
+CPACK_COMPONENT_GROUP_${_CPACK_ADDGRP_UNAME}_PARENT_GROUP
+_CPACK_ADDGRP_STR)
   cpack_append_option_set_command(
-CPACK_COMPONENT_GROUP_${CPACK_ADDGRP_UNAME}_EXPANDED
-CPACK_ADDGRP_STR)
+CPACK_COMPONENT_GROUP_${_CPACK_ADDGRP_UNAME}_EXPANDED
+_CPACK_ADDGRP_STR)
   cpack_append_option_set_command(
-CPACK_COMPONENT_GROUP_${CPACK_ADDGRP_UNAME}_BOLD_TITLE
-CPACK_ADDGRP_STR)
+CPACK_COMPONENT_GROUP_${_CPACK_ADDGRP_UNAME}_BOLD_TITLE
+_CPACK_ADDGRP_STR)
   # Backward compatibility issue.
   # Write to config iff the macros is used after CPack.cmake has been
   # included, other it's not necessary because the variables
   # will be encoded by cpack_encode_variables.
   if(CPack_CMake_INCLUDED)
-file(APPEND "${CPACK_OUTPUT_CONFIG_FILE}" "${CPACK_ADDGRP_STR}")
+file(APPEND "${CPACK_OUTPUT_CONFIG_FILE}" "${_CPACK_ADDGRP_STR}")
   endif()
 endmacro()
 
 # Macro that adds an installation type to the CPack installer
 macro(cpack_add_install_type insttype)
-  string(TOUPPER ${insttype} CPACK_INSTTYPE_UNAME)
-  cpack_parse_arguments(CPACK_INSTALL_TYPE_${CPACK_INSTTYPE_UNAME}
+  string(TOUPPER ${insttype} _CPACK_INSTTYPE_UNAME)
+  cpack_parse_arguments(CPACK_INSTALL_TYPE_${_CPACK_INSTTYPE_UNAME}
 "DISPLAY_NAME"
 ""
 ${ARGN}
 )
 
-  set(CPACK_INSTTYPE_STR
+  set(_CPACK_INSTTYPE_STR
 "\n# Configuration for installation type \"${insttype}\"\n")
-  set(CPACK_INSTTYPE_STR
-"${CPACK_INSTTYPE_STR}list(APPEND CPACK_ALL_INSTALL_TYPES ${insttype})\n")
+  set(_CPACK_INSTTYPE_STR
+"${_CPACK_INSTTYPE_STR}list(APPEND CPACK_ALL_INSTALL_TYPES ${insttype})\n")
   cpack_append_string_variable_set_command(
-CPACK_INSTALL_TYPE_${CPACK_INSTTYPE_UNAME}_DISPLAY_NAME
-CPACK_INSTTYPE_STR)
+

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

[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:
> 
> Makefile: Optionally scan only source and build trees for dependencies
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b1e1aa1e
> 
> I also added a test case and release note:
> 
> Tests: Add test for CMAKE_DEPENDS_IN_PROJECT_ONLY variable
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=52540245
> 
> Help: Add notes for topic 'cmake-depend-in-project-only'
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b06e17da
> 
> -Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers