On 10/10/2013 04:47 PM, Nils Gladitz wrote:
Thanks for the feedback!
I'll try to fix the commit message.
As far as I can tell there shouldn't be any lines longer than 79 characters.
I used the cmake developer script to set up my repository which seems to
have set up a hook script which
On 10/10/2013 08:07 PM, Stephen Kelly wrote:
So, I think this is a two dimensional calculation. There is a standard axis
and a extension axis for the compiler flag, for GCC and clang at least.
Yes.
if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.7)
On 10/11/2013 02:16 AM, Rolf Eike Beer wrote:
Brad, this is one of your dashboard machines. I currently can't find the
mails
where we discussed that. Can you please give Steven some information about
this?
Sorry, I have no idea to what dashboard machine, emails, feature, compiler,
or
On 10/11/2013 12:05 AM, clin...@elemtech.com wrote:
I've started some work towards supporting Unicode in CMake so I could get
better support for building/testing our internationalized applications.
https://github.com/clintonstimpson/CMake/commit/f08ca2ff65f434b2bc404000765a836880f78f0e
Wow,
2013/10/11 Brad King brad.k...@kitware.com:
On 10/11/2013 01:09 AM, Daniel Pfeifer wrote:
Will it still be able to generate DocBook, so companies can include
the documentation in their handbook?
It can generate whatever Sphinx can generate. IIRC Sphinx does not
currently support DocBook
Brad King wrote:
On 10/10/2013 08:55 PM, Stephen Kelly wrote:
Brad King brad.king@... writes:
I just checked the VS 6, 9 and 11 IDEs and it is possible to mark
a source file as excluded from certain configurations. Those versions
represent all the VS generators.
If listing all sources
Brad King wrote:
On 10/10/2013 08:07 PM, Stephen Kelly wrote:
So, I think this is a two dimensional calculation. There is a standard
axis and a extension axis for the compiler flag, for GCC and clang at
least.
Yes.
if (NOT CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.7)
Wow! Impressive...
Good luck getting this into CMake; I'd love to see UNICODE support through and
through.
:-)
David C.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the
On 10/11/2013 10:43 AM, Daniel Pfeifer wrote:
Comparing the expressiveness, extensability, and supported backends,
can you explain why you would prefer rST over AsciiDoc?
There is a good comparison chart here:
On 10/11/2013 10:56 AM, Stephen Kelly wrote:
I assume so. The only flag I'm aware of for XL is -qlanglvl=extended0x, and
that is equivalent to -std=c++11 afaik. What are you referring to
specifically?
I was just touching back on the issue you originally raised about
-qlanglvl=extended0x.
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14479
==
Reported By:Michael Priestman
Assigned To:
On Thursday 10 October 2013, Brad King wrote:
...
There are plenty of Wiki sites that can stage the documentation until
the new system is ready. I don't want to add --help-concepts just to
drop it again one release later or have to support it forever when the
new system has no explicit notion
On Thursday 10 October 2013, Pau Garcia i Quiles wrote:
Hello,
A few years ago, Ralf Habacker proposed and implemented a 7-zip generator
for CPack:
http://marc.info/?l=cmakem=124031321521852w=2
Despite positive review from Alexander Neundorf, it seems it was not
included. Was there any
On Fri, Oct 11, 2013 at 5:40 PM, Alexander Neundorf neund...@kde.orgwrote:
The thread looks somewhat unfinished, and Ralf simply didn't seem to reply
anymore, it would have needed just some more pushing to get it in.
What kind of pushing? Code polishing? Documentation? Tests?
--
Pau Garcia
On 10/11/2013 11:34 AM, Alexander Neundorf wrote:
On Thursday 10 October 2013, Brad King wrote:
The topic breaks some of the existing --help-* commands like --help-full,
Do you mean there won't be an all-in-one page anymore ?
There can be with a little more work beyond the current topic:
*
On Friday 11 October 2013, you wrote:
On Fri, Oct 11, 2013 at 5:40 PM, Alexander Neundorf neund...@kde.orgwrote:
The thread looks somewhat unfinished, and Ralf simply didn't seem to
reply anymore, it would have needed just some more pushing to get it in.
What kind of pushing? Code
Am Freitag, 11. Oktober 2013, 09:19:46 schrieb Brad King:
On 10/11/2013 02:16 AM, Rolf Eike Beer wrote:
Brad, this is one of your dashboard machines. I currently can't find the
mails where we discussed that. Can you please give Steven some
information about this?
Sorry, I have no idea to
On 10/11/2013 01:22 PM, Rolf Eike Beer wrote:
There is one dashboard machine that uses a combined gcc+clang compiler. I
remember having many problems when the tests error'ed out when the tests
suddenly showed support for features not expected in some compiler version.
If nothing comes
Steve,
Please extend the CMP0026 message to suggest file(GENERATE)
as a way of putting the target location in a generated file.
Some projects not supporting multi-config generators may
use LOCATION with configure_file.
Also, this policy means it will not be possible for a project
to support both
Hi Folks,
I think the time has come for a major version number bump to go with
some major updates. I propose to skip preparing 2.8.13 in 'master'
and go straight to 3.0.0. If necessary it would still be possible
to support 2.8.12.1+ or 2.8.13+ maintenance releases by basing topics
on older
Brad King wrote:
Steve,
Please extend the CMP0026 message to suggest file(GENERATE)
as a way of putting the target location in a generated file.
Some projects not supporting multi-config generators may
use LOCATION with configure_file.
Done.
Can the policy NEW behavior instead be to
On 10/11/2013 03:21 PM, Stephen Kelly wrote:
Brad King wrote:
Can the policy NEW behavior instead be to return the LOCATION
as a $TARGET_FILE:... generator expression?
I don't know. That seems like a lot of magic and bound to break existing
code.
get_property(loc TARGET myexe PROPERTY
Brad King wrote:
* New policies to disable old commands that require significant
amounts of C++ code to be kept around just to support them.
These include (but may not be limited to):
- exec_program: replaced by execute_process
- export_library_dependencies: replaced by
On 10/11/2013 03:34 PM, Rolf Eike Beer wrote:
Just out of curiosity: is the Lua integration affecting the set
of supported compilers?
There is no integration of Lua's source code in my outline. It is
only a change to the CMake language lexer/parser to handle Lua-style
long-bracket syntax. For
Am Freitag, 11. Oktober 2013, 12:07:58 schrieb Clark WANG:
See following example:
$ cmake --version
cmake version 2.8.11.2
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
FUNCTION(foo)
list(LENGTH ARGV argc)
message(ARGC=${ARGC} list(LENGTH
On Fri, Oct 11, 2013 at 2:20 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Am Freitag, 11. Oktober 2013, 12:07:58 schrieb Clark WANG:
See following example:
$ cmake --version
cmake version 2.8.11.2
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
On Fri, Oct 11, 2013 at 2:20 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Am Freitag, 11. Oktober 2013, 12:07:58 schrieb Clark WANG:
See following example:
$ cmake --version
cmake version 2.8.11.2
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
Am Freitag, 11. Oktober 2013, 14:49:18 schrieb Clark WANG:
On Fri, Oct 11, 2013 at 2:20 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Am Freitag, 11. Oktober 2013, 12:07:58 schrieb Clark WANG:
See following example:
$ cmake --version
cmake version 2.8.11.2
$ cat
Giordano Khouri wrote:
I'm surprised to see that there's no configuration specific COMPILE_FLAGS.
Please correct me if I'm wrong.
Correct, but not the whole story. When you upgrade to CMake 2.8.12 you can
use the COMPILE_OPTIONS target property.
I am currently in the process of getting the 2.8.12 documentation
generated and uploaded.
On Thu, Oct 10, 2013 at 7:36 PM, Mateusz Loskot mate...@loskot.net wrote:
Hi,
The latest version linked in the documentation [1] is 2.8.11.
Where can I find docs for the latest release?
[1]
On 11 October 2013 15:23, Robert Maynard robert.mayn...@kitware.com wrote:
I am currently in the process of getting the 2.8.12 documentation
generated and uploaded.
Sweet, thanks!
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
Powered by www.kitware.com
Please keep messages
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 1eed2247d63cf590532f1f1bb458c6d108d429ab (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 c748d415bb43d32c9a0f91f9a53353b95caa4cbe (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 d0c3d9aa946837bb9a5a06aaf88bfc42a40924bd (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 08ec9ce928ce3f8891cf9c441402221f979f3a86 (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 2857fd506b632088aa548490ea15be694ac51e7d (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 e977b7754e779f7cf6883d5fa87cd059a63749fb (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 552cb71f9b6f1885ac63e27454c76a6ee9cc8414 (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 c41a59c000739d1d246badfd7e3fde741196406b (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 32ea0dc..941aede 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 20131011
40 matches
Mail list logo
