date:20170331

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-632-g20326cf

2017-03-31 Thread 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  20326cff8f8a7e469c481767074e343006d7d901 (commit)
  from  c791fb12544926bc5870a61735dc2ec62940a6f6 (commit)

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

- Log -
---

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


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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-644-g37df168

2017-03-31 Thread 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, next has been updated
  discards  ed76ca4476a04a553ffd8e04388c4e91123d04c7 (commit)
  discards  5aa11aa1711543fdc55126798edd39626f30cb23 (commit)
  discards  9ec90185a7b3f26951c87318808752d590028d9b (commit)
  discards  38bbe4194727fc94415c44be41fe8270ef12e0e9 (commit)
  discards  cb99a240757033952b8aeaed2a1839c06ed9fd22 (commit)
  discards  20e7a6dcda2c9e214b8998a7124c3ac2f6471507 (commit)
   via  37df1680826ba8690ac0d7b6084fb5d5a53308cf (commit)
   via  87b2380b9d9ea9a37eb395c76562a1e03860ab4a (commit)
   via  a1b4b513ce7751125ed5c9b43d34c42a11b0cfe2 (commit)
   via  b3e2dac505320956bac43741910e9a0467ec586d (commit)
   via  a84e7ace6872b93522fbb3c1f001feceb5032a0a (commit)
   via  25e3c0827312892d72d60dcbd66860881539eb65 (commit)
   via  20326cff8f8a7e469c481767074e343006d7d901 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (ed76ca4476a04a553ffd8e04388c4e91123d04c7)
\
 N -- N -- N (37df1680826ba8690ac0d7b6084fb5d5a53308cf)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

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=37df1680826ba8690ac0d7b6084fb5d5a53308cf
commit 37df1680826ba8690ac0d7b6084fb5d5a53308cf
Merge: 87b2380 8206c28
Author: Brad King 
AuthorDate: Fri Mar 31 19:29:20 2017 +
Commit: Kitware Robot 
CommitDate: Sat Apr 1 00:01:37 2017 -0400

Stage topic 'test-CMake.GetPrerequisites-config-message'

Topic-id: 23435
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/654


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=87b2380b9d9ea9a37eb395c76562a1e03860ab4a
commit 87b2380b9d9ea9a37eb395c76562a1e03860ab4a
Merge: a1b4b51 4af0c9d
Author: Brad King 
AuthorDate: Fri Mar 31 18:31:41 2017 +
Commit: Kitware Robot 
CommitDate: Sat Apr 1 00:01:37 2017 -0400

Stage topic 'intel-compile-features'

Topic-id: 23431
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/652


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a1b4b513ce7751125ed5c9b43d34c42a11b0cfe2
commit a1b4b513ce7751125ed5c9b43d34c42a11b0cfe2
Merge: b3e2dac 716f8c8
Author: Brad King 
AuthorDate: Fri Mar 31 18:00:26 2017 +
Commit: Kitware Robot 
CommitDate: Sat Apr 1 00:01:35 2017 -0400

Stage topic 'test-LinkInterfaceLoop-custom-timeout'

Topic-id: 23430
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/651


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b3e2dac505320956bac43741910e9a0467ec586d
commit b3e2dac505320956bac43741910e9a0467ec586d
Merge: a84e7ac 72d0f94
Author: Brad King 
AuthorDate: Fri Mar 31 17:51:25 2017 +
Commit: Kitware Robot 
CommitDate: Sat Apr 1 00:01:34 2017 -0400

Stage topic 'test-fix-CTestTestChecksum-dir'

Topic-id: 23428
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/650


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a84e7ace6872b93522fbb3c1f001feceb5032a0a
commit a84e7ace6872b93522fbb3c1f001feceb5032a0a
Merge: 25e3c08 a122190
Author: Brad King 
AuthorDate: Fri Mar 31 17:12:26 2017 +
Commit: Kitware Robot 
CommitDate: Sat Apr 1 00:01:34 2017 -0400

Stage topic 'xcode-current-arch'

Topic-id: 23422
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/648


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=25e3c0827312892d72d60dcbd66860881539eb65
commit 25e3c0827312892d72d60dcbd66860881539eb65
Merge: 20326cf 6f3838c
Author: Brad King 
AuthorDate: Fri Mar 31 17:01:44 2017 +
Commit: Kitware Robot 
CommitDate: Sat Apr 1 00:01:34 2017 -0400

Stage topic 'ExternalProject-fix-remote-branch'

Topic-id: 23427
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/649


---

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


hooks/post-receive
-- 
CMake

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc4-631-gc791fb1

2017-03-31 Thread 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, nightly-master has been updated
   via  c791fb12544926bc5870a61735dc2ec62940a6f6 (commit)
   via  4a553ecb8e52dfd3ca605cd94ef8033e5febe937 (commit)
   via  a466d6f60abe13ddf5eb6bad7cca9743ef67f2f5 (commit)
   via  8772fc81c4ab745eb5abbae58c6a69706f610429 (commit)
   via  60dde287e71efbad71b107902991098a6c77556d (commit)
   via  d1dac1acc502af2f2b766cc9b262a4f1294be39b (commit)
   via  d02709d7f76624d9ec5e178d79cf3658d551f197 (commit)
   via  013ffe76e7d67fdb05fe29c82421b0a000feb468 (commit)
   via  32e9d0ca233439c0381abc5acee8a5acd30be494 (commit)
   via  dfa8263f4be4f1413b73c81649fdc4567a71e56a (commit)
   via  1588a577d16cfb1a689a444b1db1df3ccff2cc3d (commit)
   via  2c9f35789d4955bf77436091d1535ed8761a15d2 (commit)
   via  ec670408969b1abcce6acead9b062c7f0c59683e (commit)
   via  a75757004bda0ff32a152a0d9d6379c02b1338ce (commit)
   via  e05835c35b5d31f31e1a55baf415c075b24a27ad (commit)
  from  3e2f6bd96219ac096826fbc2ea6bc8fe8f0b4a88 (commit)

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

- Log -
---

