Brad King wrote:
On 02/10/2014 03:41 AM, Stephen Kelly wrote:
diff --git a/Source/cmAddCustomCommandCommand.cxx
b/Source/cmAddCustomCommandCommand.cxx
index 5634849..e967e3c 100644
--- a/Source/cmAddCustomCommandCommand.cxx
+++ b/Source/cmAddCustomCommandCommand.cxx
@@ -164,6 +164,7
On 02/11/2014 02:37 AM, Jayesh PATEL wrote:
I'd like to include you in my network to share updates and stay in touch.
http://community.linkedin.com/questions/19313/how-do-i-stop-linkedin-sending-out-invitation-emai.html
-Brad
--
Powered by www.kitware.com
Visit other Kitware open-source
On 02/11/2014 07:16 AM, Stephen Kelly wrote:
Ok, I'm not sure how to handle these two items. I've never used the SOURCE
signature of add_custom_command, and the AddCustomCommandOldStyle method
seems to also relate to things I haven't used before, so I wouldn't know how
to explain the
Brad King wrote:
target_link_libraries(staticB INTERFACE staticA)
However, that will propagate all usage requirements of A to consumers
of B. Depending on the usage requirements specified for A and B that
may be correct or not.
We could consider making the LINK_ONLY generator expression
The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=14749
==
Reported By:Mathieu Malaterre
Assigned To:
On 02/11/2014 08:46 AM, Stephen Kelly wrote:
We could consider making the LINK_ONLY generator expression public in order
to allow the user to decide the granularity here (possibly encapsulated in a
INTERFACE_LIBRARY).
For reference, without the interface target it is as simple as:
Brad King wrote:
On 02/11/2014 08:46 AM, Stephen Kelly wrote:
We could consider making the LINK_ONLY generator expression public in
order to allow the user to decide the granularity here (possibly
encapsulated in a INTERFACE_LIBRARY).
For reference, without the interface target it is as
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14750
==
Reported By:Orion Poplawski
Assigned To:
Brad King wrote:
// For backwards compatibility replace varibles in source names.
- // This should eventually be removed.
+ // TODO: This should eventually be removed.
this-Makefile-ExpandVariablesInString(src);
A policy should be added to remove this behavior.
Any idea how to unit test
On 02/11/2014 11:48 AM, Stephen Kelly wrote:
Confirmed. I added CMP0049 to control this behavior.
Great.
Please include a Help/release/dev/backward-compatibility.rst
file with the relevant release note.
Thanks,
-Brad
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
Brad King wrote:
On 02/11/2014 11:48 AM, Stephen Kelly wrote:
Confirmed. I added CMP0049 to control this behavior.
Great.
Please include a Help/release/dev/backward-compatibility.rst
file with the relevant release note.
Will this make it into 3.0.0? Should I just add it to the existing
On 02/11/2014 12:00 PM, Stephen Kelly wrote:
Will this make it into 3.0.0?
Likely, since it is in the spirit of the other legacy cleanup
policies. If not we can always bump the policy version before
final integration.
Should I just add it to the existing release notes on master if so?
No,
On 02/11/2014 01:18 PM, Brad King wrote:
On 02/11/2014 12:00 PM, Stephen Kelly wrote:
Should I just add it to the existing release notes on master if so?
No, thanks. I'd like to get everyone in the habbit of adding
notes to the dev/ files and myself in the habbit of integrating
the notes.
Hi,
I've just pushed two branches into next:
dev/custom-parsers
Replaces the parsers in cmMakefile::ExpandVariablesInString with
custom code rather than lex/yacc. The parsers in
cmGeneratorExpression::StripEmptyListElements
cmSystemTools::ExpandListArguments
On 02/11/2014 02:49 PM, Ben Boeckel wrote:
dev/custom-parsers
cmMakefile::ExpandVariablesInString has long been ripe for
optimization. Thanks for working on it.
Why does each level in the openstack need to hold its lookup
member? Can't everything be stored in-place in the work buffer?
Each
On Tue, Feb 11, 2014 at 15:54:40 -0500, Brad King wrote:
Why does each level in the openstack need to hold its lookup
member? Can't everything be stored in-place in the work buffer?
Each openstack level just needs to track the start character in
the work buffer. When that level is closed the
On Feb 8, 2014, at 4:10 AM, Stephen Kelly steve...@gmail.com wrote:
Great, thanks for all of that. I have force-pushed your branch, which means
you need to do this before proceeding with further work.
1) Get remote changes, including my change to your branch.
You'll see output
On Tue, Feb 11, 2014 at 17:18:22 -0500, Matthew Woehlke wrote:
On a loosely related note, did you know that there are now at least
two Python parsers for CMake script? (Besides I believe a C++ one in
KDevelop...)
1. https://github.com/ijt/cmakelists_parsing
2.
Thank you, that fixed the problem I was seeing.
SteveW
On Feb 10, 2014, at 8:28 AM, Brad King brad.k...@kitware.com wrote:
On 02/07/2014 05:19 PM, Steve Wilson wrote:
On Feb 7, 2014, at 3:01 PM, Brad King wrote:
-DCMAKE_BUILD_TYPE=\${CTEST_CONFIGURATION_TYPE}
I have tried adding that to
I just pushed the topic AddCustomCommandWithConfig to stage. This topic
implements the CONFIG keyword for add_custom_command().
SteveW
signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
On Tue, Feb 11, 2014 at 19:16:49 -0500, Matthew Woehlke wrote:
On 2014-02-11 17:54, Ben Boeckel wrote:
Parsing in CMake is split into separate sections: the part which parses
the lines into CMake's command calls and the part which expands
variables (which is why ${cmd}(${args}) isn't allowed).
I owe you a beer! Thank you. Many, many hours saved here. And of course yeah, I
feel dumb for not having grokked in fullness.
/me starts the day on a high note
From: Petr Kmoch [mailto:petr.km...@gmail.com]
Sent: Tuesday, February 11, 2014 1:57 AM
To: Phil Smith
Cc: cmake@cmake.org
Subject: Re:
- Original Message -
Hello,
I don't know if I overlook something or the framework/CFBundle support on Mac
OS is rarely.
Most of the things I have already implemented as post-build commands but are
there also CMake ways of doing such things?
.) Adding resources to CFBundles?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
op 10-02-14 13:38, David Cole schreef:
Should I file this as a bug in the issue tracker then?
Sure. Especially if you have an easy way to reproduce. (Either
reference an external, publicly available project we can just
build and get it to
You can use add_custom_command as POST_BUILD step and TargetGenerators for the
main GUI bundle to do what you want.
Best Regards
Am 09.02.2014 um 23:56 schrieb Andreas Pakulat ap...@gmx.de:
Hi Bill,
On Sun, Feb 9, 2014 at 8:45 PM, Bill Somerville b...@classdesign.com wrote:
Hi,
noob
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 0586081cab2a622c04be0640aa05dd1f0ed5ab34 (commit)
via
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 6aa66934d984cb2b24075577adae2e89d4bcb28e (commit)
via
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 8950be80eb213f1a54289c25da2a4b01dcfce65b (commit)
via
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 e44bbec0134200c2f2f320d4364117888ab99248 (commit)
via
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 cef89d4a1c6857dbd97f469d1aa438fd2d0b8b7b (commit)
via
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 c29eb751cdaff74b3113f6199881f76b427a8391 (commit)
via
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 418a155be7e44117297c072b6aa0f21f4407c052 (commit)
via
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 a12dd791dd32944f52ef5e1078a2e3a8eec2a8a1 (commit)
via
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 a9b056228d64ee12fcaf6c52393cca6a2b7232c7 (commit)
via
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 9e98a8d095adf12b79bcbef2bad31ded136cf5c7 (commit)
via
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 0fc09f7974f8a61cd2906650b1732e58acc6daa4 (commit)
via
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 6201a5f4b166b600ff0e31b2437107ac28d89735 (commit)
via
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 7362f0a07b892400134b5bc5c308633059eaa788 (commit)
via
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 d7d4d2297e2e11f1dec6a89a9f8d478f57966362 (commit)
via
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 4281217b9317518f23cebd03b48800bec9c871ea (commit)
via
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 d434df4ff8750bf96de5251847473addeeff69bd (commit)
via
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 1ec618612cdd61f4994324c727d812cf133077af (commit)
via
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 42f870c733978416e959bd8102ea57855d231632 (commit)
via
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 74ad0c21321e7d2978e2ba07cf2d91e08a52 (commit)
via
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 81132f4478ebcd8a3575c237e5b5c8978088c2a1 (commit)
via
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 6454cb0f491ca26c3ebd535d10a12139e68b23cb (commit)
via
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 febff8f368adb484bf6c46af60949f870dd0154b (commit)
via
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 765971c021ebf386f3f2a3e5bedd2152ff367b21 (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 33c4db5..4bbbd75 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
set(CMake_VERSION_MAJOR 2)
set(CMake_VERSION_MINOR 8)
set(CMake_VERSION_PATCH 12)
-set(CMake_VERSION_TWEAK 20140211
49 matches
Mail list logo
