[cmake-developers] [CMake 0014899]: $TARGET_PROPERTY:prop with add_custom_target does not work
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14899
==
Reported By:Kiron
Assigned To:
==
Project:CMake
Issue ID: 14899
Category: CMake
Reproducibility:always
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2014-04-28 08:22 EDT
Last Modified: 2014-04-28 08:22 EDT
==
Summary:$TARGET_PROPERTY:prop with add_custom_target does
not work
Description:
When using the $TARGET_PROPERTY:FOO generator expression inside an
add_custom_target command the following error is produced:
CMake Error at CMakeLists.txt:6 (add_custom_target):
Error evaluating generator expression:
$TARGET_PROPERTY:FOO
$TARGET_PROPERTY:prop may only be used with targets. It may not be used
with add_custom_command. Specify the target to read a property from using
the $TARGET_PROPERTY:tgt,prop signature instead.
I would expect that with add_custom_target command the short hand form should
work (like error message says already, ... may only be used with targets).
Steps to Reproduce:
Save this as a CMakeLists.txt and run cmake:
cmake_minimum_required(VERSION 2.8 FATAL_ERROR)
project(Foo NONE)
add_custom_target(foo
COMMAND ${CMAKE_COMMAND} -E echo $TARGET_PROPERTY:FOO
)
set_property(TARGET foo PROPERTY FOO foobar)
Additional Information:
Problem exists with cmake version 2.8.12.1, 3.0.20140422-g9f9532, and
3.0.20140424-gb4aa99
==
Issue History
Date ModifiedUsername FieldChange
==
2014-04-28 08:22 Kiron New Issue
==
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CMake identifies MacOSX10.7-Xcode43-ub as GNU, but it runs clang.
On 04/26/2014 08:55 AM, Stephen Kelly wrote: Stephen Kelly wrote: Could this be because it is old clang which did not define __clang__? Apart from the misidentification, I don't understand how the WriteCompilerDetectionHeader test could have a different result than the compiler identification code. It should be checking the same defines in the same order, and it should arrive at the same incorrect conclusion that the compiler is GNU. That machine seems to partly be using llvm-gcc. At least that is what is used for the identification step, which is why it identifies as GNU. Ugh. That Xcode selects a different compiler when the project file sets SDKROOT than when it does not. The compiler id step runs very early so Darwin.cmake has not been loaded to set CMAKE_OSX_SYSROOT. When that is later used then the actual generated project files get SDKROOT and Xcode changes the compiler. For the compiler id step Xcode chooses com.apple.compilers.llvmgcc42 but the build uses com.apple.compilers.llvm.clang.1_0.compiler. It looks like in this case users will have to tell Xcode what tool to use up front using the CMake generator toolset feature (cmake -T). I think this is acceptable because it only affects old Xcode versions. Otherwise we will need a much more complicated compiler id bootstrap process :( I've updated the dashboard script on the build in question to specify the clang compiler explicitly. Please drop the non-APPLE condition for the test to see if it works now. -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/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CMP0043 warnings everywhere
-Original Message- From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of Brad King Sent: Wednesday, April 23, 2014 11:06 AM To: cmake-developers@cmake.org Subject: Re: [cmake-developers] CMP0043 warnings everywhere On 04/23/2014 12:57 PM, James Bigler wrote: I'm getting tons of CMP0043 warnings on my existing project. I have cmake_policy(VERSION 2.6) set in my project. Why am I being pestered by warnings? Shouldn't I get a policy value appropriate for 2.6 (so CMP0043 should be set to OLD)? Setting policies by VERSION leaves policies newer than that version unset, not set to OLD. If it were to set them to OLD then no new policies would ever warn. There is intentionally no way to turn off warnings about policies newer than those known to the project code, except by using -Wno-dev locally. Otherwise developers would never see the warnings and know to update their code. I thought the purpose of policies was to keep some backward compatibility feature, but allow users to select the new behavior. In this case, setting the behavior for new policies to OLD seems the most logical, especially when I asked for it with cmake_policy(VERSION). Now I'm forced to set this policy to OLD in order to not have a million warnings spam my team. This seems like a non-backward compatible decision. Is there a way to not have all these developer warnings on by default? I'm not sure how CMake distinguishes between who is a developer and who isn't. --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- 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/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] Explanation....
On Thursday, 24. April 2014, 17:34:40, Matthew Woehlke wrote:
On 2014-04-24 04:53, Johannes Zarl wrote:
On Wednesday, 23. April 2014, 18:54:39, Matthew Woehlke wrote:
if ( ${arg} STREQUAL TOTO)
set( TOTO evil)
You sure? When I checked, this did not work.
Are *you* sure? :-)
Yes, I am. For the specific use-case given in this thread (the STREQUAL), the
prefix *is* safe to use. I still prefer the MATCHES syntax, as it is not too
much overhead and prods the programmer to think about why it was used and what
is happening.
And of course, David Cole is totally right when he says:
It's just ridiculous to waste time trying to justify the existing
behavior. It's more confusing than useful, and ought to be changed.
Right; *explicit* expansion is limited in what characters are allowed.
As David Cole points out, you must expand such variables indirectly. Of
course, implicit expansion counts as indirect expansion, which is why
there is no safe character/prefix that can guarantee implicit expansion
won't occur.
I'm always happy to learn something new. How would you manage to make the
following if statement trigger?
set( arg value)
if ( ${arg} STREQUAL TOTO )
message ( arg equals 'TOTO', and arg equals 'value' )
endif()
(And - again as David Cole already noted - you didn't get an error in
the set() command, did you?)
No, but the if statement didn't trigger, either.
On 2014-04-24 06:31, David Cole wrote:
I, for one, would fully support breaking backwards compatibility to fix
this, and be strict with variable and macro and function name
identifiers.
Of course, the *real* problem is implicit expansion. The permissiveness
of variable naming makes it harder to work around this, but would be
less of an issue if implicit expansion was less eager.
I aggree 100% with both of you, here.
Cheers,
Johannes
--
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://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Explanation....
I'm always happy to learn something new. How would you manage to make
the following if statement trigger?
set( arg value)
if ( ${arg} STREQUAL TOTO )
message ( arg equals 'TOTO', and arg equals 'value' )
endif()
By having a variable named value that you didn't know about...
This makes it print out:
set( value TOTO)
set( arg value)
if ( ${arg} STREQUAL TOTO )
message ( arg equals 'TOTO', and arg equals 'value' )
endif()
:-)
Ridiculous, I know, but possible, and therefore, I'm sure somebody has
seen the unexpected as a result of this feature...
Cheers,
David C.
--
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://www.cmake.org/mailman/listinfo/cmake
[CMake] sigil ($) in add custom command
Through trial and error, I've found that I can do the following to
escape a variable in a custom command.
ADD_CUSTOM_COMMAND(
...
COMMAND bash -c 'for i in ${FILES}\; do cpp -P -CC -DDPI_EXTERN $$i
${FILEEXTERN}.tmp \; done'
...
)
Is this the proper way to escape a variable that needs to make to the
shell command level? I'm assuming this would only work through a Unix
Makefile? Is there an alternative to iterating over a variable in a
custom command?
--
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://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] sigil ($) in add custom command
foreach( file ${files} )
ADD_CUSTOM_COMMAND(
...
COMMAND cpp -P -CC -DDPI_EXTERN ${file}
${FILEEXTERN}.tmp \; done'
)
On Mon, Apr 28, 2014 at 9:05 AM, j s j.s4...@gmail.com wrote:
Through trial and error, I've found that I can do the following to
escape a variable in a custom command.
ADD_CUSTOM_COMMAND(
...
COMMAND bash -c 'for i in ${FILES}\; do cpp -P -CC -DDPI_EXTERN $$i
${FILEEXTERN}.tmp \; done'
...
)
Is this the proper way to escape a variable that needs to make to the
shell command level? I'm assuming this would only work through a Unix
Makefile? Is there an alternative to iterating over a variable in a
custom command?
--
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://www.cmake.org/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://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Explanation....
On 2014-04-28 04:58, Johannes Zarl wrote:
I'm always happy to learn something new. How would you manage to make the
following if statement trigger?
set( arg value)
if ( ${arg} STREQUAL TOTO )
message ( arg equals 'TOTO', and arg equals 'value' )
endif()
Exactly how you would expect:
set( TOTO value)
...and it does trigger:
$ cmake -P evil.cmake
arg equals 'TOTO', and arg equals 'value'
No, but the if statement didn't trigger, either.
Well, yes, but that's because I caused arg to be compared against 'evil'
instead of 'TOTO'. Since arg is set to 'value', it still didn't match.
The previous example was more metaphorical.
--
Matthew
--
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://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] sigil ($) in add custom command
The i
On Mon, Apr 28, 2014 at 11:44 AM, J Decker d3c...@gmail.com wrote:
foreach( file ${files} )
ADD_CUSTOM_COMMAND(
...
COMMAND cpp -P -CC -DDPI_EXTERN ${file}
${FILEEXTERN}.tmp \; done'
)
Unfortunately that doesn't work for me since all of the individual
files are writing to the same file. The output file is
non-deterministic in content and subject to race conditions. I would
need a foreach loop in the custom command itself to ensure that the
files are properly ordered. Is anything like this possible?
ADD_CUSTOM_COMMAND(
OUTPUT ${FILEEXTERN}.tmp
FOREACH(I ${FILES})
COMMAND cpp -P -CC -DDPI_EXTERN ${I} ${FILEEXTERN}.tmp \; done'
ENDFOREACH(I ${FILES})
DEPENDS ${FILES}
)
Regards,
Juan
On Mon, Apr 28, 2014 at 9:05 AM, j s j.s4...@gmail.com wrote:
Through trial and error, I've found that I can do the following to
escape a variable in a custom command.
ADD_CUSTOM_COMMAND(
...
COMMAND bash -c 'for i in ${FILES}\; do cpp -P -CC -DDPI_EXTERN $$i
${FILEEXTERN}.tmp \; done'
...
)
Is this the proper way to escape a variable that needs to make to the
shell command level? I'm assuming this would only work through a Unix
Makefile? Is there an alternative to iterating over a variable in a
custom command?
--
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://www.cmake.org/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://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Are the [Project name]_SOURCE_DIR variables stored in the cache ?
On 2014-04-23 14:18, Glenn Coombs wrote: Are the [Project name]_SOURCE_DIR variables being automatically stored in the cmake cache? Running 'grep _SOURCE_DIR CMakeCache.txt' would answer this question. (And yes, they are.) -- Matthew -- 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://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] sigil ($) in add custom command
the commands are done sequentially... or you could invent fictional target
names based on the filename, and chain current to prior
(I guess if you used -j 4 or something the commands might not be sequential)
is there a way to force 1 job?
On Mon, Apr 28, 2014 at 10:43 AM, j s j.s4...@gmail.com wrote:
The i
On Mon, Apr 28, 2014 at 11:44 AM, J Decker d3c...@gmail.com wrote:
foreach( file ${files} )
ADD_CUSTOM_COMMAND(
...
COMMAND cpp -P -CC -DDPI_EXTERN ${file}
${FILEEXTERN}.tmp \; done'
)
Unfortunately that doesn't work for me since all of the individual
files are writing to the same file. The output file is
non-deterministic in content and subject to race conditions. I would
need a foreach loop in the custom command itself to ensure that the
files are properly ordered. Is anything like this possible?
ADD_CUSTOM_COMMAND(
OUTPUT ${FILEEXTERN}.tmp
FOREACH(I ${FILES})
COMMAND cpp -P -CC -DDPI_EXTERN ${I} ${FILEEXTERN}.tmp \; done'
ENDFOREACH(I ${FILES})
DEPENDS ${FILES}
)
Regards,
Juan
On Mon, Apr 28, 2014 at 9:05 AM, j s j.s4...@gmail.com wrote:
Through trial and error, I've found that I can do the following to
escape a variable in a custom command.
ADD_CUSTOM_COMMAND(
...
COMMAND bash -c 'for i in ${FILES}\; do cpp -P -CC -DDPI_EXTERN $$i
${FILEEXTERN}.tmp \; done'
...
)
Is this the proper way to escape a variable that needs to make to the
shell command level? I'm assuming this would only work through a Unix
Makefile? Is there an alternative to iterating over a variable in a
custom command?
--
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://www.cmake.org/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://www.cmake.org/mailman/listinfo/cmake
[Cmake-commits] CMake branch, next, updated. v3.0.0-rc4-2584-g8723298
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 8723298cd6c9874ead0462483b866c5988351263 (commit)
via 6a5bd7f0dacd96b66c294919fa5859ca12224d5f (commit)
via 041dfea55b689fc1e0376c6f68c2e65b38a0507d (commit)
from b4aa9984f257d28ad8020be348b5d7ba54327325 (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 -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8723298cd6c9874ead0462483b866c5988351263
commit 8723298cd6c9874ead0462483b866c5988351263
Merge: b4aa998 6a5bd7f
Author: Peter Kuemmel syntheti...@gmx.net
AuthorDate: Mon Apr 28 09:52:47 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Apr 28 09:52:47 2014 -0400
Merge topic 'dont-rewrite-moc-parameter-file' into next
6a5bd7f0 Qt4: write moc parameter file only when content has changed
041dfea5 CMake Nightly Date Stamp
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6a5bd7f0dacd96b66c294919fa5859ca12224d5f
commit 6a5bd7f0dacd96b66c294919fa5859ca12224d5f
Author: Peter Kümmel syntheti...@gmx.net
AuthorDate: Fri Apr 25 18:24:56 2014 +0200
Commit: Peter Kümmel syntheti...@gmx.net
CommitDate: Fri Apr 25 18:24:56 2014 +0200
Qt4: write moc parameter file only when content has changed
diff --git a/Modules/Qt4Macros.cmake b/Modules/Qt4Macros.cmake
index b1b12d6..8c4daac 100644
--- a/Modules/Qt4Macros.cmake
+++ b/Modules/Qt4Macros.cmake
@@ -135,7 +135,9 @@ function (QT4_CREATE_MOC_COMMAND infile outfile moc_flags
moc_options moc_target
set(targetincludes)
set(targetdefines)
else()
-file(WRITE ${_moc_parameters_file} ${_moc_parameters}\n)
+set(CMAKE_CONFIGURABLE_FILE_CONTENT ${_moc_parameters})
+configure_file(${CMAKE_ROOT}/Modules/CMakeConfigurableFile.in
+ ${_moc_parameters_file} @ONLY)
endif()
set(_moc_extra_parameters_file @${_moc_parameters_file})
---
Summary of changes:
Modules/Qt4Macros.cmake |4 +++-
Source/CMakeVersion.cmake |2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v3.0.0-rc4-2586-g881bf7f
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 881bf7ffe1c85109bde5b28916ed6a802c47a850 (commit) via a63a16f66ac5565472d2dc04f1493ae48eefd6ff (commit) from 8723298cd6c9874ead0462483b866c5988351263 (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=881bf7ffe1c85109bde5b28916ed6a802c47a850 commit 881bf7ffe1c85109bde5b28916ed6a802c47a850 Merge: 8723298 a63a16f Author: Stephen Kelly steve...@gmail.com AuthorDate: Mon Apr 28 14:48:16 2014 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Apr 28 14:48:16 2014 -0400 Merge topic 'WriteCompilerDetectionHeader-module' into next a63a16f6 Test on APPLE. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a63a16f66ac5565472d2dc04f1493ae48eefd6ff commit a63a16f66ac5565472d2dc04f1493ae48eefd6ff Author: Stephen Kelly steve...@gmail.com AuthorDate: Mon Apr 28 20:47:44 2014 +0200 Commit: Stephen Kelly steve...@gmail.com CommitDate: Mon Apr 28 20:47:44 2014 +0200 Test on APPLE. diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt index 27c87a0..f5271b5 100644 --- a/Tests/CMakeLists.txt +++ b/Tests/CMakeLists.txt @@ -411,7 +411,7 @@ if(BUILD_TESTING) ADD_TEST_MACRO(Module.GenerateExportHeader GenerateExportHeader) ADD_TEST_MACRO(Module.FindDependency FindDependency) - if (CMAKE_CXX_COMPILER_ID STREQUAL GNU AND UNIX AND NOT APPLE) + if (CMAKE_CXX_COMPILER_ID STREQUAL GNU) ADD_TEST_MACRO(Module.WriteCompilerDetectionHeader WriteCompilerDetectionHeader) endif() if (APPLE OR CMAKE_CXX_COMPILER_ID MATCHES GNU) --- Summary of changes: Tests/CMakeLists.txt |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.0.0-rc4-729-gc51d07d
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 c51d07d4397ceed55c534a036ef81df44b741ff6 (commit) from bb1c41a085c6eb9296bf701ea7633f715a06f6e1 (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 - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c51d07d4397ceed55c534a036ef81df44b741ff6 commit c51d07d4397ceed55c534a036ef81df44b741ff6 Author: Kitware Robot kwro...@kitware.com AuthorDate: Tue Apr 29 00:01:08 2014 -0400 Commit: Kitware Robot kwro...@kitware.com CommitDate: Tue Apr 29 00:01:08 2014 -0400 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index f6f3a70..1e0d885 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 0) -set(CMake_VERSION_PATCH 20140428) +set(CMake_VERSION_PATCH 20140429) #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/cgi-bin/mailman/listinfo/cmake-commits