Summary of changes:
 Help/manual/cmake-generator-expressions.7.rst  |9 ++
 Help/manual/cmake-policies.7.rst   |1 +
 Help/policy/CMP0069.rst|   92 
 Help/release/dev/bundle-genex.rst  |   12 ++
 Help/release/dev/gcc-ipo.rst   |7 +
 .../dev/interprocedural_optimization_policy.rst|8 ++
 Modules/CheckIPOSupported.cmake|   22 ++-
 Modules/CheckIPOSupported/CMakeLists-C.txt.in  |2 +-
 Modules/CheckIPOSupported/CMakeLists-CXX.txt.in|2 +-
 Modules/Compiler/Clang.cmake   |8 ++
 Modules/Compiler/GNU.cmake |   39 +
 Modules/Compiler/QCC.cmake |8 ++
 Modules/Platform/Linux-Intel.cmake |1 +
 Source/CMakeVersion.cmake  |2 +-
 Source/Modules/FindLibUV.cmake |2 +-
 Source/cmCommonTargetGenerator.cxx |7 +-
 Source/cmCommonTargetGenerator.h   |1 -
 Source/cmGeneratorExpressionNode.cxx   |   61 
 Source/cmGeneratorTarget.cxx   |  149 +++-
 Source/cmGeneratorTarget.h |   31 ++--
 Source/cmGlobalGenerator.h |2 +
 Source/cmGlobalNinjaGenerator.h|2 +
 Source/cmGlobalUnixMakefileGenerator3.h|2 +
 Source/cmGlobalVisualStudioGenerator.cxx   |   14 ++
 Source/cmGlobalXCodeGenerator.cxx  |3 +
 Source/cmLocalGenerator.cxx|2 +-
 Source/cmLocalVisualStudio7Generator.cxx   |3 +
 Source/cmMakefileLibraryTargetGenerator.cxx|   21 ++-
 Source/cmNinjaNormalTargetGenerator.cxx|8 ++
 Source/cmOSXBundleGenerator.cxx|   24 ++--
 Source/cmPolicies.h|6 +-
 Source/cmVisualStudio10TargetGenerator.cxx |3 +
 .../CMP0069-NEW-cmake-result.txt}  |0
 .../RunCMake/CMP0069/CMP0069-NEW-cmake-stderr.txt  |4 +
 Tests/RunCMake/CMP0069/CMP0069-NEW-cmake.cmake |6 +
 .../CMP0069-NEW-compiler-result.txt}   |0
 .../CMP0069/CMP0069-NEW-compiler-stderr.txt|4 +
 Tests/RunCMake/CMP0069/CMP0069-NEW-compiler.cmake  |7 +
 .../CMP0069-NEW-generator-result.txt}  |0
 .../CMP0069/CMP0069-NEW-generator-stderr.txt   |4 +
 Tests/RunCMake/CMP0069/CMP0069-NEW-generator.cmake |7 +
 Tests/RunCMake/CMP0069/CMP0069-OLD.cmake   |4 +
 Tests/RunCMake/CMP0069/CMP0069-WARN-stderr.txt |9 ++
 Tests/RunCMake/CMP0069/CMP0069-WARN.cmake  |4 +
 Tests/RunCMake/{CMP0068 => CMP0069}/CMakeLists.txt |0
 Tests/RunCMake/CMP0069/RunCMakeTest.cmake  |   11 ++
 .../TestProject => RunCMake/CMP0069}/main.cpp  |0
 Tests/RunCMake/CMakeLists.txt  |1 +
 Tests/RunCMake/CheckIPOSupported/CMakeLists.txt|3 +
 .../RunCMake/CheckIPOSupported/RunCMakeTest.cmake  |5 +
 .../cmp0069-is-old-result.txt} |0
 .../CheckIPOSupported/cmp0069-is-old-stderr.txt|5 +
 .../CheckIPOSupported/cmp0069-is-old.cmake |6 +
 .../not-supported-by-compiler-stderr.txt   |2 +-
 .../not-supported-by-generator-result.txt} |0
 ...r.txt => not-supported-by-generator-stderr.txt} |4 +-

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc4-643-ged76ca4

2017-03-31 Thread 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, nightly has been updated
  discards  baa8c9c3568c808b6217c6548a1d927cf85475ab (commit)
  discards  83fb3398df43d9ea22fcc462ff56c60ac2be4d87 (commit)
  discards  c84c233c802d69b4404d064fc40bc16cbea8b5d6 (commit)
  discards  1399748bd856ce8f5a24e30990c536c77cfc768e (commit)
   via  ed76ca4476a04a553ffd8e04388c4e91123d04c7 (commit)
   via  8206c28bd6e6d7849e80a68cdfef79ff5a1031a3 (commit)
   via  5aa11aa1711543fdc55126798edd39626f30cb23 (commit)
   via  4af0c9daf41dfe08c776e77f5b19aebd81469479 (commit)
   via  9ec90185a7b3f26951c87318808752d590028d9b (commit)
   via  716f8c88c9c94dc58f22ae770d613a4fec51c276 (commit)
   via  38bbe4194727fc94415c44be41fe8270ef12e0e9 (commit)
   via  72d0f947136f535fe7486f9b02caddb33f66eea1 (commit)
   via  cb99a240757033952b8aeaed2a1839c06ed9fd22 (commit)
   via  20e7a6dcda2c9e214b8998a7124c3ac2f6471507 (commit)
   via  6f3838c034e652b90d9c2571851729313880a328 (commit)
   via  a1221905092c09603c0b59dd0ed05bfe9f1f22ef (commit)
   via  c791fb12544926bc5870a61735dc2ec62940a6f6 (commit)
   via  4a553ecb8e52dfd3ca605cd94ef8033e5febe937 (commit)
   via  a466d6f60abe13ddf5eb6bad7cca9743ef67f2f5 (commit)
   via  8772fc81c4ab745eb5abbae58c6a69706f610429 (commit)
   via  60dde287e71efbad71b107902991098a6c77556d (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (baa8c9c3568c808b6217c6548a1d927cf85475ab)
\
 N -- N -- N (ed76ca4476a04a553ffd8e04388c4e91123d04c7)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

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

- Log -
---

Summary of changes:
 Modules/CMakeCCompiler.cmake.in|1 +
 Modules/CMakeCXXCompiler.cmake.in  |1 +
 Modules/CMakeDetermineCCompiler.cmake  |5 +
 Modules/CMakeDetermineCXXCompiler.cmake|5 +
 Modules/CMakeDetermineCompilerId.cmake |4 
 Modules/Compiler/Intel-CXX-FeatureTests.cmake  |4 +++-
 Modules/CompilerId/Xcode-3.pbxproj.in  |2 +-
 Modules/ExternalProject.cmake  |5 -
 Source/CMakeVersion.cmake  |2 +-
 Tests/CMakeOnly/CMakeLists.txt |9 -
 Tests/CMakeTests/CMakeLists.txt|5 +
 Tests/CMakeTests/GetPrerequisitesTest.cmake.in |7 ++-
 Tests/CTestTestChecksum/test.cmake.in  |4 ++--
 13 files changed, 38 insertions(+), 16 deletions(-)


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

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

2017-03-31 Thread ウルヰ

> I suggest you try the experiment of using the system version of
> libcurl instead (which also supplies SSL capability). For example, my
> Linux distribution is Debian Stable which only installs libssl 1.0.1.
> And for that case when I tried the bootstrap method with the
> --system-curl option (the usual way I build cmake), I do not confirm
> your linking issue.  So my expectation is you will also avoid that
> linking issue on Ubuntu 2016.10 if you use that bootstrap option or a
> similar system libcurl option for the non-bootstrap case.

I tried running ./bootstrap with the --system-curl option, and I see
a different error:

[ 93%] Linking CXX executable ../bin/ccmake
/usr/bin/ld: 
../Utilities/cmlibarchive/libarchive/libcmlibarchive.a(archive_cryptor.c.o):
undefined reference to symbol 'EVP_aes_256_ecb@@OPENSSL_1.0.0'
//lib/x86_64-linux-gnu/libcrypto.so.1.0.0: error adding symbols: DSO
missing from command line
collect2: error: ld returned 1 exit status
Source/CMakeFiles/ccmake.dir/build.make:420: recipe for target
'bin/ccmake' failed
make[2]: *** [bin/ccmake] Error 1
CMakeFiles/Makefile2:2135: recipe for target
'Source/CMakeFiles/ccmake.dir/all' failed
make[1]: *** [Source/CMakeFiles/ccmake.dir/all] Error 2
Makefile:162: recipe for target 'all' failed
make: *** [all] Error 2

So the problem is likely on my end.
-- 

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] Linker error when building 3.8.0-rc4 on Linux

2017-03-31 Thread Nils Gladitz


On 31.03.2017 22:44, Alan W. Irwin wrote:


Therefore, from the sidelines I am encouraging you guys to be
extraordinarily careful about this particular issue; e.g., by
attempting to to confirm this CMake-3.8.0-rc4 issue independently for
Ubuntu 16.10.



FWIW I tried reproducing it from within an Ubuntu 16.10 Docker container 
and it worked there as-is.



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

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

2017-03-31 Thread Alan W. Irwin


On 2017-03-31 14:00+0200 Nils Gladitz wrote:


On 03/31/2017 11:54 AM, Alan W. Irwin wrote:


