Re: [CMake] How to set _default_ timeout for the ctest command?

[Marcel Loose]

Hi Alan,

Just by experimenting, I discovered that you also need to set
DART_TESTING_TIMEOUT. I'm not sure what the relationship (if any) is
between CTEST_TEST_TIMEOUT and DART_TESTING_TIMEOUT. I set them both in
the file CTestConfig.cmake. I get the feeling that DART_TESTING_TIMEOUT
is there for less than historic reasons. Maybe someone from Kitware can
shed a light on this.

Regards,
Marcel Loose.


On 09/12/15 07:33, Alan W. Irwin wrote:
> For the lapack CMake-based build and test system, some of the ctests
> can exceed 1500 seconds (the default limit) for special conditions
> (e.g, a quadruple-precision build of lapack that can be very slow). To
> reduce such issues without forcing users to use the ctest --timeout
>  option, the lapack developers would like to
> increase the default limit substantially above 1500 seconds.  Does
> anyone here know how to do that?
>
> I guessed that setting CTEST_TEST_TIMEOUT might do that, but when I
> experimentally set that to a small number (actually 1) (just before
> the first add_test command of another project I am completely familiar
> with (PLplot, natch)) the ctests that ran beyond that one second limit
> did not error out (i.e., I presume they were still using the 1500
> second default).  Note, the ctests I am referring to are simply run
> using the ctest command from the command line and are not submitted to
> a dashboard server.
>
> I presume another way to do it would be to set the TIMEOUT test property
> for every ctest, but that constitutes a maintanence issue, i.e., it
> is a pretty clumsy way to do it.
>
> So any ideas for setting the default timeout (either higher or lower
> than 1500) for ctests would be welcome.
>
> 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] Please comment on ios-universal topic

[Ruslan Baratov via cmake-developers]

On 09-Dec-15 04:51, Gregor Jasny wrote:


Hello,

On 02/12/15 13:44, Bartosz Kosiorek wrote:

I would like to propose to rename property name to INSTALL_IOS_UNIVERSAL_LIBS.

My thoughts about the property name:

I added the necessary functionality to also combine Frameworks and App
Bundles. So the _LIBS suffix now got misleading. And I think that
providing a different property for libraries, frameworks and app bundles
is not really helpful. To combine all targets one could set the CMAKE_
prefixed variable, to combine only some, one could set the property on
the target itself.

Deploying applications which support both armv7 (32bit) and armv8
(64bit) is already working by setting both architectures in the
OSX_ARCHITECTURES property because both are covered by the device SDK.

So technically we already support UNIVERSAL libraries. What we don't
support is combining device and simulator builds. So how about replacing
UNIVERSAL with COMBINED?

IOS_INSTALL_COMBINED_BINARY


Just to clarify you want to leave only one variable IOS_INSTALL_COMBINED_BINARY 
for the device + simulator on iOS platforms. Other platforms (in future) will 
be controlled by using *_ARCHITECTURES variables, right?

Ruslo

--

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-developers] Keil Armcc support

[yann suisini]

Hi,

Is theresomme support planned in a near future for the Keil / Armcc
toolchain ?

Regards,

Yann Suisini
-- 

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.4.1-656-g27ed820