Hi Nils:

And use of ExternalProject_Add, etc.  In other words, this is a pretty
crippling restriction for users with Linux distributions (such as the
quite recent Ubuntu 2016.10 of the original poster) that do not yet
give access to libssl version 1.1.0 (the oldest version of libssl
where HMAC_CTX_new() and HMAC_CTX_free() are available according to
your previous post).


Strangely enough I have no issue on Ubuntu 16.04 with the system default 
installation of OpenSSL.


What I missed in the original post is that the error comes from libarchive 
rather than libcurl.
But libarchive itself also seems to provide inline definitions of the missing 
functions in Utilities/cmlibarchive/libarchive/archive_openssl_hmac_private.h 
for OpenSSL < 1.1.


I can't tell why the inline definitions aren't used on the original posters 
system.

Perhaps there is a mismatch between OpenSSL headers and libraries?


Hi Nils:

Strictly from what you have said (since my result bypassed OpenSSL
completely by using libcurl for SSL functionality), it appears to me
that CMake (or libarchive?) developers have attempted to adjust for
the case where OpenSSL < 1.1, and that adjustment works for you with
Ubuntu 16.04, but does not work for the O.P. with Ubuntu 16.10.

Ultimately, of course, it is strictly up to the CMake developers how
carefully they respond to reports of OpenSSL issues, but from my
perspective CMake SSL functionality is important because of the widely
used ExternalProject module that depends on that functionality.

Therefore, from the sidelines I am encouraging you guys to be
extraordinarily careful about this particular issue; e.g., by
attempting to to confirm this CMake-3.8.0-rc4 issue independently for
Ubuntu 16.10.

Further to such confirmation does the CMake dashboard already test
system OpenSSL for the Ubuntu 16.10 case or does one of the CMake
developers have ready access to a Ubuntu 16.10 system so they can
attempt to confirm the issue?

That is the end of my ideas for helping you to debug this issue so
I am likely bowing out of further discussion in this thread.

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-643-ged76ca4

2017-03-31 Thread 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, next has been updated
   via  ed76ca4476a04a553ffd8e04388c4e91123d04c7 (commit)
   via  8206c28bd6e6d7849e80a68cdfef79ff5a1031a3 (commit)
  from  5aa11aa1711543fdc55126798edd39626f30cb23 (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=ed76ca4476a04a553ffd8e04388c4e91123d04c7
commit ed76ca4476a04a553ffd8e04388c4e91123d04c7
Merge: 5aa11aa 8206c28
Author: Brad King 
AuthorDate: Fri Mar 31 19:29:20 2017 +
Commit: Kitware Robot 
CommitDate: Fri Mar 31 15:29:23 2017 -0400

Stage topic 'test-CMake.GetPrerequisites-config-message'

Topic-id: 23435
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/654


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8206c28bd6e6d7849e80a68cdfef79ff5a1031a3
commit 8206c28bd6e6d7849e80a68cdfef79ff5a1031a3
Author: Brad King 
AuthorDate: Fri Mar 31 15:20:01 2017 -0400
Commit: Brad King 
CommitDate: Fri Mar 31 15:20:01 2017 -0400

Tests: Fix CMake.GetPrerequisites test config message

Since commit v2.8.11~239^2~1 (ProcessorCount test: fix path to
cmsysTestsCxx executable, 2013-01-24) we accidentally printed a literal
`${CTEST_CONFIGURATION_TYPE}` instead of the actual build configuration.
Update the message to use the `$` generator expression to get
the real build configuration used.

diff --git a/Tests/CMakeTests/CMakeLists.txt b/Tests/CMakeTests/CMakeLists.txt
index d5524c3..aa7ae25 100644
--- a/Tests/CMakeTests/CMakeLists.txt
+++ b/Tests/CMakeTests/CMakeLists.txt
@@ -53,10 +53,7 @@ set(EndStuff_PreArgs
   )
 AddCMakeTest(EndStuff "${EndStuff_PreArgs}")
 
-set(GetPrerequisites_PreArgs
-  "-DCTEST_CONFIGURATION_TYPE:STRING=\\\${CTEST_CONFIGURATION_TYPE}"
-  )
-AddCMakeTest(GetPrerequisites "${GetPrerequisites_PreArgs}")
+AddCMakeTest(GetPrerequisites "-DConfiguration:STRING=$")
 
 if(GIT_EXECUTABLE)
   set(PolicyCheck_PreArgs
diff --git a/Tests/CMakeTests/GetPrerequisitesTest.cmake.in 
b/Tests/CMakeTests/GetPrerequisitesTest.cmake.in
index 89ca735..7325b87 100644
--- a/Tests/CMakeTests/GetPrerequisitesTest.cmake.in
+++ b/Tests/CMakeTests/GetPrerequisitesTest.cmake.in
@@ -2,18 +2,15 @@
 #
 include(GetPrerequisites)
 
-set(CMAKE_BUILD_TYPE "@CMAKE_BUILD_TYPE@")
-set(CMAKE_CONFIGURATION_TYPES "@CMAKE_CONFIGURATION_TYPES@")
 set(CMAKE_EXECUTABLE_SUFFIX "@CMAKE_EXECUTABLE_SUFFIX@")
 
 
 message(STATUS 
"=")
 message(STATUS "CTEST_FULL_OUTPUT (Avoid ctest truncation of output)")
 message(STATUS "")
-message(STATUS "CMAKE_BUILD_TYPE='${CMAKE_BUILD_TYPE}'")
-message(STATUS "CMAKE_CONFIGURATION_TYPES='${CMAKE_CONFIGURATION_TYPES}'")
+message(STATUS "Configuration '${Configuration}'")
+message(STATUS "CMAKE_COMMAND='${CMAKE_COMMAND}'")
 message(STATUS "CMAKE_EXECUTABLE_SUFFIX='${CMAKE_EXECUTABLE_SUFFIX}'")
-message(STATUS "CTEST_CONFIGURATION_TYPE='${CTEST_CONFIGURATION_TYPE}'")
 message(STATUS "")
 
 

---

Summary of changes:
 Tests/CMakeTests/CMakeLists.txt|5 +
 Tests/CMakeTests/GetPrerequisitesTest.cmake.in |7 ++-
 2 files changed, 3 insertions(+), 9 deletions(-)


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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-641-g5aa11aa

2017-03-31 Thread 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, next has been updated
   via  5aa11aa1711543fdc55126798edd39626f30cb23 (commit)
   via  4af0c9daf41dfe08c776e77f5b19aebd81469479 (commit)
  from  9ec90185a7b3f26951c87318808752d590028d9b (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=5aa11aa1711543fdc55126798edd39626f30cb23
commit 5aa11aa1711543fdc55126798edd39626f30cb23
Merge: 9ec9018 4af0c9d
Author: Brad King 
AuthorDate: Fri Mar 31 18:31:41 2017 +
Commit: Kitware Robot 
CommitDate: Fri Mar 31 14:31:52 2017 -0400

Stage topic 'intel-compile-features'

Topic-id: 23431
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/652


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4af0c9daf41dfe08c776e77f5b19aebd81469479
commit 4af0c9daf41dfe08c776e77f5b19aebd81469479
Author: Brad King 
AuthorDate: Fri Mar 31 14:19:17 2017 -0400
Commit: Brad King 
CommitDate: Fri Mar 31 14:29:18 2017 -0400

Features: Update features for Intel C++ 17.0.2 on UNIX

Intel 17.0.2 on UNIX introduced a regression from 17.0.1 in its
definition of `__cpp_constexpr` in `-std=c++14` mode.  It incorrectly
defines it as `200704` instead of the expected `201304`.  Fix our
feature detection table to account for this.

diff --git a/Modules/Compiler/Intel-CXX-FeatureTests.cmake 
b/Modules/Compiler/Intel-CXX-FeatureTests.cmake
index e370647..929a7c6 100644
--- a/Modules/Compiler/Intel-CXX-FeatureTests.cmake
+++ b/Modules/Compiler/Intel-CXX-FeatureTests.cmake
@@ -13,7 +13,6 @@
 # - __cpp_variadic_templates 200704
 
 set(_cmake_feature_test_cxx_variable_templates "__cpp_variable_templates >= 
201304")
-set(_cmake_feature_test_cxx_relaxed_constexpr "__cpp_constexpr >= 201304")
 
 set(_cmake_oldestSupported "__INTEL_COMPILER >= 1210")
 set(DETECT_CXX11 "((__cplusplus >= 201103L) || defined(__INTEL_CXX11_MODE__) 
|| defined(__GXX_EXPERIMENTAL_CXX0X__))")
@@ -24,6 +23,9 @@ set(DETECT_BUGGY_ICC15 "((__INTEL_COMPILER == 1500) && 
(__INTEL_COMPILER_UPDATE
 set(DETECT_CXX14 "((__cplusplus >= 201300L) || ((__cplusplus == 201103L) && 
!defined(__INTEL_CXX11_MODE__)) || ((${DETECT_BUGGY_ICC15}) && 
defined(__GXX_EXPERIMENTAL_CXX0X__) && !defined(__INTEL_CXX11_MODE__) ) || 
(defined(__INTEL_CXX11_MODE__) && defined(__cpp_aggregate_nsdmi)) )")
 unset(DETECT_BUGGY_ICC15)
 
+set(Intel17_CXX14 "__INTEL_COMPILER >= 1700 && ${DETECT_CXX14}")
+set(_cmake_feature_test_cxx_relaxed_constexpr "__cpp_constexpr >= 201304 || 
(${Intel17_CXX14} && !defined(_MSC_VER))")
+
 set(Intel16_CXX14 "__INTEL_COMPILER >= 1600 && ${DETECT_CXX14}")
 set(_cmake_feature_test_cxx_aggregate_default_initializers "${Intel16_CXX14}")
 set(_cmake_feature_test_cxx_contextual_conversions "${Intel16_CXX14}")

---

Summary of changes:
 Modules/Compiler/Intel-CXX-FeatureTests.cmake |4 +++-
 1 file changed, 3 insertions(+), 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, next, updated. v3.8.0-rc4-639-g9ec9018

2017-03-31 Thread 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, next has been updated
   via  9ec90185a7b3f26951c87318808752d590028d9b (commit)
   via  716f8c88c9c94dc58f22ae770d613a4fec51c276 (commit)
  from  38bbe4194727fc94415c44be41fe8270ef12e0e9 (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=9ec90185a7b3f26951c87318808752d590028d9b
commit 9ec90185a7b3f26951c87318808752d590028d9b
Merge: 38bbe41 716f8c8
Author: Brad King 
AuthorDate: Fri Mar 31 18:00:26 2017 +
Commit: Kitware Robot 
CommitDate: Fri Mar 31 14:00:28 2017 -0400

Stage topic 'test-LinkInterfaceLoop-custom-timeout'

Topic-id: 23430
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/651


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=716f8c88c9c94dc58f22ae770d613a4fec51c276
commit 716f8c88c9c94dc58f22ae770d613a4fec51c276
Author: Brad King 
AuthorDate: Fri Mar 31 13:56:49 2017 -0400
Commit: Brad King 
CommitDate: Fri Mar 31 13:56:49 2017 -0400

Tests: Add option to customize LinkInterfaceLoop timeout

This test has a timeout in case CMake gets into an infinite loop.  The
default of 90 seconds should be plenty of time for the test to run
correctly since it does not actually do a build.  However, busy machines
that run lots of tests in parallel may need a longer timeout.  Give them
an option to extend it.

diff --git a/Tests/CMakeOnly/CMakeLists.txt b/Tests/CMakeOnly/CMakeLists.txt
index c692cbd..d44c836 100644
--- a/Tests/CMakeOnly/CMakeLists.txt
+++ b/Tests/CMakeOnly/CMakeLists.txt
@@ -9,7 +9,14 @@ macro(add_CMakeOnly_test test)
 endmacro()
 
 add_CMakeOnly_test(LinkInterfaceLoop)
-set_property(TEST CMakeOnly.LinkInterfaceLoop PROPERTY TIMEOUT 90)
+# If a bug is introduced in CMake that causes an infinite loop while
+# analyzing LinkInterfaceLoop then don't let the test run too long.
+# Use an option to customize it so that the timeout can be extended
+# on busy machines.
+if(NOT DEFINED CMake_TEST_CMakeOnly.LinkInterfaceLoop_TIMEOUT)
+  set(CMake_TEST_CMakeOnly.LinkInterfaceLoop_TIMEOUT 90)
+endif()
+set_property(TEST CMakeOnly.LinkInterfaceLoop PROPERTY TIMEOUT 
${CMake_TEST_CMakeOnly.LinkInterfaceLoop_TIMEOUT})
 
 add_CMakeOnly_test(CheckSymbolExists)
 

---

Summary of changes:
 Tests/CMakeOnly/CMakeLists.txt |9 -
 1 file changed, 8 insertions(+), 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, next, updated. v3.8.0-rc4-637-g38bbe41

2017-03-31 Thread 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, next has been updated
   via  38bbe4194727fc94415c44be41fe8270ef12e0e9 (commit)
   via  72d0f947136f535fe7486f9b02caddb33f66eea1 (commit)
  from  cb99a240757033952b8aeaed2a1839c06ed9fd22 (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=38bbe4194727fc94415c44be41fe8270ef12e0e9
commit 38bbe4194727fc94415c44be41fe8270ef12e0e9
Merge: cb99a24 72d0f94
Author: Brad King 
AuthorDate: Fri Mar 31 17:51:25 2017 +
Commit: Kitware Robot 
CommitDate: Fri Mar 31 13:51:29 2017 -0400

Stage topic 'test-fix-CTestTestChecksum-dir'

Topic-id: 23428
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/650


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=72d0f947136f535fe7486f9b02caddb33f66eea1
commit 72d0f947136f535fe7486f9b02caddb33f66eea1
Author: Brad King 
AuthorDate: Fri Mar 31 13:43:44 2017 -0400
Commit: Brad King 
CommitDate: Fri Mar 31 13:46:08 2017 -0400

Tests: Fix spurious CTestTestParallel failures

If `CTestTestParallel` was run at the same time as `CTestTestChecksum`
(e.g. during parallel testing) then the former fails due to the latter
stepping on its directory.  Fix the directory used for the latter to
avoid the conflict.

diff --git a/Tests/CTestTestChecksum/test.cmake.in 
b/Tests/CTestTestChecksum/test.cmake.in
index 32d62bb..2a435d2 100644
--- a/Tests/CTestTestChecksum/test.cmake.in
+++ b/Tests/CTestTestChecksum/test.cmake.in
@@ -5,8 +5,8 @@ set(CTEST_DASHBOARD_ROOT
"@CMake_BINARY_DIR@/Tests/CTestTest")
 set(CTEST_SITE  "@SITE@")
 set(CTEST_BUILD_NAME"CTestTest-@BUILDNAME@-Checksum")
 
-set(CTEST_SOURCE_DIRECTORY  
"@CMake_SOURCE_DIR@/Tests/CTestTestParallel")
-set(CTEST_BINARY_DIRECTORY  
"@CMake_BINARY_DIR@/Tests/CTestTestParallel")
+set(CTEST_SOURCE_DIRECTORY  
"@CMake_SOURCE_DIR@/Tests/CTestTestChecksum")
+set(CTEST_BINARY_DIRECTORY  
"@CMake_BINARY_DIR@/Tests/CTestTestChecksum")
 set(CTEST_CVS_COMMAND   "@CVSCOMMAND@")
 set(CTEST_CMAKE_GENERATOR   "@CMAKE_GENERATOR@")
 set(CTEST_CMAKE_GENERATOR_PLATFORM  "@CMAKE_GENERATOR_PLATFORM@")

---

Summary of changes:
 Tests/CTestTestChecksum/test.cmake.in |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


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

Re: [cmake-developers] Problems with CTestTestParallel

2017-03-31 Thread Brad King

On 03/10/2017 10:32 AM, Brad King wrote:
> On 03/10/2017 06:34 AM, Rolf Eike Beer wrote:
>> I've attached the complete build dir of that test, maybe anyone 
>> has a clue what is going on there
> 
> The `Testing/Temporary/LastSubmit_20170310-1035.log` shows errors
> submitting to CDash.  However, the `test.cmake` script does not
> include a `ctest_submit` call.  Any idea what happens there?

It turns out another test was accidentally stepping on this one.
That's why it always passed locally but failed at night.  I can
reproduce the failure by running `CTestTestParallel` and
`CTestTestChecksum` in parallel.  Here is a fix:

https://gitlab.kitware.com/cmake/cmake/merge_requests/650

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-commits] CMake branch, next, updated. v3.8.0-rc4-635-gcb99a24

2017-03-31 Thread 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, next has been updated
   via  cb99a240757033952b8aeaed2a1839c06ed9fd22 (commit)
   via  a1221905092c09603c0b59dd0ed05bfe9f1f22ef (commit)
  from  20e7a6dcda2c9e214b8998a7124c3ac2f6471507 (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=cb99a240757033952b8aeaed2a1839c06ed9fd22
commit cb99a240757033952b8aeaed2a1839c06ed9fd22
Merge: 20e7a6d a122190
Author: Brad King 
AuthorDate: Fri Mar 31 17:12:26 2017 +
Commit: Kitware Robot 
CommitDate: Fri Mar 31 13:12:38 2017 -0400

Stage topic 'xcode-current-arch'

Topic-id: 23422
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/648


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a1221905092c09603c0b59dd0ed05bfe9f1f22ef
commit a1221905092c09603c0b59dd0ed05bfe9f1f22ef
Author: Brad King 
AuthorDate: Fri Mar 31 11:26:08 2017 -0400
Commit: Brad King 
CommitDate: Fri Mar 31 11:26:08 2017 -0400

Xcode: Detect CURRENT_ARCH for use by generator

During compiler identification, extract the Xcode `CURRENT_ARCH` value
and save it for later use by the Xcode generator in an internal compiler
information variable.  This will be useful to know the locations of
object files when only one architecture is built.

diff --git a/Modules/CMakeCCompiler.cmake.in b/Modules/CMakeCCompiler.cmake.in
index ab068a2..102ab69 100644
--- a/Modules/CMakeCCompiler.cmake.in
+++ b/Modules/CMakeCCompiler.cmake.in
@@ -13,6 +13,7 @@ set(CMAKE_C_PLATFORM_ID "@CMAKE_C_PLATFORM_ID@")
 set(CMAKE_C_SIMULATE_ID "@CMAKE_C_SIMULATE_ID@")
 set(CMAKE_C_SIMULATE_VERSION "@CMAKE_C_SIMULATE_VERSION@")
 @SET_MSVC_C_ARCHITECTURE_ID@
+@SET_CMAKE_XCODE_CURRENT_ARCH@
 set(CMAKE_AR "@CMAKE_AR@")
 set(CMAKE_GCC_AR "@CMAKE_GCC_AR@")
 set(CMAKE_RANLIB "@CMAKE_RANLIB@")
diff --git a/Modules/CMakeCXXCompiler.cmake.in 
b/Modules/CMakeCXXCompiler.cmake.in
index 27c8881..3dae035 100644
--- a/Modules/CMakeCXXCompiler.cmake.in
+++ b/Modules/CMakeCXXCompiler.cmake.in
@@ -14,6 +14,7 @@ set(CMAKE_CXX_PLATFORM_ID "@CMAKE_CXX_PLATFORM_ID@")
 set(CMAKE_CXX_SIMULATE_ID "@CMAKE_CXX_SIMULATE_ID@")
 set(CMAKE_CXX_SIMULATE_VERSION "@CMAKE_CXX_SIMULATE_VERSION@")
 @SET_MSVC_CXX_ARCHITECTURE_ID@
+@SET_CMAKE_XCODE_CURRENT_ARCH@
 set(CMAKE_AR "@CMAKE_AR@")
 set(CMAKE_GCC_AR "@CMAKE_GCC_AR@")
 set(CMAKE_RANLIB "@CMAKE_RANLIB@")
diff --git a/Modules/CMakeDetermineCCompiler.cmake 
b/Modules/CMakeDetermineCCompiler.cmake
index 5d9850d..3caccde 100644
--- a/Modules/CMakeDetermineCCompiler.cmake
+++ b/Modules/CMakeDetermineCCompiler.cmake
@@ -175,6 +175,11 @@ if(MSVC_C_ARCHITECTURE_ID)
 "set(MSVC_C_ARCHITECTURE_ID ${MSVC_C_ARCHITECTURE_ID})")
 endif()
 
+if(CMAKE_C_XCODE_CURRENT_ARCH)
+  set(SET_CMAKE_XCODE_CURRENT_ARCH
+"set(CMAKE_XCODE_CURRENT_ARCH ${CMAKE_C_XCODE_CURRENT_ARCH})")
+endif()
+
 # configure variables set in this file for fast reload later on
 configure_file(${CMAKE_ROOT}/Modules/CMakeCCompiler.cmake.in
   ${CMAKE_PLATFORM_INFO_DIR}/CMakeCCompiler.cmake
diff --git a/Modules/CMakeDetermineCXXCompiler.cmake 
b/Modules/CMakeDetermineCXXCompiler.cmake
index 4d85150..9150962 100644
--- a/Modules/CMakeDetermineCXXCompiler.cmake
+++ b/Modules/CMakeDetermineCXXCompiler.cmake
@@ -170,6 +170,11 @@ if(MSVC_CXX_ARCHITECTURE_ID)
 "set(MSVC_CXX_ARCHITECTURE_ID ${MSVC_CXX_ARCHITECTURE_ID})")
 endif()
 
+if(CMAKE_CXX_XCODE_CURRENT_ARCH)
+  set(SET_CMAKE_XCODE_CURRENT_ARCH
+"set(CMAKE_XCODE_CURRENT_ARCH ${CMAKE_CXX_XCODE_CURRENT_ARCH})")
+endif()
+
 # configure all variables set in this file
 configure_file(${CMAKE_ROOT}/Modules/CMakeCXXCompiler.cmake.in
   ${CMAKE_PLATFORM_INFO_DIR}/CMakeCXXCompiler.cmake
diff --git a/Modules/CMakeDetermineCompilerId.cmake 
b/Modules/CMakeDetermineCompilerId.cmake
index 1abbc01..687263a 100644
--- a/Modules/CMakeDetermineCompilerId.cmake
+++ b/Modules/CMakeDetermineCompilerId.cmake
@@ -104,6 +104,7 @@ function(CMAKE_DETERMINE_COMPILER_ID lang flagvar src)
   set(CMAKE_${lang}_PLATFORM_ID "${CMAKE_${lang}_PLATFORM_ID}" PARENT_SCOPE)
   set(MSVC_${lang}_ARCHITECTURE_ID "${MSVC_${lang}_ARCHITECTURE_ID}"
 PARENT_SCOPE)
+  set(CMAKE_${lang}_XCODE_CURRENT_ARCH "${CMAKE_${lang}_XCODE_CURRENT_ARCH}" 
PARENT_SCOPE)
   set(CMAKE_${lang}_CL_SHOWINCLUDES_PREFIX 
"${CMAKE_${lang}_CL_SHOWINCLUDES_PREFIX}" PARENT_SCOPE)
   set(CMAKE_${lang}_COMPILER_VERSION "${CMAKE_${lang}_COMPILER_VERSION}" 
PARENT_SCOPE)
   set(CMAKE_${lang}_COMPILER_WRAPPER "${CMAKE_${lang}_COMPILER_WRAPPER}" 
PARENT_SCOPE)
@@ -358,6 +359,9 @@ Id flags:

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-633-g20e7a6d

2017-03-31 Thread 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, next has been updated
   via  20e7a6dcda2c9e214b8998a7124c3ac2f6471507 (commit)
   via  6f3838c034e652b90d9c2571851729313880a328 (commit)
  from  c791fb12544926bc5870a61735dc2ec62940a6f6 (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=20e7a6dcda2c9e214b8998a7124c3ac2f6471507
commit 20e7a6dcda2c9e214b8998a7124c3ac2f6471507
Merge: c791fb1 6f3838c
Author: Brad King 
AuthorDate: Fri Mar 31 17:01:44 2017 +
Commit: Kitware Robot 
CommitDate: Fri Mar 31 13:01:52 2017 -0400

Stage topic 'ExternalProject-fix-remote-branch'

Topic-id: 23427
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/649


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6f3838c034e652b90d9c2571851729313880a328
commit 6f3838c034e652b90d9c2571851729313880a328
Author: Brad King 
AuthorDate: Fri Mar 31 12:53:51 2017 -0400
Commit: Brad King 
CommitDate: Fri Mar 31 12:59:53 2017 -0400

ExternalProject: Fix regression in GIT_TAG with remote branch name

The change in commit  v3.8.0-rc2~7^2 (ExternalProject: Run `git
checkout` with `--` to clarify arguments, 2017-02-24) broke the case of
`GIT_TAG some-remote-branch` because an explicit `--` means that the
preceding argument is a tree-ish instead of a branch.  Revert the change
and leave a comment.

Fixes: #16763

diff --git a/Modules/ExternalProject.cmake b/Modules/ExternalProject.cmake
index 00781d6..b42d2dd 100644
--- a/Modules/ExternalProject.cmake
+++ b/Modules/ExternalProject.cmake
@@ -600,8 +600,11 @@ if(error_code)
   message(FATAL_ERROR \"Failed to clone repository: '${git_repository}'\")
 endif()
 
+# Use `git checkout ` even though this risks ambiguity with a
+# local path.  Unfortunately we cannot use `git checkout  --`
+# because that will not search for remote branch names, a common use case.
 execute_process(
-  COMMAND \"${git_EXECUTABLE}\" \${git_options} checkout ${git_tag} --
+  COMMAND \"${git_EXECUTABLE}\" \${git_options} checkout ${git_tag}
   WORKING_DIRECTORY \"${work_dir}/${src_name}\"
   RESULT_VARIABLE error_code
   )

---

Summary of changes:
 Modules/ExternalProject.cmake |5 -
 1 file changed, 4 insertions(+), 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.8.0-rc4-631-gc791fb1

2017-03-31 Thread 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  c791fb12544926bc5870a61735dc2ec62940a6f6 (commit)
   via  4a553ecb8e52dfd3ca605cd94ef8033e5febe937 (commit)
   via  a466d6f60abe13ddf5eb6bad7cca9743ef67f2f5 (commit)
   via  8772fc81c4ab745eb5abbae58c6a69706f610429 (commit)
   via  d1dac1acc502af2f2b766cc9b262a4f1294be39b (commit)
   via  d02709d7f76624d9ec5e178d79cf3658d551f197 (commit)
   via  013ffe76e7d67fdb05fe29c82421b0a000feb468 (commit)
   via  32e9d0ca233439c0381abc5acee8a5acd30be494 (commit)
   via  dfa8263f4be4f1413b73c81649fdc4567a71e56a (commit)
   via  1588a577d16cfb1a689a444b1db1df3ccff2cc3d (commit)
   via  2c9f35789d4955bf77436091d1535ed8761a15d2 (commit)
   via  ec670408969b1abcce6acead9b062c7f0c59683e (commit)
   via  a75757004bda0ff32a152a0d9d6379c02b1338ce (commit)
   via  e05835c35b5d31f31e1a55baf415c075b24a27ad (commit)
  from  60dde287e71efbad71b107902991098a6c77556d (commit)

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

- Log -
---

Summary of changes:
 Help/manual/cmake-generator-expressions.7.rst  |9 ++
 Help/manual/cmake-policies.7.rst   |1 +
 Help/policy/CMP0069.rst|   92 
 Help/release/dev/bundle-genex.rst  |   12 ++
 Help/release/dev/gcc-ipo.rst   |7 +
 .../dev/interprocedural_optimization_policy.rst|8 ++
 Modules/CheckIPOSupported.cmake|   22 ++-
 Modules/CheckIPOSupported/CMakeLists-C.txt.in  |2 +-
 Modules/CheckIPOSupported/CMakeLists-CXX.txt.in|2 +-
 Modules/Compiler/Clang.cmake   |8 ++
 Modules/Compiler/GNU.cmake |   39 +
 Modules/Compiler/QCC.cmake |8 ++
 Modules/Platform/Linux-Intel.cmake |1 +
 Source/Modules/FindLibUV.cmake |2 +-
 Source/cmCommonTargetGenerator.cxx |7 +-
 Source/cmCommonTargetGenerator.h   |1 -
 Source/cmGeneratorExpressionNode.cxx   |   61 
 Source/cmGeneratorTarget.cxx   |  149 +++-
 Source/cmGeneratorTarget.h |   31 ++--
 Source/cmGlobalGenerator.h |2 +
 Source/cmGlobalNinjaGenerator.h|2 +
 Source/cmGlobalUnixMakefileGenerator3.h|2 +
 Source/cmGlobalVisualStudioGenerator.cxx   |   14 ++
 Source/cmGlobalXCodeGenerator.cxx  |3 +
 Source/cmLocalGenerator.cxx|2 +-
 Source/cmLocalVisualStudio7Generator.cxx   |3 +
 Source/cmMakefileLibraryTargetGenerator.cxx|   21 ++-
 Source/cmNinjaNormalTargetGenerator.cxx|8 ++
 Source/cmOSXBundleGenerator.cxx|   24 ++--
 Source/cmPolicies.h|6 +-
 Source/cmVisualStudio10TargetGenerator.cxx |3 +
 .../CMP0069-NEW-cmake-result.txt}  |0
 .../RunCMake/CMP0069/CMP0069-NEW-cmake-stderr.txt  |4 +
 Tests/RunCMake/CMP0069/CMP0069-NEW-cmake.cmake |6 +
 .../CMP0069-NEW-compiler-result.txt}   |0
 .../CMP0069/CMP0069-NEW-compiler-stderr.txt|4 +
 Tests/RunCMake/CMP0069/CMP0069-NEW-compiler.cmake  |7 +
 .../CMP0069-NEW-generator-result.txt}  |0
 .../CMP0069/CMP0069-NEW-generator-stderr.txt   |4 +
 Tests/RunCMake/CMP0069/CMP0069-NEW-generator.cmake |7 +
 Tests/RunCMake/CMP0069/CMP0069-OLD.cmake   |4 +
 Tests/RunCMake/CMP0069/CMP0069-WARN-stderr.txt |9 ++
 Tests/RunCMake/CMP0069/CMP0069-WARN.cmake  |4 +
 Tests/RunCMake/{CMP0068 => CMP0069}/CMakeLists.txt |0
 Tests/RunCMake/CMP0069/RunCMakeTest.cmake  |   11 ++
 .../TestProject => RunCMake/CMP0069}/main.cpp  |0
 Tests/RunCMake/CMakeLists.txt  |1 +
 Tests/RunCMake/CheckIPOSupported/CMakeLists.txt|3 +
 .../RunCMake/CheckIPOSupported/RunCMakeTest.cmake  |5 +
 .../cmp0069-is-old-result.txt} |0
 .../CheckIPOSupported/cmp0069-is-old-stderr.txt|5 +
 .../CheckIPOSupported/cmp0069-is-old.cmake |6 +
 .../not-supported-by-compiler-stderr.txt   |2 +-
 .../not-supported-by-generator-result.txt} |0
 ...r.txt => not-supported-by-generator-stderr.txt} |4 +-
 .../not-supported-by-generator.cmake   |6 +
 Tests/RunCMake/Framework/FrameworkLayout.cmake |5 +

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-631-gc791fb1

2017-03-31 Thread 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, next has been updated
  discards  eddbd8729d37dd4a4c0ada538868576ff1fe518c (commit)
  discards  45146a43e3b855b41320dcc7b4da1271048c63a3 (commit)
  discards  25e3b0b810e6e0c81890ef55c22ca40100757efd (commit)
  discards  d545708715c4bdc623ca68f2a0f6f848c6e87194 (commit)
   via  c791fb12544926bc5870a61735dc2ec62940a6f6 (commit)
   via  4a553ecb8e52dfd3ca605cd94ef8033e5febe937 (commit)
   via  a466d6f60abe13ddf5eb6bad7cca9743ef67f2f5 (commit)
   via  8772fc81c4ab745eb5abbae58c6a69706f610429 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (eddbd8729d37dd4a4c0ada538868576ff1fe518c)
\
 N -- N -- N (c791fb12544926bc5870a61735dc2ec62940a6f6)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

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

- Log -
---

Summary of changes:


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

Re: [CMake] Building third party libraries along with normal targets

2017-03-31 Thread Tamás Kenéz

[about shell script portability]

We do use shell-scripts on Windows since git-bash comes with git for free.
Our workflow is centered around the command-line (git-bash for Windows) and
you can run shell scripts in git-bash, that's why compatibility is not a
problem. All our scripts and workflows are the same on all our platforms
(windows, linux, mac).

This is an issue only if you're not using git on Windows so adding git-bash
to the workflow would be an extra hassle.

On Thu, Mar 30, 2017 at 3:45 PM, Robert Dailey 
wrote:

> On Thu, Mar 30, 2017 at 3:42 AM, Tamás Kenéz 
> wrote:
> > An alternative to the CMake superbuild: leave your actual project intact.
> > Simply create a separate shell script which builds all the dependencies
> (by
> > running cmake commands). Or, if you do like the ExternalProject stuff,
> > create a superbuild which builds only the dependencies.
>
> Problem with that is that it's not a portable solution. The #1 benefit
> of using CMake superbuilds (supplied with CMake build solution for the
> target library) is that it will function correctly on all platforms.
>
-- 

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] Linker error when building 3.8.0-rc4 on Linux

2017-03-31 Thread Nils Gladitz


On 03/31/2017 11:54 AM, Alan W. Irwin wrote:


Hi Nils:

And use of ExternalProject_Add, etc.  In other words, this is a pretty
crippling restriction for users with Linux distributions (such as the
quite recent Ubuntu 2016.10 of the original poster) that do not yet
give access to libssl version 1.1.0 (the oldest version of libssl
where HMAC_CTX_new() and HMAC_CTX_free() are available according to
your previous post).


Strangely enough I have no issue on Ubuntu 16.04 with the system default 
installation of OpenSSL.


What I missed in the original post is that the error comes from 
libarchive rather than libcurl.
But libarchive itself also seems to provide inline definitions of the 
missing functions in 
Utilities/cmlibarchive/libarchive/archive_openssl_hmac_private.h for 
OpenSSL < 1.1.


I can't tell why the inline definitions aren't used on the original 
posters system.

Perhaps there is a mismatch between OpenSSL headers and libraries?


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

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

2017-03-31 Thread Alan W. Irwin


On 2017-03-31 09:12+0200 Nils Gladitz wrote:


On 03/31/2017 09:04 AM, ウルヰ wrote:

To disable OpenSSL e.g. "cmake ... -DCMAKE_USE_OPENSSL=false" or 
"bootstrap

... --  -DCMAKE_USE_OPENSSL=false".

What would be the ramifications of building CMake without OpenSSL?


As far as I am aware it would mean no "https://; support in curl which would 
mean no "https://; support in e.g. file(DOWNLOAD) and CTest submissions.


Hi Nils:

And use of ExternalProject_Add, etc.  In other words, this is a pretty
crippling restriction for users with Linux distributions (such as the
quite recent Ubuntu 2016.10 of the original poster) that do not yet
give access to libssl version 1.1.0 (the oldest version of libssl
where HMAC_CTX_new() and HMAC_CTX_free() are available according to
your previous post).

@ The original poster, ウルヰ  (whose real name I do not know 
because he obviously
did not use the normal UTF-8 encoding for his mail address name):

I suggest you try the experiment of using the system version of
libcurl instead (which also supplies SSL capability). For example, my
Linux distribution is Debian Stable which only installs libssl 1.0.1.
And for that case when I tried the bootstrap method with the
--system-curl option (the usual way I build cmake), I do not confirm
your linking issue.  So my expectation is you will also avoid that
linking issue on Ubuntu 2016.10 if you use that bootstrap option or a
similar system libcurl option for the non-bootstrap case.

@Nils:

Even if the original poster finds the suggested workaround (of using
the system version of libcurl rather than system version of
libopenssl) works to provide key CMake SSL functionality, on general
principles (because Linux distribution support for libssl version
1.1.0 is obviously not widespread at the current time), I would
strongly suggest CMake developers drop use of HMAC_CTX_new() and
HMAC_CTX_free() throughout CMake for the final version of CMake-3.8.0.

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] ExternalProject_Add ... output directy (sln file directory)

2017-03-31 Thread Christophe Demez


Also,

I have try with a sample, just a main and a lib. But it seems that the 
lib CMakeLists.txt file is not called !


The project is created, but it does not point to the source code by 
example and the "message" are not displayed in the console too !


The download link :

https://www.dropbox.com/s/eto84gwtw2rx8oe/CMakeTest.zip?dl=0



On 30/03/2017 17:11, Christophe Demez wrote:


BTW,

I notice this too, if I use the following command line with an empty 
cmakelists.txt file : cmake -G "Visual Studio 15 2017 Win64"


And it also generate the .sln (and other files) in the same folder, 
but I don't request to build such a solution ! right ?


In reality, I only need a cmakelists.txt file that will build an 
external library for Android (Ninja generator, directly from 
AndroidStudio).

For now I use the wrong generator for test.


On 30/03/2017 16:20, David Cole wrote:

Do give it a BINARY_DIR, but do NOT give it a BUILD_COMMAND. Giving it
an empty BUILD_COMMAND means "do nothing" for the build step and using
"cmake --build ./LibraryBuild" does not work unless cmake is in your
PATH, and with a Visual Studio solution, you also need to specify
"--config Release" or "--config Debug"

Also posted on SO.


HTH,
David C.



On Thu, Mar 30, 2017 at 10:10 AM, Christophe Demez
  wrote:

Hi,

I'm currently using one CMakeLists.txt file that will execute an external
CMakeLists.txt (and dependency).

For this I use the ExternalProject_Add command, but I can't find a way to
specify where the ".sln" file will be generated.

I have also created StackOverflow question here with more information, if
someone have an idea for a solution ?

http://stackoverflow.com/questions/43117117/cmake-use-externalproject-add-and-specify-the-output-folder

Thanks
--

Powered bywww.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


--
Luciad Email Signature *Christophe Demez *
PROJECT LEADER

*LUCIAD*  CONNECT •  VISUALIZE •  ANALYZE •  ACT

christophe.de...@luciad.com  •  T 
+32 16 23 95 91
Follow us on LinkedIn or 
@LUCIADconnect 


Luciad




--
Luciad Email Signature *Christophe Demez *
PROJECT LEADER

*LUCIAD*  CONNECT •  VISUALIZE •  ANALYZE •  ACT

christophe.de...@luciad.com  •  T 
+32 16 23 95 91
Follow us on LinkedIn or 
@LUCIADconnect 


Luciad
-- 

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 exclude some files from building?

2017-03-31 Thread kipade

Oh, I got it. I think the first method was so cool.
Thank you very much.



At 2017-03-31 14:10:12, "Domen Vrankar"  wrote:

2017-03-31 4:41 GMT+02:00 kipade :

There are some files I do not want to build if the specified condition was ture.
For example, for testing, I want build a new file witch include a main entry 
just
for testing; if not, a new file would be compile for normal task.
I do not want to write two main entries in the same file just using macros to
control compiling. I want to use different clean and simple files.
So, how to do it?



You can either use generator expressions:

-

cmake_minimum_required(VERSION 3.5)

project(dependent CXX)

set(MY_DEPEND "ON" CACHE BOOL "toggle feature")

add_executable(
${PROJECT_NAME}
main.cpp
$<$:first/a.cpp>
$<$>:second/a.cpp>
  )

target_include_directories(
${PROJECT_NAME} PRIVATE "${CMAKE_CURRENT_SOURCE_DIR}"
  )

-


Or  add files to a variable:

-

cmake_minimum_required(VERSION 3.5)

project(dependent CXX)

set(MY_DEPEND "ON" CACHE BOOL "toggle feature")


if(MY_DEPEND)

  set(extra_src_ "first/a.cpp")

else()

  set(extra_src_ "second/a.cpp")

endif()


add_executable(
${PROJECT_NAME}
main.cpp

${extra_src_}

  )

target_include_directories(
${PROJECT_NAME} PRIVATE "${CMAKE_CURRENT_SOURCE_DIR}"
  )

-


Regards,

Domen
-- 

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] Linker error when building 3.8.0-rc4 on Linux