[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  27ed820c816a80bf140613cb2f47ccb2f21b021f (commit)
   via  27e6f74f29084fbdee35eb5a8d309d99d39e66d8 (commit)
   via  c926efa1398aa2c4ff273dee173d84d0031bcdf6 (commit)
  from  3a824a963ac54930b072e2d31c54e182af3d027c (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=27ed820c816a80bf140613cb2f47ccb2f21b021f
commit 27ed820c816a80bf140613cb2f47ccb2f21b021f
Merge: 3a824a9 27e6f74
Author: Brad King 
AuthorDate: Wed Dec 9 08:36:50 2015 -0500
Commit: CMake Topic Stage 
CommitDate: Wed Dec 9 08:36:50 2015 -0500

Merge topic 'cpack-rpm-percomponent-group-and-name'

27e6f74f CPack: Added tests for package name and group controll fields
c926efa1 CPackRPM: Configure RPM package group and name per component


---

Summary of changes:
 .../dev/cpack-rpm-percomponent-group-and-name.rst  |7 
 Modules/CPackRPM.cmake |   39 ++--
 .../DEB/PER_COMPONENT_FIELDS-ExpectedFiles.cmake   |9 +
 .../DEB/PER_COMPONENT_FIELDS-VerifyResult.cmake|   18 +
 .../CPack/DEB/PER_COMPONENT_FIELDS-specifics.cmake |6 +++
 Tests/RunCMake/CPack/PER_COMPONENT_FIELDS.cmake|5 +++
 Tests/RunCMake/CPack/RPM/Helpers.cmake |9 +
 .../RPM/PER_COMPONENT_FIELDS-ExpectedFiles.cmake   |9 +
 .../RPM/PER_COMPONENT_FIELDS-VerifyResult.cmake|   18 +
 .../CPack/RPM/PER_COMPONENT_FIELDS-specifics.cmake |5 +++
 Tests/RunCMake/CPack/RunCMakeTest.cmake|1 +
 11 files changed, 115 insertions(+), 11 deletions(-)
 create mode 100644 Help/release/dev/cpack-rpm-percomponent-group-and-name.rst
 create mode 100644 
Tests/RunCMake/CPack/DEB/PER_COMPONENT_FIELDS-ExpectedFiles.cmake
 create mode 100644 
Tests/RunCMake/CPack/DEB/PER_COMPONENT_FIELDS-VerifyResult.cmake
 create mode 100644 
Tests/RunCMake/CPack/DEB/PER_COMPONENT_FIELDS-specifics.cmake
 create mode 100644 Tests/RunCMake/CPack/PER_COMPONENT_FIELDS.cmake
 create mode 100644 
Tests/RunCMake/CPack/RPM/PER_COMPONENT_FIELDS-ExpectedFiles.cmake
 create mode 100644 
Tests/RunCMake/CPack/RPM/PER_COMPONENT_FIELDS-VerifyResult.cmake
 create mode 100644 
Tests/RunCMake/CPack/RPM/PER_COMPONENT_FIELDS-specifics.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.4.1-1649-gdf5dbe2

[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  df5dbe2d51b9b88583792bdfe818c97e8a6474c8 (commit)
   via  a7ef02253bf8ef33d4ffdd761802ea30ef289b8a (commit)
  from  8b8a03fc4a03845c797523d918fc06d408dde2c7 (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=df5dbe2d51b9b88583792bdfe818c97e8a6474c8
commit df5dbe2d51b9b88583792bdfe818c97e8a6474c8
Merge: 8b8a03f a7ef022
Author: Brad King 
AuthorDate: Wed Dec 9 08:36:08 2015 -0500
Commit: CMake Topic Stage 
CommitDate: Wed Dec 9 08:36:08 2015 -0500

Merge topic 'detect-cray-wrappers' into next

a7ef0225 Cray: Refactor the Cray platform files to use compiler wrapper 
checks


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a7ef02253bf8ef33d4ffdd761802ea30ef289b8a
commit a7ef02253bf8ef33d4ffdd761802ea30ef289b8a
Author: Chuck Atkins 
AuthorDate: Wed Dec 2 10:00:44 2015 -0600
Commit: Brad King 
CommitDate: Wed Dec 9 08:35:19 2015 -0500

Cray: Refactor the Cray platform files to use compiler wrapper checks

This is an extensive refactoring of the Cray compiler wrapper usage.
Using the new compiler wrapper checks, the CrayPrgEnv info files have
been moved from Platform/ to Compiler/.  The adjusted naming convention
allows the compiler-wrapper information files to be loaded for both the
CrayLinuxEnvironment platform when cross-compiling and the Linux
platform if building natively on the Cray compute nodes.  It also
creates a separation of common arguments for compiler id and language
information used to perform the appropriate introspection of implicit
arguments and libraries used by the compiler wrappers based on the
loaded module environment.

diff --git a/Modules/Compiler/CrayPrgEnv-C.cmake 
b/Modules/Compiler/CrayPrgEnv-C.cmake
new file mode 100644
index 000..6b461ce
--- /dev/null
+++ b/Modules/Compiler/CrayPrgEnv-C.cmake
@@ -0,0 +1,11 @@
+if(__craylinux_crayprgenv_c)
+  return()
+endif()
+set(__craylinux_crayprgenv_c 1)
+
+include(Compiler/CrayPrgEnv)
+macro(__CrayPrgEnv_setup_C compiler_cmd link_cmd)
+  __CrayPrgEnv_setup(C
+${CMAKE_ROOT}/Modules/CMakeCCompilerABI.c
+${compiler_cmd} ${link_cmd})
+endmacro()
diff --git a/Modules/Compiler/CrayPrgEnv-CXX.cmake 
b/Modules/Compiler/CrayPrgEnv-CXX.cmake
new file mode 100644
index 000..aad85b6
--- /dev/null
+++ b/Modules/Compiler/CrayPrgEnv-CXX.cmake
@@ -0,0 +1,11 @@
+if(__craylinux_crayprgenv_cxx)
+  return()
+endif()
+set(__craylinux_crayprgenv_cxx 1)
+
+include(Compiler/CrayPrgEnv)
+macro(__CrayPrgEnv_setup_CXX compiler_cmd link_cmd)
+  __CrayPrgEnv_setup(CXX
+${CMAKE_ROOT}/Modules/CMakeCXXCompilerABI.cpp
+${compiler_cmd} ${link_cmd})
+endmacro()
diff --git a/Modules/Compiler/CrayPrgEnv-Cray-C.cmake 
b/Modules/Compiler/CrayPrgEnv-Cray-C.cmake
new file mode 100644
index 000..547a4b4
--- /dev/null
+++ b/Modules/Compiler/CrayPrgEnv-Cray-C.cmake
@@ -0,0 +1,7 @@
+if(__craylinux_crayprgenv_cray_c)
+  return()
+endif()
+set(__craylinux_crayprgenv_cray_c 1)
+
+include(Compiler/CrayPrgEnv-C)
+__CrayPrgEnv_setup_C("/opt/cray/cce/.*/ccfe" "/opt/cray/cce/.*/ld")
diff --git a/Modules/Compiler/CrayPrgEnv-Cray-CXX.cmake 
b/Modules/Compiler/CrayPrgEnv-Cray-CXX.cmake
new file mode 100644
index 000..df8452c
--- /dev/null
+++ b/Modules/Compiler/CrayPrgEnv-Cray-CXX.cmake
@@ -0,0 +1,7 @@
+if(__craylinux_crayprgenv_cray_cxx)
+  return()
+endif()
+set(__craylinux_crayprgenv_cray_cxx 1)
+
+include(Compiler/CrayPrgEnv-CXX)
+__CrayPrgEnv_setup_CXX("/opt/cray/cce/.*/ccfe" "/opt/cray/cce/.*/ld")
diff --git a/Modules/Compiler/CrayPrgEnv-Cray-Fortran.cmake 
b/Modules/Compiler/CrayPrgEnv-Cray-Fortran.cmake
new file mode 100644
index 000..9f46a04
--- /dev/null
+++ b/Modules/Compiler/CrayPrgEnv-Cray-Fortran.cmake
@@ -0,0 +1,7 @@
+if(__craylinux_crayprgenv_cray_fortran)
+  return()
+endif()
+set(__craylinux_crayprgenv_cray_fortran 1)
+
+include(Compiler/CrayPrgEnv-Fortran)
+__CrayPrgEnv_setup_Fortran("/opt/cray/cce/.*/ftnfe" "/opt/cray/cce/.*/ld")
diff --git a/Modules/Compiler/CrayPrgEnv-Fortran.cmake 
b/Modules/Compiler/CrayPrgEnv-Fortran.cmake
new file mode 100644
index 000..9c4d269
--- /dev/null
+++ b/Modules/Compiler/CrayPrgEnv-Fortran.cmake
@@ -0,0 +1,11 @@
+if(__craylinux_crayprgenv_fortran)
+  return()
+endif()
+set(__craylinux_crayprgenv_fortran 1)
+
+include(Compiler/CrayPrgEnv)
+macro(__CrayPrgEnv_setup_Fortran compiler_cmd link_cmd)
+  __CrayPrgEnv_setup(Fortran
+${CMAKE_ROOT}/Modules/CMakeFortranCompilerABI.F
+

[Cmake-commits] CMake branch, next, updated. v3.4.1-1655-g93c69b8

[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  93c69b8edc6c0b1a69cc995c0321cc275acdd3ee (commit)
   via  dc873f6eef1e6f952cf3d09be7568b03fbf8c6d3 (commit)
   via  ad1be6ee769ecaba4d6dadae84c0fc372049a333 (commit)
   via  27ed820c816a80bf140613cb2f47ccb2f21b021f (commit)
   via  3a824a963ac54930b072e2d31c54e182af3d027c (commit)
   via  c6eacfd56a9c5a8da2304c446230127b6ce42470 (commit)
  from  df5dbe2d51b9b88583792bdfe818c97e8a6474c8 (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=93c69b8edc6c0b1a69cc995c0321cc275acdd3ee
commit 93c69b8edc6c0b1a69cc995c0321cc275acdd3ee
Merge: df5dbe2 dc873f6
Author: Brad King 
AuthorDate: Wed Dec 9 08:37:14 2015 -0500
Commit: Brad King 
CommitDate: Wed Dec 9 08:37:14 2015 -0500

Merge branch 'master' into next


---

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.4.1-660-gad1be6e

[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  ad1be6ee769ecaba4d6dadae84c0fc372049a333 (commit)
   via  a7ef02253bf8ef33d4ffdd761802ea30ef289b8a (commit)
   via  0763a8365528166747746e3b94e74ca98d0d705f (commit)
   via  5eaac0c96ac51e1300664ef37239f3215bb58489 (commit)
  from  27ed820c816a80bf140613cb2f47ccb2f21b021f (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=ad1be6ee769ecaba4d6dadae84c0fc372049a333
commit ad1be6ee769ecaba4d6dadae84c0fc372049a333
Merge: 27ed820 a7ef022
Author: Brad King 
AuthorDate: Wed Dec 9 08:36:53 2015 -0500
Commit: CMake Topic Stage 
CommitDate: Wed Dec 9 08:36:53 2015 -0500

Merge topic 'detect-cray-wrappers'

a7ef0225 Cray: Refactor the Cray platform files to use compiler wrapper 
checks
0763a836 Cray: Add macro tests to detect the Cray compiler wrappers
5eaac0c9 Compiler: Add infrastructure for detecting compiler wrappers


---

Summary of changes:
 Modules/CMakeCCompiler.cmake.in |1 +
 Modules/CMakeCCompilerId.c.in   |7 ++
 Modules/CMakeCInformation.cmake |8 ++
 Modules/CMakeCXXCompiler.cmake.in   |1 +
 Modules/CMakeCXXCompilerId.cpp.in   |7 ++
 Modules/CMakeCXXInformation.cmake   |8 ++
 Modules/CMakeDetermineCompilerId.cmake  |6 +
 Modules/CMakeFortranCompiler.cmake.in   |1 +
 Modules/CMakeFortranCompilerId.F.in |3 +
 Modules/CMakeFortranInformation.cmake   |8 ++
 Modules/CMakeLanguageInformation.cmake  |   37 ++
 Modules/Compiler/CrayPrgEnv-C.cmake |   11 ++
 Modules/Compiler/CrayPrgEnv-CXX.cmake   |   11 ++
 Modules/Compiler/CrayPrgEnv-Cray-C.cmake|7 ++
 Modules/Compiler/CrayPrgEnv-Cray-CXX.cmake  |7 ++
 Modules/Compiler/CrayPrgEnv-Cray-Fortran.cmake  |7 ++
 Modules/Compiler/CrayPrgEnv-Fortran.cmake   |   11 ++
 Modules/Compiler/CrayPrgEnv-GNU-C.cmake |7 ++
 Modules/Compiler/CrayPrgEnv-GNU-CXX.cmake   |7 ++
 Modules/Compiler/CrayPrgEnv-GNU-Fortran.cmake   |7 ++
 Modules/Compiler/CrayPrgEnv-Intel-C.cmake   |7 ++
 Modules/Compiler/CrayPrgEnv-Intel-CXX.cmake |7 ++
 Modules/Compiler/CrayPrgEnv-Intel-Fortran.cmake |7 ++
 Modules/Compiler/CrayPrgEnv-PGI-C.cmake |7 ++
 Modules/Compiler/CrayPrgEnv-PGI-CXX.cmake   |7 ++
 Modules/Compiler/CrayPrgEnv-PGI-Fortran.cmake   |7 ++
 Modules/Compiler/CrayPrgEnv.cmake   |   83 +
 Modules/Platform/CrayLinuxEnvironment.cmake |   97 ++-
 Modules/Platform/CrayPrgEnv.cmake   |  149 ---
 29 files changed, 351 insertions(+), 182 deletions(-)
 create mode 100644 Modules/CMakeLanguageInformation.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-C.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-CXX.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-Cray-C.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-Cray-CXX.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-Cray-Fortran.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-Fortran.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-GNU-C.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-GNU-CXX.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-GNU-Fortran.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-Intel-C.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-Intel-CXX.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-Intel-Fortran.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-PGI-C.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-PGI-CXX.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv-PGI-Fortran.cmake
 create mode 100644 Modules/Compiler/CrayPrgEnv.cmake
 delete mode 100644 Modules/Platform/CrayPrgEnv.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.4.1-1658-g3b6d20b

[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  3b6d20b90ba55652b3bd3f75ceed4bc6a45286c4 (commit)
   via  7f4a91effc558b164bba6de78388543411541cf4 (commit)
   via  c185045515eaa9482bc29a0b325fde4f6490f5e1 (commit)
  from  93c69b8edc6c0b1a69cc995c0321cc275acdd3ee (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=3b6d20b90ba55652b3bd3f75ceed4bc6a45286c4
commit 3b6d20b90ba55652b3bd3f75ceed4bc6a45286c4
Merge: 93c69b8 7f4a91e
Author: Brad King 
AuthorDate: Wed Dec 9 08:57:57 2015 -0500
Commit: CMake Topic Stage 
CommitDate: Wed Dec 9 08:57:57 2015 -0500

Merge topic 'cmake-W-options' into next

7f4a91ef cmake: Deduplicate warning message control code
c1850455 cmake-gui: Add options to control warning messages


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7f4a91effc558b164bba6de78388543411541cf4
commit 7f4a91effc558b164bba6de78388543411541cf4
Author: Michael Scott 
AuthorDate: Sun Dec 6 12:58:24 2015 +
Commit: Brad King 
CommitDate: Wed Dec 9 08:56:17 2015 -0500

cmake: Deduplicate warning message control code

Remove the duplicate code in cmake::Configure to set the cache variables
for the warning message suppression.  Replace it with calls to the
dedicated methods to carry this out.

diff --git a/Source/cmake.cxx b/Source/cmake.cxx
index e57e512..7992495 100644
--- a/Source/cmake.cxx
+++ b/Source/cmake.cxx
@@ -1269,17 +1269,11 @@ int cmake::Configure()
 diagLevel = this->DiagLevels["deprecated"];
 if (diagLevel == DIAG_IGNORE)
   {
-  this->AddCacheEntry("CMAKE_WARN_DEPRECATED", "FALSE",
-  "Whether to issue warnings for deprecated "
-  "functionality.",
-  cmState::INTERNAL);
+  this->SetSuppressDeprecatedWarnings(true);
   }
 else if (diagLevel == DIAG_WARN)
   {
-  this->AddCacheEntry("CMAKE_WARN_DEPRECATED", "TRUE",
-  "Whether to issue warnings for deprecated "
-  "functionality.",
-  cmState::INTERNAL);
+  this->SetSuppressDeprecatedWarnings(false);
   }
 }
 
@@ -1299,32 +1293,20 @@ int cmake::Configure()
 diagLevel = this->DiagLevels["dev"];
 if (diagLevel == DIAG_IGNORE)
   {
-  this->AddCacheEntry("CMAKE_SUPPRESS_DEVELOPER_WARNINGS", "TRUE",
-  "Suppress Warnings that are meant for"
-  " the author of the CMakeLists.txt files.",
-  cmState::INTERNAL);
+  this->SetSuppressDevWarnings(true);
 
   if (setDeprecatedVariables)
 {
-this->AddCacheEntry("CMAKE_WARN_DEPRECATED", "FALSE",
-"Whether to issue warnings for deprecated "
-"functionality.",
-cmState::INTERNAL);
+this->SetSuppressDeprecatedWarnings(true);
 }
   }
 else if (diagLevel == DIAG_WARN)
   {
-  this->AddCacheEntry("CMAKE_SUPPRESS_DEVELOPER_WARNINGS", "FALSE",
-  "Suppress Warnings that are meant for"
-  " the author of the CMakeLists.txt files.",
-  cmState::INTERNAL);
+  this->SetSuppressDevWarnings(false);
 
   if (setDeprecatedVariables)
 {
-this->AddCacheEntry("CMAKE_WARN_DEPRECATED", "TRUE",
-"Whether to issue warnings for deprecated "
-"functionality.",
-cmState::INTERNAL);
+this->SetSuppressDeprecatedWarnings(false);
 }
   }
 }
@@ -2881,6 +2863,24 @@ void cmake::RunCheckForUnusedVariables()
 #endif
 }
 
+bool cmake::GetSuppressDevWarnings(cmMakefile const* mf)
+{
+  /*
+   * The suppression CMake variable may be set in the CMake configuration file
+   * itself, so we have to check what its set to in the makefile if we can.
+   */
+  if (mf)
+{
+return mf->IsOn("CMAKE_SUPPRESS_DEVELOPER_WARNINGS");
+}
+  else
+{
+const char* cacheEntryValue = this->State->GetCacheEntryValue(
+  "CMAKE_SUPPRESS_DEVELOPER_WARNINGS");
+return cmSystemTools::IsOn(cacheEntryValue);
+}
+}
+
 void cmake::SetSuppressDevWarnings(bool b)
 {
   std::string value;
@@ -2902,24 +2902,6 @@ void cmake::SetSuppressDevWarnings(bool b)
   cmState::INTERNAL);
 }
 
-bool cmake::GetSuppressDevWarnings(cmMakefile const* mf)
-{
-  /*
-   * The 

Re: [cmake-developers] [CMake][PATCH] AIX RPATH handling

[Brad King]

On 12/09/2015 09:09 AM, CHEVRIER, Marc wrote:
> You are right. I missed this capability.
> My first idea was to apply to exec the same approach as for shared lib but I 
> didn’t found appropriate variable: something like 
> CMAKE_EXE_CREATE__FLAGS
> Or may be CMAKE_EXE_LINKER_FLAGS_INIT can be used but I am not sure of the 
> usage of the *_INIT variables.

Actually the old code has it in two places:

> - set(CMAKE_SHARED_LIBRARY_CREATE_${lang}_FLAGS "-G -Wl,-bnoipath") # -shared
> - set(CMAKE_SHARED_LIBRARY_LINK_${lang}_FLAGS "-Wl,-brtl,-bnoipath,-bexpall") 
> # +s, flag for exe link to use shared lib

The CREATE_ value is used when linking a shared library itself.
The LINK_ value is used to link executables.  Both should already
be getting the flag with no changes.

-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] Parallel jobs failed for cmake

[Igor Sobinov]

 Hello,

I compiled cmake based project with -jN option, but failed: I got the following 
error:

make[4]: warning: jobserver unavailable: using -j1.  Add `+' to parent make 
rule.

How to make cmake to compile with multiple targets?

Bye, Igor
-- 

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] Proposal to teach cmDepends to only take dependencies from the source tree

[Ben Boeckel]

On Wed, Dec 09, 2015 at 09:19:45 +0100, Attila Krasznahorkay wrote:
> I myself am on the side of simplicity. Using regular expressions would
> allow us to do what I want. But if >95% of the people using this new
> possibility would use it exactly like I plan to, then implementing it
> in a more complicated way than necessary would just be a bad design
> choice.

Do you have performance numbers for the change in your build between
using include_directories (or target_include_directories), with and
without SYSTEM, each with and without this change?

--Ben
-- 

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.4.1-665-gdc873f6

[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  dc873f6eef1e6f952cf3d09be7568b03fbf8c6d3 (commit)
   via  bc35087da3eb9039dad8fb5d27c1fab60b43f776 (commit)
   via  98be140fc0dc0bab8955c4fea9274ea52ac8cd9c (commit)
   via  93cc80aee59cfb328d541ba527d40239ab8348b1 (commit)
   via  0903812b0b8c325913d766b793bbf9438ad6b423 (commit)
  from  ad1be6ee769ecaba4d6dadae84c0fc372049a333 (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=dc873f6eef1e6f952cf3d09be7568b03fbf8c6d3
commit dc873f6eef1e6f952cf3d09be7568b03fbf8c6d3
Merge: ad1be6e bc35087
Author: Brad King 
AuthorDate: Wed Dec 9 08:36:56 2015 -0500
Commit: CMake Topic Stage 
CommitDate: Wed Dec 9 08:36:56 2015 -0500

Merge topic 'cmake-E-copy-multiple-inputs'

bc35087d cmake: Teach -E copy_directory to support multiple input 
directories
98be140f cmake: Refine -E copy[_if_different] documentation
93cc80ae cmake: Refine -E copy_if_different implementation indentation
0903812b cmake: Refine -E chdir documentation


---

Summary of changes:
 Help/manual/cmake.1.rst|   14 ++---
 Help/release/dev/cmake-E-copy-multiple-inputs.rst  |3 ++
 Source/cmcmd.cxx   |   30 
 ...ee-source-files-target-is-directory-result.txt} |0
 ...ree-source-files-target-is-directory-stderr.txt |0
 ...y-three-source-files-target-is-file-result.txt} |0
 ...ry-three-source-files-target-is-file-stderr.txt |3 ++
 ...ee-source-files-target-is-not-exist-result.txt} |0
 ...ree-source-files-target-is-not-exist-stderr.txt |0
 Tests/RunCMake/CommandLine/RunCMakeTest.cmake  |   17 +++
 .../RunCMake/CommandLine/copy_input/d1/d1.txt  |0
 .../RunCMake/CommandLine/copy_input/d2/d2.txt  |0
 .../RunCMake/CommandLine/copy_input/d3/d3.txt  |0
 13 files changed, 51 insertions(+), 16 deletions(-)
 copy Tests/RunCMake/{CMP0022/CMP0022-WARN-empty-old-result.txt => 
CommandLine/E_copy_directory-three-source-files-target-is-directory-result.txt} 
(100%)
 copy Modules/IntelVSImplicitPath/hello.f => 
Tests/RunCMake/CommandLine/E_copy_directory-three-source-files-target-is-directory-stderr.txt
 (100%)
 copy Tests/RunCMake/{CMP0004/CMP0004-NEW-result.txt => 
CommandLine/E_copy_directory-three-source-files-target-is-file-result.txt} 
(100%)
 create mode 100644 
Tests/RunCMake/CommandLine/E_copy_directory-three-source-files-target-is-file-stderr.txt
 copy Tests/RunCMake/{CMP0022/CMP0022-WARN-empty-old-result.txt => 
CommandLine/E_copy_directory-three-source-files-target-is-not-exist-result.txt} 
(100%)
 copy Modules/IntelVSImplicitPath/hello.f => 
Tests/RunCMake/CommandLine/E_copy_directory-three-source-files-target-is-not-exist-stderr.txt
 (100%)
 copy Modules/IntelVSImplicitPath/hello.f => 
Tests/RunCMake/CommandLine/copy_input/d1/d1.txt (100%)
 copy Modules/IntelVSImplicitPath/hello.f => 
Tests/RunCMake/CommandLine/copy_input/d2/d2.txt (100%)
 copy Modules/IntelVSImplicitPath/hello.f => 
Tests/RunCMake/CommandLine/copy_input/d3/d3.txt (100%)


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

Re: [cmake-developers] [CMake][PATCH] AIX RPATH handling

[Brad King]

On 12/09/2015 08:02 AM, CHEVRIER, Marc wrote:
> Attached is a patch for AIX enabling correct generation of executables
> regarding runtime path handling (currently, build paths could be stored
> as part of installed executables): option -bnoipath is required for
> executables link command (currently, only shared libs link command
> get -bnoipath option).

Thanks.  I agree that -bnoipath should be used for all linking because
we never want the path to a library file to be encoded in its dependents.
However, the proposed patch moves the flag over to the flags used to
specify the RPATH.  These may not be used if CMAKE_SKIP_RPATH or similar
options are enabled.  We should find another place for the flag that
is always used for both shared libraries and executables.

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-developers

Re: [cmake-developers] Add command line options for deprecation message control

[Brad King]

On 12/07/2015 01:51 PM, Michael Scott wrote:
>> I noticed one glitch.  I built against Qt 5.5.1 on Linux and the
>> option dialog seems to truncate the labels.
> I think I've fixed it, by using vertical layouts rather than form 
> layouts and setting the size policy to expanding for the widgets, if 
> that doesn't fix I'll need to look into QT in more depth as I've not got 
> much experience with it. Which Linux distro did you notice it in, looks 
> like gnome3?

It is Debian 'testing' with KDE 5.  Your changes fixed it for me.

> Patches for the fix are attached.

Thanks.  Applied with slightly modified commit messages and
merged to 'next' for testing:

 cmake-gui: Add options to control warning messages
 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c1850455

 cmake: Deduplicate warning message control code
 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7f4a91ef

-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

Re: [cmake-developers] Keil Armcc support

[Brad King]

On 12/09/2015 06:25 AM, yann suisini wrote:
> Is theresomme support planned in a near future for the
> Keil / Armcc toolchain ? 

This was contributed recently:

 Add support for the ARM Compiler (arm.com)
 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=035a658f

 http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/14786

Please try it out from the development version to see how it goes.

-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

Re: [CMake] Parallel jobs failed for cmake

[Richard Shaw]

On Wed, Dec 9, 2015 at 7:32 AM, Igor Sobinov  wrote:

> Hello,
>
> I compiled cmake based project with -jN option, but failed: I got the
> following error:
>
> make[4]: warning: jobserver unavailable: using -j1.  Add `+' to parent
> make rule.
>
> How to make cmake to compile with multiple targets?
>

Are you using the ExternalProject module? A little more detail would be
helpful.

Thanks,
Richard
-- 

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] [CMake][PATCH] AIX RPATH handling

[CHEVRIER, Marc]

Oops !
You are right, on a simple example, all is OK. So the problem seems on my side.
I will investigate this curious behaviour…

Sorry for the noise.

Marc




On 09/12/15 15:15, "Brad King"  wrote:

>On 12/09/2015 09:09 AM, CHEVRIER, Marc wrote:
>> You are right. I missed this capability.
>> My first idea was to apply to exec the same approach as for shared lib but I 
>> didn’t found appropriate variable: something like 
>> CMAKE_EXE_CREATE__FLAGS
>> Or may be CMAKE_EXE_LINKER_FLAGS_INIT can be used but I am not sure of the 
>> usage of the *_INIT variables.
>
>Actually the old code has it in two places:
>
>> - set(CMAKE_SHARED_LIBRARY_CREATE_${lang}_FLAGS "-G -Wl,-bnoipath") # -shared
>> - set(CMAKE_SHARED_LIBRARY_LINK_${lang}_FLAGS 
>> "-Wl,-brtl,-bnoipath,-bexpall") # +s, flag for exe link to use shared lib
>
>The CREATE_ value is used when linking a shared library itself.
>The LINK_ value is used to link executables.  Both should already
>be getting the flag with no changes.
>
>-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] How to select components by default using CPack ?

[David Demelier]

Hello,

I'm trying to create a tree of components like this:

- plugins
  | - a
  | - b

Where the user can select plugins to select all children or manually 
select a, b.


I can get the selection of that component tree but unable to mark them 
selected by default using CPackIFW. This is my current CMakeLists.txt:




cmake_minimum_required(VERSION 3.2)
project(test)

set(CPACK_PACKAGE_NAME Hello)
set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "Hello world using IFW")
set(CPACK_PACKAGE_VERSION "1.0.0")
set(CPACK_GENERATOR "IFW")

set(PLUGINS one two)

foreach (plugin ${PLUGINS})
install(
FILES ${plugin}.js
COMPONENT plugin_${plugin}
DESTINATION plugins
)

list(APPEND CPACK_COMPONENTS_ALL plugin_${plugin})
endforeach ()

include(CPack)
include(CPackIFW)

cpack_add_component_group(plugins)

foreach (plugin ${PLUGINS})
cpack_add_component_group(
plugin_group_${plugin}
PARENT_GROUP plugins
DISPLAY_NAME "${plugin}"
DESCRIPTION "Install ${plugin}.js"
)

cpack_add_component(plugin_${plugin} GROUP plugin_group_${plugin})
endforeach ()



The CMakeLists.txt just expect to have one.js and two.js in the 
top-level directory. Can you please tell me what I'm doing wrong?


Regards,

--
David Demelier

--

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] Parallel jobs failed for cmake

[J Decker]

On Wed, Dec 9, 2015 at 5:32 AM, Igor Sobinov  wrote:
> Hello,
>
> I compiled cmake based project with -jN option, but failed: I got the
> following error:
>
> make[4]: warning: jobserver unavailable: using -j1.  Add `+' to parent make
> rule.
>

That is actually only a warning

‘warning: jobserver unavailable: using -j1. Add `+' to parent make rule.’

In order for make processes to communicate, the parent will pass
information to the child. Since this could result in problems if the
child process isn’t actually a make, the parent will only do this if
it thinks the child is a make. The parent uses the normal algorithms
to determine this (see How the MAKE Variable Works). If the makefile
is constructed such that the parent doesn’t know the child is a make
process, then the child will receive only part of the information
necessary. In this case, the child will generate this warning message
and proceed with its build in a sequential manner.


Probably you're building on windows; which doesn't do 'fork' so it's
not possible to parallel make, and you'll have to suffer with
single-target makes.

It's slower but doesn't cause 'issues'.  Maybe grab Visual Studio
community edition target that instead which is able to parallel
make... I think Ninja handles parallel makes also(?).



> How to make cmake to compile with multiple targets?
>
> Bye, Igor
>
> --
>
> 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-developers] [CMake][PATCH] AIX RPATH handling

[CHEVRIER, Marc]

You are right. I missed this capability.
My first idea was to apply to exec the same approach as for shared lib but I 
didn’t found appropriate variable: something like CMAKE_EXE_CREATE__FLAGS
Or may be CMAKE_EXE_LINKER_FLAGS_INIT can be used but I am not sure of the 
usage of the *_INIT variables.

Marc




On 09/12/15 15:00, "Brad King"  wrote:

>On 12/09/2015 08:02 AM, CHEVRIER, Marc wrote:
>> Attached is a patch for AIX enabling correct generation of executables
>> regarding runtime path handling (currently, build paths could be stored
>> as part of installed executables): option -bnoipath is required for
>> executables link command (currently, only shared libs link command
>> get -bnoipath option).
>
>Thanks.  I agree that -bnoipath should be used for all linking because
>we never want the path to a library file to be encoded in its dependents.
>However, the proposed patch moves the flag over to the flags used to
>specify the RPATH.  These may not be used if CMAKE_SKIP_RPATH or similar
>options are enabled.  We should find another place for the flag that
>is always used for both shared libraries and executables.
>
>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-developers

[CMake] Toolset target property?

[Robert Dailey]

Doesn't look like there is a Toolset target property anywhere. You can
set it from the command line, but I think setting a toolset per target
makes sense. Considering the direction that Visual Studio 2015 is
headed. For example Microsoft has a Clang compiler with MS CodeGen.
They recommend using this toolset with the platform agnostic targets,
and using normal MSVC with windows-specific targets (for example, CLR
projects).

This requires setting a toolset per target. Does this feature make
sense from the CMake perspective?
-- 

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] CPack and PackageMaker

[Robert Bielik]

Mac OSX:

Since PackageMaker has been deprecated by Apple, the new tools to use 
are pkgbuild [1] and productbuild [2].


Simple question: Is there any work being done by the CMake community on 
a new OS X CPack backend to support the above tools ?


Regards
/Robert
[1] 
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/pkgbuild.1.html
[2] 
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/productbuild.1.html


--

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.4.1-1660-g11039e0

[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  11039e0002bd03eccaee930d308b1afd5dcf3a9b (commit)
   via  d462ac27d814e966c54bb638444e4b125d1d665f (commit)
  from  3b6d20b90ba55652b3bd3f75ceed4bc6a45286c4 (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=11039e0002bd03eccaee930d308b1afd5dcf3a9b
commit 11039e0002bd03eccaee930d308b1afd5dcf3a9b
Merge: 3b6d20b d462ac2
Author: Brad King 
AuthorDate: Wed Dec 9 11:40:35 2015 -0500
Commit: CMake Topic Stage 
CommitDate: Wed Dec 9 11:40:35 2015 -0500

Merge topic 'cmELF-use-KWIML' into next

d462ac27 cmELF: Use KWIML ABI.h header to get endian-ness


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d462ac27d814e966c54bb638444e4b125d1d665f
commit d462ac27d814e966c54bb638444e4b125d1d665f
Author: Brad King 
AuthorDate: Wed Dec 9 11:38:10 2015 -0500
Commit: Brad King 
CommitDate: Wed Dec 9 11:38:10 2015 -0500

cmELF: Use KWIML ABI.h header to get endian-ness

Port away from KWSys CPU header.

diff --git a/Source/cmELF.cxx b/Source/cmELF.cxx
index 37dd328..fda6e02 100644
--- a/Source/cmELF.cxx
+++ b/Source/cmELF.cxx
@@ -16,8 +16,7 @@
 #include 
 
 // Need the native byte order of the running CPU.
-#define cmsys_CPU_UNKNOWN_OKAY // We can decide at runtime if not known.
-#include 
+#include 
 
 // Include the ELF format information system header.
 #if defined(__OpenBSD__)
@@ -102,9 +101,9 @@ public:
 // In most cases the processor-specific byte order will match that
 // of the target execution environment.  If we choose wrong here
 // it is fixed when the header is read.
-#if cmsys_CPU_ENDIAN_ID == cmsys_CPU_ENDIAN_ID_LITTLE
+#if cmIML_ABI_ENDIAN_ID == cmIML_ABI_ENDIAN_ID_LITTLE
 this->NeedSwap = (this->ByteOrder == ByteOrderMSB);
-#elif cmsys_CPU_ENDIAN_ID == cmsys_CPU_ENDIAN_ID_BIG
+#elif cmIML_ABI_ENDIAN_ID == cmIML_ABI_ENDIAN_ID_BIG
 this->NeedSwap = (this->ByteOrder == ByteOrderLSB);
 #else
 this->NeedSwap = false; // Final decision is at runtime anyway.

---

Summary of changes:
 Source/cmELF.cxx |7 +++
 1 file changed, 3 insertions(+), 4 deletions(-)


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

Re: [CMake] Idea: generic task-driven make-like targets with CMake

[Kevin Wojniak]

Looks interesting Tamas! Too bad shell scripts don’t work natively on 
Windows :)


Kevin



On 8 Dec 2015, at 16:59, Tamás Kenéz wrote:


Kevin, I have a shell script for such tasks, see
https://gist.github.com/tamaskenez/d4509f240f4224eb9853. Feel free to 
use

it if that's what you need.
It extends the `cmake` command by executing multiple, related `cmake` 
calls

with one command. See docs in gist.

Your 'make release' example looks like this:

 cmakex cr -Hsourcedir -Bbuilddir # Configure Release

with additional options you can do many tasks with one command

 cmakex cbitdr -Hsourcedir -Bbuilddir -GXcode # Configure, Build,
Install, Test Debug & Release using Xcode

Tamas

On Tue, Dec 8, 2015 at 7:44 PM, Kevin Wojniak  
wrote:


Functionality like add_custom_target combined with script mode is 
close,
but not quite there. add_custom_target already requires a build 
directory
and a generator, so it’s too late. Script mode requires setting 
variables

on the command line, so it’s too verbose. For example:

if(“${ACTION}” STREQUAL “release”)
 execute_process(…)
endif()

cmake -P myscript.cmake -DACTION=release

I suppose you could have multiple *.cmake files for each task, and 
those
could then call the master file with necessary variables set, but 
then

you’d need one file per task and that could become excessive.

Kevin



On 8 Dec 2015, at 10:22, Nils Gladitz wrote:

On 08.12.2015 19:04, Kevin Wojniak wrote:




add_task(release
COMMAND ${CMAKE_COMMAND} -E make_directory “build_dir”
COMMAND ${CMAKE_COMMAND} -E chdir “build_dir” ${CMAKE_COMMAND}
“-DCMAKE_BUILD_TYPE=Release”, “..”
)



There is add_custom_target().

You can e.g. add_custom_target(release ${CMAKE_COMMAND} -E echo 
foobar)

and with the Makefiles generator run "make release" and with visual
studio trigger the build of the "release" project.

For scripting you can use cmake in script mode with -P.

e.g. given a script file release.cmake:
message("Hello World")

add_custom_target(release ${CMAKE_COMMAND} -P
${CMAKE_CURRENT_SOURCE_DIR}/release.cmake)

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


--

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 target_link_libraries() items should be quoted or not? Linux/Ubuntu 14.04 cmake 3.4.1

[Normand Robert]

Reading docs trying to understand why my build works when I write

target_link_libraries(Debug ${VTK_LIBRARIES} -lsri-spatialfft 
-lsri-spatial -lsri-memory)


but does not work when everything is protected in quotes:

target_link_libraries(Debug "${VTK_LIBRARIES} -lsri-spatialfft 
-lsri-spatial -lsri-memory")


which causes an extra library which does not exist to be passed to the 
linker. Is this expected behaviour?


robert@kalymnos:~/Code/Debug/normandBuild$ cmake --version
cmake version 3.4.1

--
Normand Robert PhD
Sunnybrook Health Sciences Centre
Room S632, 2075 Bayview Avenue, Toronto, ON M4N 3M5

--

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 target_link_libraries items should be quoted or not? Linux/Ubuntu 14.04 cmake 3.4.1

[Normand Robert]

robert@kalymnos:~/Code/Debug/normandBuild$ cmake --version
cmake version 3.4.1

Reading docs trying to understand why my build works when I write

target_link_libraries(Debug ${VTK_LIBRARIES} -lsri-spatialfft 
-lsri-spatial -lsri-memory)


but not when everything is protected in quotes:

target_link_libraries(Debug "${VTK_LIBRARIES} -lsri-spatialfft 
-lsri-spatial -lsri-memory")


which causes an extra library which does not exist to be passed to the 
linker. Is this expected behaviour?


--
Normand Robert PhD
Sunnybrook Health Sciences Centre
Room S632, 2075 Bayview Avenue, Toronto, ON M4N 3M5

--

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] To Post to the "CMake" Mailing List

[Humberto H`]

Hi,Please, I would like to be able to post to the "CMake" mailing list. Thank you.Humberto Leon-Bermudez
-- 

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] Idea: generic task-driven make-like targets with CMake

[Tamás Kenéz]

[getting offtopic] Well, not because of this script but for any serious
development on Windows I think it's a good idea to use the *nix shell
provided by the Windows Git installation, it feels quite native. Together
with cbucher's ConsoleZ you get a very convenient environment for
cmake/command-line centered development, even when working with VS IDE.

On Wed, Dec 9, 2015 at 6:43 PM, Kevin Wojniak  wrote:

> Looks interesting Tamas! Too bad shell scripts don’t work natively on
> Windows :)
>
> Kevin
>
>
>
>
> On 8 Dec 2015, at 16:59, Tamás Kenéz wrote:
>
> Kevin, I have a shell script for such tasks, see
>> https://gist.github.com/tamaskenez/d4509f240f4224eb9853. Feel free to use
>> it if that's what you need.
>> It extends the `cmake` command by executing multiple, related `cmake`
>> calls
>> with one command. See docs in gist.
>>
>> Your 'make release' example looks like this:
>>
>>  cmakex cr -Hsourcedir -Bbuilddir # Configure Release
>>
>> with additional options you can do many tasks with one command
>>
>>  cmakex cbitdr -Hsourcedir -Bbuilddir -GXcode # Configure, Build,
>> Install, Test Debug & Release using Xcode
>>
>> Tamas
>>
>> On Tue, Dec 8, 2015 at 7:44 PM, Kevin Wojniak 
>> wrote:
>>
>> Functionality like add_custom_target combined with script mode is close,
>>> but not quite there. add_custom_target already requires a build directory
>>> and a generator, so it’s too late. Script mode requires setting variables
>>> on the command line, so it’s too verbose. For example:
>>>
>>> if(“${ACTION}” STREQUAL “release”)
>>>  execute_process(…)
>>> endif()
>>>
>>> cmake -P myscript.cmake -DACTION=release
>>>
>>> I suppose you could have multiple *.cmake files for each task, and those
>>> could then call the master file with necessary variables set, but then
>>> you’d need one file per task and that could become excessive.
>>>
>>> Kevin
>>>
>>>
>>>
>>> On 8 Dec 2015, at 10:22, Nils Gladitz wrote:
>>>
>>> On 08.12.2015 19:04, Kevin Wojniak wrote:
>>>


> add_task(release
> COMMAND ${CMAKE_COMMAND} -E make_directory “build_dir”
> COMMAND ${CMAKE_COMMAND} -E chdir “build_dir” ${CMAKE_COMMAND}
> “-DCMAKE_BUILD_TYPE=Release”, “..”
> )
>
>
> There is add_custom_target().

 You can e.g. add_custom_target(release ${CMAKE_COMMAND} -E echo foobar)
 and with the Makefiles generator run "make release" and with visual
 studio trigger the build of the "release" project.

 For scripting you can use cmake in script mode with -P.

 e.g. given a script file release.cmake:
 message("Hello World")

 add_custom_target(release ${CMAKE_COMMAND} -P
 ${CMAKE_CURRENT_SOURCE_DIR}/release.cmake)

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

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-developers] set(CACHE) and the local scope

[Ben Boeckel]

Hi,

So some behavior I was unaware of until today came up:

set(var ON)
option(var "description" OFF)
message("var: ${var}")

outputs "OFF" for the first configure and "ON" for subsequent
configures. This is because set(var CACHE) does unset(var) *if* the
cache was touched. This is not done on the second time around since it
is already in the cache.

I think a policy to remove the unset(var) behavior should be added since
the current behavior means that clean builds can be wildly different
than incremental builds.

Related, I have a branch on the stage (update-variable-docs) which
attempts to clarify some darker corners of the set() command and the
*VARIABLES directory properties.

Thoughts on the documentation updates and the policy?

Thanks,

--Ben
-- 

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-developers] [CMake 0015876]: "Cannot restore timestamp"

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=15876 
== 
Reported By:A. Jesse Jiryu Davis
Assigned To:
== 
Project:CMake
Issue ID:   15876
Category:   CMake
Reproducibility:random
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2015-12-09 15:38 EST
Last Modified:  2015-12-09 15:38 EST
== 
Summary:"Cannot restore timestamp"
Description: 
Appears that bug http://public.kitware.com/Bug/view.php?id=13639 wasn't
completely fixed, or has experienced a regression. With CMake 3.2.2 I very
occasionally see this error at the end of an otherwise successful build on
Windows:

CUSTOMBUILD : CMake error : Cannot restore timestamp CMakeFiles\generate.stamp

Steps to Reproduce: 
CMakeLists.txt with multiple add_library commands.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-12-09 15:38 A. Jesse Jiryu DavisNew 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

Re: [CMake] target_include_directories SYSTEM adds -isystem to Clang, but not GCC

[Gregor Jasny via CMake]

On 08/12/15 20:21, digitalriptide wrote:
> Thank you Gregor! I have tried the Makefile generator, but on OS X -isystem
> still seems to be missing with GCC. The -isystem flag appears with Clang,
> however. I have installed CMake 3.4.1 and GCC 5.3.0, both through MacPorts.
> I can provide a sample project, if that would help.

Please file a bug report and attach your test case. That way it does not
get lost.

Thanks,
Gregor

-- 

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] organizing includes statements

[Owen Alanzo Hogarth]

hi

I am building a shared library project that's composed of many smaller
shared library files.

Here's the main shared library project and a list of all the sub projects.

SET(HEADER_FILES ${CMAKE_CURRENT_SOURCE_DIR}/headers/main_lib.h)
SET(SRC_FILES ${CMAKE_CURRENT_SOURCE_DIR}/main_lib.c)
SET(TARGET_LIBS core_math point2d line2d quad2d timer_utils)

ADD_LIBRARY(main_lib SHARED ${SRC_FILES} ${HEADER_FILES})
TARGET_LINK_LIBRARIES(core_engine ${TARGET_LIBS})

i have each module setup like this.
module
module/headers/module.h
module/module.c

then the module.c will look like this
#include "headers/module.h"

the file main_lib.h depends on all those target libs, which makes my
main_lib.h file's include statement look like this

#include "../../module/headers/module.h"
#include "../../module1/headers/module1.h"
#include "../../module2/headers/module2.h"


is there any way that I can clean up these includes?

For example if I want to use io functions I can just do #include 
or #include 

for math functions.

I would like to make my include statements not relative to the files actual
location, the way it's currently hard coded.
-- 

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] How to set environment variables with spaces in commands

[Qingping Hou]

Hi all,

I am trying to setup an ExternalProject in cmake but got stuck in the
configuration step. I am using ccache to speed up the compilation:

```
ExternalProject_Add(
  ...
  CONFIGURE_COMMAND CC="ccache arm-linux-gnueabihf-gcc" ./configure
  ...
)
```

However, when cmake generates the Makefile, it moves the quotes around
and breaks the command:

```
"CC=ccache arm-linux-gnueabihf-gcc" ./configure
```

I have tried various escaping method to try to get it work properly
without any luck. Is this a bug or an unintended feature?

Thanks,
QP
-- 

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] How to set environment variables with spaces in commands

[Attila Krasznahorkay]

Hi QP,

Probably not the intended solution, but what I’m doing in such cases is that in 
a patch step I create a shell script that does the configuration for me. With 
all the environment settings and everything. Like:

PATCH_COMMAND ${CMAKE_COMMAND} -E echo “cd someDir/; CC=\”something\” 
./configure” > configure.sh
CONFIGURE_COMMAND sh configure.sh

Unfortunately this makes the code quite unportable, as it will only work on 
POSIX platforms like this. But I guess that’s the case anyway once you start 
setting environment variables.

Cheers,
   Attila

P.S. I often create build.sh and install.sh scripts as well in additional patch 
commands.

> On Dec 10, 2015, at 5:35 AM, Qingping Hou  wrote:
> 
> Hi all,
> 
> I am trying to setup an ExternalProject in cmake but got stuck in the
> configuration step. I am using ccache to speed up the compilation:
> 
> ```
> ExternalProject_Add(
>  ...
>  CONFIGURE_COMMAND CC="ccache arm-linux-gnueabihf-gcc" ./configure
>  ...
> )
> ```
> 
> However, when cmake generates the Makefile, it moves the quotes around
> and breaks the command:
> 
> ```
> "CC=ccache arm-linux-gnueabihf-gcc" ./configure
> ```
> 
> I have tried various escaping method to try to get it work properly
> without any luck. Is this a bug or an unintended feature?
> 
> Thanks,
> QP
> -- 
> 
> 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-developers] Please comment on ios-universal topic

[Gregor Jasny via cmake-developers]

Hello,

On 09/12/15 10:21, Ruslan Baratov wrote:

IOS_INSTALL_COMBINED_BINARY


Just to clarify you want to leave only one variable
IOS_INSTALL_COMBINED_BINARY for the device + simulator on iOS platforms.
Other platforms (in future) will be controlled by using *_ARCHITECTURES
variables, right?


Right. Any objections to that property name?

Thanks,
Gregor
--

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.4.1-666-ga657b32

[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  a657b324822b5bd549706b337a74fa3bfd7bc1c6 (commit)
  from  dc873f6eef1e6f952cf3d09be7568b03fbf8c6d3 (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=a657b324822b5bd549706b337a74fa3bfd7bc1c6
commit a657b324822b5bd549706b337a74fa3bfd7bc1c6
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Thu Dec 10 00:01:06 2015 -0500
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Thu Dec 10 00:01:06 2015 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index c24341f..fab29ab 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 4)
-set(CMake_VERSION_PATCH 20151209)
+set(CMake_VERSION_PATCH 20151210)
 #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

Re: [CMake] organizing includes statements

[Attila Krasznahorkay]

Hi Owen,

This seems like a textbook example of using target_include_directories(…) with 
generator expressions. Let’s take the example where:

lib1/headers/lib1.h
lib1/lib1.c
lib2/headers/lib2.h
lib2/lib2.c

If you want to be able to include lib1.h and lib2.h with simply

#include “lib1.h”

and

#include “lib2.h”

in your user code, and in the library code itself, you’d do something like:

add_library( lib1 SHARED lib1/lib1.c )
target_include_directories( lib1 PUBLIC
   $
   $ )

add_library( lib2 SHARED lib2/lib2.c )
target_include_directories( lib2 PUBLIC
   $
   $ )
target_link_libraries( lib2 lib1 )

install( FILES lib1/headers/lib1.h lib2/headers/lib2.h DESTINATION include )
install( TARGETS lib1 lib2 DESTINATION lib )

In this setup “lib1” should get a -I${CMAKE_SOURCE_DIR}/lib1/headers flag, and 
“lib2” should get both -I${CMAKE_SOURCE_DIR}/lib1/headers and 
-I${CMAKE_SOURCE_DIR}/lib2/headers. Finally the headers both get installed into 
the same include directory, so an outside user will just have to be able to 
find that one directory. (Or if you export CMake’s targets, the lib1/2 imported 
targets will know that their header files are in that directory.)

Cheers,
Attila

> On Dec 10, 2015, at 12:07 AM, Owen Alanzo Hogarth  wrote:
> 
> hi
> 
> I am building a shared library project that's composed of many smaller shared 
> library files.
> 
> Here's the main shared library project and a list of all the sub projects.
> 
> SET(HEADER_FILES ${CMAKE_CURRENT_SOURCE_DIR}/headers/main_lib.h)
> SET(SRC_FILES ${CMAKE_CURRENT_SOURCE_DIR}/main_lib.c)
> SET(TARGET_LIBS core_math point2d line2d quad2d timer_utils)
> 
> ADD_LIBRARY(main_lib SHARED ${SRC_FILES} ${HEADER_FILES})
> TARGET_LINK_LIBRARIES(core_engine ${TARGET_LIBS})
> 
> i have each module setup like this.
> module
> module/headers/module.h
> module/module.c
> 
> then the module.c will look like this
> #include "headers/module.h"
> 
> the file main_lib.h depends on all those target libs, which makes my 
> main_lib.h file's include statement look like this
> 
> #include "../../module/headers/module.h"
> #include "../../module1/headers/module1.h"
> #include "../../module2/headers/module2.h"
> 
> 
> is there any way that I can clean up these includes?
> 
> For example if I want to use io functions I can just do #include  or 
> #include 
> 
> for math functions.
> 
> I would like to make my include statements not relative to the files actual 
> location, the way it's currently hard coded.
> -- 
> 
> 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] How to set _default_ timeout for the ctest command?

[Alan W. Irwin]

On 2015-12-09 09:23+0100 Marcel Loose wrote:


Hi Alan,

Just by experimenting, I discovered that you also need to set
DART_TESTING_TIMEOUT. I'm not sure what the relationship (if any) is
between CTEST_TEST_TIMEOUT and DART_TESTING_TIMEOUT. I set them both in
the file CTestConfig.cmake. I get the feeling that DART_TESTING_TIMEOUT
is there for less than historic reasons. Maybe someone from Kitware can
shed a light on this.


Thanks, Marcel, for trying those experiments.

I tried some additional experiments and found that all that is needed is
to set the CTEST_TEST_TIMEOUT value before CTest is included in my
top-level CMakeLists.txt file.  (My previous experiment set that value
after the include, but before the first add_test command.) Note that
I do not use CTestConfig.cmake at all.

So the current experimental logic is
# Control the default timeout for all ctests.
set(CTEST_TEST_TIMEOUT 1)
include(CTest)

Those commands generate the following timeout results in the build tree.

software@raven> find . -type f |xargs grep -i timeout
./CMakeCache.txt:DART_TESTING_TIMEOUT:STRING=1
./CMakeCache.txt://ADVANCED property for variable: DART_TESTING_TIMEOUT
./CMakeCache.txt:DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1
./DartConfiguration.tcl:# TimeOut is the amount of time in seconds to wait for 
processes
./DartConfiguration.tcl:# to complete during testing.  After TimeOut seconds, 
the
./DartConfiguration.tcl:TimeOut: 1
./DartConfiguration.tcl:# For CTest submissions that timeout, these options

So for this case, DART_TESTING_TIMEOUT is automatically set to the
specified CTEST_TEST_TIMEOUT value.  (If CTEST_TEST_TIMEOUT is not set,
the cached value of DART_TESTING_TIMEOUT is 1500, and the value of the
timeout in DartConfiguration.tcl is also set to 1500).

Afterwards, ctest timed out at 1 second for all tests that exceeded
that value, but it turns out that is a hard-coded value which cannot
be superseded by the ctest --timeout option.  So this approach is not
really ideal for the lapack developers who will want to increase the
default limit by only an order of magnitude or less to substantially
reduce the probability someone with a slow computer or special
circumstances will have to override using the ctest --timeout option,
but that change likely will not reduce that probability to zero so
keeping the ability to override the lapack timeout default by the
ctest --timeout option is still likely imporatant to them.

@CMake developers:

The documentation of CTEST_TEST_TIMEOUT (and DART_TESTING_TIMEOUT)
includes the following language:

"The default timeout for each test if
not specified by the `TIMEOUT` test property.

Also, the documentation of the ctest --timeout option says:

`--timeout `
 Set a global timeout on all tests.

This option will set a global timeout on all tests that do not
already have a timeout set on them.

So I guess it could be argued that CTEST_TEST_TIMEOUT does impose a
specific timeout on all tests, and that is why the --timeout option is
being ignored for this case.  But that is not particularly useful
behaviour, and it would be far better in my opinion for the --timeout
option to work for all tests where the TIMEOUT test property has
not been specifically set by the project's build system.

I would appreciate some further investigation of these matters by a
knowledgable CMake developer, and if it turns out this issue is
actually caused by a cmake or ctest bug, then I would be willing to
write up the appropriate bug report if it turns out an instantaneous
fix could not be made.

I also tried the experiment of dropping the setting of
CTEST_TEST_TIMEOUT and using set_tests_properties to set the TIMEOUT
for individual commands, but consistent with the above wording of the
documentation, the ctest --timeout option was ignored for this case. I
am OK with that limitation so long (see above) as some change is made
so CTEST_TEST_TIMEOUT is interpreted exactly the same as the 1500
default timeout, i.e., the CTEST_TEST_TIMEOUT value can be overridden
by the ctest --timeout option.

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: 

Re: [CMake] Parallel jobs failed for cmake

[Igor Sobinov]

 Hello All,

Here is the small description of the issue:

OS: RHEL 6.6
cmake ver. 2.8.12.2
gmake ver. 3.81

I launch the build and got the following error:

make build_release -j5
make[1]: Entering directory `/home/igor/build_root/release_target'
make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make 
rule. So, make[1] reported that's job server is unavailable.

Here is typical process subtree of my make:


root 1731 0.0 0.0 66688 580 ? Ss Nov18 0:00 /usr/sbin/sshd
root 30968 0.0 0.0 100436 4744 ? Ss 07:44 0:00 \_ sshd: root@pts/3 
root 30975 0.0 0.0 108432 1888 pts/3 Ss 07:44 0:00 | \_ -bash
root 31043 0.0 0.0 163856 2212 pts/3 S 07:49 0:00 | \_ su - igor
igor 31045 0.0 0.0 108472 1896 pts/3 S 07:49 0:00 | \_ -bash
igor 5460 0.0 0.0 101152 972 pts/3 S+ 08:10 0:00 | \_ make build_release -j5
igor 5466 0.0 0.0 106096 1164 pts/3 S+ 08:10 0:00 | \_ /bin/sh -c cd 
/home/igor/build_root/release_target; make release
igor 5467 0.0 0.0 101184 1060 pts/3 S+ 08:10 0:00 | \_ make release
igor 5470 0.0 0.0 101448 1256 pts/3 S+ 08:10 0:00 | \_ make -f 
CMakeFiles/Makefile2 release
igor 5475 0.0 0.0 101448 1260 pts/3 S+ 08:10 0:00 | \_ make -f 
CMakeFiles/Makefile2 install/CMakeFiles/release.dir/all
igor 5480 0.0 0.0 101052 944 pts/3 S+ 08:10 0:00 | \_ make -f 
CMakeFiles/make_install.dir/build.make CMakeFiles/make_install.dir/build
igor 5481 0.0 0.0 101184 1020 pts/3 S+ 08:10 0:00 | \_ make install
igor 5486 0.0 0.0 101448 1256 pts/3 S+ 08:10 0:00 | \_ make -f 
CMakeFiles/Makefile2 all
igor 5880 6.3 0.1 106980 6892 pts/3 S+ 08:11 0:00 | \_ make -f 
mydaemon/CMakeFiles/snmp.dir/build.make mydaemon/CMakeFiles/snmp.dir/build
Hope it helps to find the issue

Regards, Igor


>Среда,  9 декабря 2015, 10:57 -05:00 от Paul Smith :
>
>On Wed, 2015-12-09 at 07:15 -0800, J Decker wrote:
>> Probably you're building on windows; which doesn't do 'fork' so it's
>> not possible to parallel make, and you'll have to suffer with
>> single-target makes.
>
>You just need a newer version of GNU make.  GNU make for Windows has
>supported the jobserver feature since GNU make 4.0 (released in October
>2013).  There were some issues with that release so I recommend getting
>4.1, the latest.  There are pre-built versions available for download
>from various places, such as Eli's archives:
>
>http://sourceforge.net/projects/ezwinports/files/make-4.1-2-without-gui
>le-w32-bin.zip/download
>
>http://sourceforge.net/projects/ezwinports/files/make-4.1-2-with-guile-
>w32-bin.zip/download


Bye, Igor

-- 

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] organizing includes statements

[Owen Alanzo Hogarth]

my main CMakeLists.txt file already has a few directives that move the libs
to an output folder so the binaries go to /bin while static and shared
libraries go to /lib

set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)


it seems like this line in your reply above
install( TARGETS lib1 lib2 DESTINATION lib )

moves the shared libraries to the lib folder and this line below moves the
header files to the newly created include directory.

install( FILES lib1/headers/lib1.h lib2/headers/lib2.h DESTINATION include )

is that right?

On Thu, Dec 10, 2015 at 1:46 PM, Attila Krasznahorkay <
attila.krasznahor...@gmail.com> wrote:

> Hi Owen,
>
> This seems like a textbook example of using target_include_directories(…)
> with generator expressions. Let’s take the example where:
>
> lib1/headers/lib1.h
> lib1/lib1.c
> lib2/headers/lib2.h
> lib2/lib2.c
>
> If you want to be able to include lib1.h and lib2.h with simply
>
> #include “lib1.h”
>
> and
>
> #include “lib2.h”
>
> in your user code, and in the library code itself, you’d do something like:
>
> add_library( lib1 SHARED lib1/lib1.c )
> target_include_directories( lib1 PUBLIC
>$
>$ )
>
> add_library( lib2 SHARED lib2/lib2.c )
> target_include_directories( lib2 PUBLIC
>$
>$ )
> target_link_libraries( lib2 lib1 )
>
> install( FILES lib1/headers/lib1.h lib2/headers/lib2.h DESTINATION include
> )
> install( TARGETS lib1 lib2 DESTINATION lib )
>
> In this setup “lib1” should get a -I${CMAKE_SOURCE_DIR}/lib1/headers flag,
> and “lib2” should get both -I${CMAKE_SOURCE_DIR}/lib1/headers and
> -I${CMAKE_SOURCE_DIR}/lib2/headers. Finally the headers both get installed
> into the same include directory, so an outside user will just have to be
> able to find that one directory. (Or if you export CMake’s targets, the
> lib1/2 imported targets will know that their header files are in that
> directory.)
>
> Cheers,
> Attila
>
> > On Dec 10, 2015, at 12:07 AM, Owen Alanzo Hogarth 
> wrote:
> >
> > hi
> >
> > I am building a shared library project that's composed of many smaller
> shared library files.
> >
> > Here's the main shared library project and a list of all the sub
> projects.
> >
> > SET(HEADER_FILES ${CMAKE_CURRENT_SOURCE_DIR}/headers/main_lib.h)
> > SET(SRC_FILES ${CMAKE_CURRENT_SOURCE_DIR}/main_lib.c)
> > SET(TARGET_LIBS core_math point2d line2d quad2d timer_utils)
> >
> > ADD_LIBRARY(main_lib SHARED ${SRC_FILES} ${HEADER_FILES})
> > TARGET_LINK_LIBRARIES(core_engine ${TARGET_LIBS})
> >
> > i have each module setup like this.
> > module
> > module/headers/module.h
> > module/module.c
> >
> > then the module.c will look like this
> > #include "headers/module.h"
> >
> > the file main_lib.h depends on all those target libs, which makes my
> main_lib.h file's include statement look like this
> >
> > #include "../../module/headers/module.h"
> > #include "../../module1/headers/module1.h"
> > #include "../../module2/headers/module2.h"
> >
> >
> > is there any way that I can clean up these includes?
> >
> > For example if I want to use io functions I can just do #include
>  or #include 
> >
> > for math functions.
> >
> > I would like to make my include statements not relative to the files
> actual location, the way it's currently hard coded.
> > --
> >
> > 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

[cmake-developers] [PATCH] Support multiple directories by "cmake -E make_directory" command

[Bartosz Kosiorek]

Hello.


With following patch, I have added support for multiple directories for 
make_directory command.


?Best Regards

Bartosz
From e189db26e60254712e3e73a11296c58d8f61fe68 Mon Sep 17 00:00:00 2001
From: Bartosz Kosiorek 
Date: Wed, 9 Dec 2015 15:59:43 +0100
Subject: [PATCH] Extend make_directory command to support multiple directories

---
 Help/manual/cmake.1.rst   |  9 +
 Source/cmcmd.cxx  | 19 ---
 .../E_make_directory-directory-with-parent-result.txt |  1 +
 .../E_make_directory-directory-with-parent-stderr.txt |  0
 ...ke_directory-three-directories-and-file-result.txt |  1 +
 ...ke_directory-three-directories-and-file-stderr.txt |  1 +
 .../E_make_directory-three-directories-result.txt |  1 +
 .../E_make_directory-three-directories-stderr.txt |  0
 Tests/RunCMake/CommandLine/RunCMakeTest.cmake | 14 ++
 9 files changed, 35 insertions(+), 11 deletions(-)
 create mode 100644 Tests/RunCMake/CommandLine/E_make_directory-directory-with-parent-result.txt
 create mode 100644 Tests/RunCMake/CommandLine/E_make_directory-directory-with-parent-stderr.txt
 create mode 100644 Tests/RunCMake/CommandLine/E_make_directory-three-directories-and-file-result.txt
 create mode 100644 Tests/RunCMake/CommandLine/E_make_directory-three-directories-and-file-stderr.txt
 create mode 100644 Tests/RunCMake/CommandLine/E_make_directory-three-directories-result.txt
 create mode 100644 Tests/RunCMake/CommandLine/E_make_directory-three-directories-stderr.txt

diff --git a/Help/manual/cmake.1.rst b/Help/manual/cmake.1.rst
index 4cbe976..3cd7888 100644
--- a/Help/manual/cmake.1.rst
+++ b/Help/manual/cmake.1.rst
@@ -167,7 +167,8 @@ Available commands are:
   Change the current working directory and run a command.
 
 ``compare_files  ``
-  Check if file1 is same as file2.
+  Check if  is same as . If files are the same,
+  then returns 0, if not itreturns 1.
 
 ``copy ... ``
   Copy files to  (either file or directory).
@@ -194,10 +195,10 @@ Available commands are:
   Run command in a modified environment.
 
 ``environment``
-  Display the current environment.
+  Display the current environment variables.
 
-``make_directory ``
-  Create a directory.
+``make_directory ...``
+  Create parent and  directories.
 
 ``md5sum ...``
   Compute md5sum of files.
diff --git a/Source/cmcmd.cxx b/Source/cmcmd.cxx
index 6a4234f..fb7b1f5 100644
--- a/Source/cmcmd.cxx
+++ b/Source/cmcmd.cxx
@@ -68,7 +68,7 @@ void CMakeCommandUsage(const char* program)
 << "  env [--unset=NAME]... [NAME=VALUE]... COMMAND [ARG]...\n"
 << "- run command in a modified environment\n"
 << "  environment   - display the current environment\n"
-<< "  make_directory dir- create a directory\n"
+<< "  make_directory ...   - create parent and  directories\n"
 << "  md5sum ...  - compute md5sum of files\n"
 << "  remove [-f] ... - remove the file(s), use -f to force "
"it\n"
@@ -447,15 +447,20 @@ int cmcmd::ExecuteCMakeCommand(std::vector& args)
   }
 #endif
 
-else if (args[1] == "make_directory" && args.size() == 3)
+else if (args[1] == "make_directory" && args.size() > 2)
   {
-  if(!cmSystemTools::MakeDirectory(args[2].c_str()))
+  // If error occurs we want to continue copying next files.
+  bool return_value = 0;
+  for (std::string::size_type cc = 2; cc < args.size(); cc ++)
 {
-std::cerr << "Error making directory \"" << args[2]
-  << "\".\n";
-return 1;
+if(!cmSystemTools::MakeDirectory(args[cc].c_str()))
+  {
+  std::cerr << "Error creating directory \""
+<< args[cc] << "\".\n";
+  return_value = 1;
+  }
 }
-  return 0;
+  return return_value;
   }
 
 else if (args[1] == "remove_directory" && args.size() == 3)
diff --git a/Tests/RunCMake/CommandLine/E_make_directory-directory-with-parent-result.txt b/Tests/RunCMake/CommandLine/E_make_directory-directory-with-parent-result.txt
new file mode 100644
index 000..573541a
--- /dev/null
+++ b/Tests/RunCMake/CommandLine/E_make_directory-directory-with-parent-result.txt
@@ -0,0 +1 @@
+0
diff --git a/Tests/RunCMake/CommandLine/E_make_directory-directory-with-parent-stderr.txt b/Tests/RunCMake/CommandLine/E_make_directory-directory-with-parent-stderr.txt
new file mode 100644
index 000..e69de29
diff --git a/Tests/RunCMake/CommandLine/E_make_directory-three-directories-and-file-result.txt b/Tests/RunCMake/CommandLine/E_make_directory-three-directories-and-file-result.txt
new file mode 100644
index 000..d00491f
--- /dev/null
+++ b/Tests/RunCMake/CommandLine/E_make_directory-three-directories-and-file-result.txt
@@ -0,0 +1 @@
+1
diff --git a/Tests/RunCMake/CommandLine/E_make_directory-three-directories-and-file-stderr.txt