2017-03-31 Thread Nils Gladitz


On 03/31/2017 09:04 AM, ウルヰ wrote:


To disable OpenSSL e.g. "cmake ... -DCMAKE_USE_OPENSSL=false" or "bootstrap
... --  -DCMAKE_USE_OPENSSL=false".

What would be the ramifications of building CMake without OpenSSL?


As far as I am aware it would mean no "https://; support in curl which 
would mean no "https://; support in e.g. file(DOWNLOAD) and CTest 
submissions.


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

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

2017-03-31 Thread ウルヰ

> To disable OpenSSL e.g. "cmake ... -DCMAKE_USE_OPENSSL=false" or "bootstrap
> ... --  -DCMAKE_USE_OPENSSL=false".

What would be the ramifications of building CMake without OpenSSL?
-- 

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] Linker error when building 3.8.0-rc4 on Linux

2017-03-31 Thread Nils Gladitz


On 03/31/2017 07:46 AM, ウルヰ wrote:


../Utilities/cmlibarchive/libarchive/libcmlibarchive.a(archive_hmac.c.o):
In function `__hmac_sha1_init':
archive_hmac.c:(.text+0x25): undefined reference to `HMAC_CTX_new'
../Utilities/cmlibarchive/libarchive/libcmlibarchive.a(archive_hmac.c.o):
In function `__hmac_sha1_cleanup':
archive_hmac.c:(.text+0x12d): undefined reference to `HMAC_CTX_free'
collect2: error: ld returned 1 exit status
Source/CMakeFiles/ccmake.dir/build.make:422: recipe for target
'bin/ccmake' failed
make[2]: *** [bin/ccmake] Error 1
CMakeFiles/Makefile2:2314: recipe for target
'Source/CMakeFiles/ccmake.dir/all' failed
make[1]: *** [Source/CMakeFiles/ccmake.dir/all] Error 2
Makefile:162: recipe for target 'all' failed
make: *** [all] Error 2

Is this a bug with the build configuration or have I forgotten to do
something I need to do?


According to the OpenSSL documentation HMAC_CTX_new() and 
HMAC_CTX_free() were introduced in 1.1.0.
Presumably your OpenSSL version is older than that and disabling OpenSSL 
(presuming you don't need it) or building against a newer version should 
help.


To disable OpenSSL e.g. "cmake ... -DCMAKE_USE_OPENSSL=false" or 
"bootstrap ... --  -DCMAKE_USE_OPENSSL=false".
To point CMake at a custom OpenSSL installation instead setting the 
CMAKE_PREFIX_PATH environment to the installation should work.


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

Re: [CMake] How to exclude some files from building?

2017-03-31 Thread Domen Vrankar

2017-03-31 4:41 GMT+02:00 kipade :

> There are some files I do not want to build if the specified condition was
> ture.
> For example, for testing, I want build a new file witch include a main
> entry just
> for testing; if not, a new file would be compile for normal task.
> I do not want to write two main entries in the same file just using macros
> to
> control compiling. I want to use different clean and simple files.
> So, how to do it?
>


You can either use generator expressions:

-

cmake_minimum_required(VERSION 3.5)

project(dependent CXX)

set(MY_DEPEND "ON" CACHE BOOL "toggle feature")

add_executable(
${PROJECT_NAME}
main.cpp
$<$:first/a.cpp>
$<$>:second/a.cpp>
  )

target_include_directories(
${PROJECT_NAME} PRIVATE "${CMAKE_CURRENT_SOURCE_DIR}"
  )

-

Or  add files to a variable:

-

cmake_minimum_required(VERSION 3.5)

project(dependent CXX)

set(MY_DEPEND "ON" CACHE BOOL "toggle feature")

if(MY_DEPEND)
  set(extra_src_ "first/a.cpp")
else()
  set(extra_src_ "second/a.cpp")
endif()

add_executable(
${PROJECT_NAME}
main.cpp
${extra_src_}
  )

target_include_directories(
${PROJECT_NAME} PRIVATE "${CMAKE_CURRENT_SOURCE_DIR}"
  )

-

Regards,
Domen
-- 

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, master, updated. v3.8.0-rc4-632-g20326cf

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-644-g37df168

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc4-631-gc791fb1

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc4-643-ged76ca4

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-643-ged76ca4

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-641-g5aa11aa

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-639-g9ec9018

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-637-g38bbe41

Re: [cmake-developers] Problems with CTestTestParallel

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-635-gcb99a24

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-633-g20e7a6d

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-631-gc791fb1

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-631-gc791fb1

Re: [CMake] Building third party libraries along with normal targets

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

Re: [CMake] ExternalProject_Add ... output directy (sln file directory)

Re: [CMake] How to exclude some files from building?

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

Re: [CMake] Linker error when building 3.8.0-rc4 on Linux

Re: [CMake] How to exclude some files from building?

25 matches

Site Navigation

Mail list logo

Footer information