On 11/26/2013 08:20 AM, Peter Kümmel wrote:
Will be fixed in QtCreator 3.0.
Thank you for the fix!
Nils
--
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 CMake FAQ at:
On 26.11.2013 09:17, Nils Gladitz wrote:
On 11/25/2013 06:31 PM, Nils Gladitz wrote:
On 25.11.2013 18:21, Peter Kümmel wrote:
Also this system is localized? I don't see any prefixes, e.g. here
http://open.cdash.org/testDetails.php?test=220476713build=3114166
The system indeed has a german
On 25/11/13 18:04, Jean-Christophe Fillion-Robin wrote:
After copying the ExternalProject.cmake in the Module directory of the
CMake installation I used for daily work, I didn't see any issue / side
effect.
Considering the external projects I am dealing with always specify the
SHA1, I
On 11/26/2013 09:41 AM, Nils Gladitz wrote:
On 11/26/2013 09:33 AM, Peter Kümmel wrote:
Seems the launcher breaks the ninja parser. Why are launcher needed?
I never used them.
The CTest launchers collect the output of each command (compiler call,
linker call, custom command).
That way
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14597
==
Reported By:tisi
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14598
==
Reported By:Moshe Rubin
Assigned To:
On 11/26/2013 10:16 AM, Nils Gladitz wrote:
The CTest launchers collect the output of each command (compiler call,
linker call, custom command).
I just now realized what this means in this case ...
When the launcher was running cmcldeps it did not see any /showincludes
output since it was
On 11/25/2013 07:01 PM, Pau Garcia i Quiles wrote:
I have implemented an EXTRACT_COMMAND for ExternalProject_Add.
It is useful in case you are downloading a file that CMake does
not know how to extract, but you do (e. g. NSIS installers that
can be extracted without installation,
On 11/25/2013 04:41 PM, Peter Kümmel wrote:
Ah, very comfortable. I updated next.
Great, thanks. The topic looks good now so I merged it to 'master'.
-Brad
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14599
==
Reported By:Galeazzi
Assigned To:
There is this 9 year old ticket about support for precompiled headers,
http://www.cmake.org/Bug/view.php?id=1260
And I wanna bring up a patch for discussion,
http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=d207f1bf8fd697ae6521a1336dd27222168f548e
With the two new source file
On 11/26/2013 12:32 PM, Peter Kuemmel wrote:
So, is this the right way to improve the pch situation?
Please summarize the situation here so we don't have to read the
entire history of issue 1260 and all the proposed approaches.
IIUC the modules in issue 1260 are all a workaround for lack for
Peter Kuemmel wrote:
So, is this the right way to improve the pch situation?
I don't know anything about PCH, but Daniel Pfeifer has a branch here:
https://github.com/purpleKarrot/CMake/tree/WIP-PCH-Support
Thanks,
Steve.
--
Powered by www.kitware.com
Visit other Kitware open-source
On 11/26/2013 12:32 PM, Peter Kuemmel wrote:
So, is this the right way to improve the pch situation?
Please summarize the situation here so we don't have to read the
entire history of issue 1260 and all the proposed approaches.
As you already said, many attempts to solve the problem with
On 11/26/2013 02:23 PM, Peter Kuemmel wrote:
I'm not sure if it is a good idea to implement the pch support
completely on the C++ side
It could be a combination of C++-coded logic plus lookups of
platform information variables set in Modules/Platform/*.cmake
and Modules/Compiler/*.cmake files.
It could be a combination of C++-coded logic plus lookups of
You mean lookups only form C++ the side?
platform information variables set in Modules/Platform/*.cmake
and Modules/Compiler/*.cmake files. Just about everything
CMake generates works this way.
With this property we have
I don't know anything about PCH
So PCHs were never relevant in your real world projects?
I also don't use them very often because of the non-existing
support of CMake. And too often you break the build when
someone builds without using PCHs.
On 11/26/2013 03:20 PM, Peter Kuemmel wrote:
That doesn't matter because IMO the properties are not suitable
for addition because they step on the toes of internal implementation
What properties would be needed for the IDEs?
And couldn't we make some properties internal only?
We can't
2013/11/26 Stephen Kelly steve...@gmail.com:
Peter Kuemmel wrote:
So, is this the right way to improve the pch situation?
I don't know anything about PCH, but Daniel Pfeifer has a branch here:
https://github.com/purpleKarrot/CMake/tree/WIP-PCH-Support
Thanks for pointing at this branch. I
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14600
==
Reported By:Charles Karney
Assigned To:
Hi all,
According to the CMake documentation, the TARGET property LOCATION for a
non-imported target is provided for compatibility with CMake 2.4 and
below. My question is: are there any plans to deprecate this property? I
want to know, because AFAIK, the only way to determine the full path to
a
In many of my subprojects I've got some sources outside of CMakeLists
directory. This is an example:
C:\Product1\project1\CMakeLists.txt
C:\SharedFiles\dir1\foo.cpp
C:\SharedFiles\dir1\foo.h
Unfortunately Eclipse doesn't show them in the Project Explorer view.
Should it be possible to request
2013/11/26 Andrea Galeazzi galea...@korg.it:
In many of my subprojects I've got some sources outside of CMakeLists
directory. This is an example:
C:\Product1\project1\CMakeLists.txt
C:\SharedFiles\dir1\foo.cpp
C:\SharedFiles\dir1\foo.h
This looks like an Eclipse issue?
Can you craft an
Yes, of course I can.
It's possibile to add both linked folder and linked file by hand (in
general they're named linked resources). Also CMake creates linked
folder in order to make the subprojects appear in the project explorer.
In this way the behavior of the Eclipse generator would be
2013/11/26 Andrea Galeazzi galea...@korg.it:
Yes, of course I can.
It's possibile to add both linked folder and linked file by hand (in general
they're named linked resources). Also CMake creates linked folder in order
to make the subprojects appear in the project explorer. In this way the
Hello all,
I’m following the directions posted here:
http://www.cmake.org/Wiki/CMake_Testing_With_CTest
I’d like to get my dashboard up on the public one:
http://open.cdash.org/index.php?project=PublicDashboard
I’ve obtained an account on CTest.
How do I register my project?
Thanks,
Adam
What an honor for me that you guys responded so quickly. Our group has done well to move to CMake. Sorry for taking such a long time to reply; I'm part of a big organization that can be slow to decide things.
The way this is going, is to continue with one package rather than use a workaround, if
In our project, we need to build an Win8+ Metro app. Currently the CMake do
support VS_WINRT_EXTENSIONS. However, if you want to build an exe instead
of dll or lib, even with x86 or x64, it always fails because lacking of
some tags in vcxproj and sln.
The requirements about it in our project are:
2013/11/27 j...@linuxwest.com:
What an honor for me that you guys responded so quickly. Our group has done
well to move to CMake. Sorry for taking such a long time to reply; I'm part
of a big organization that can be slow to decide things.
The way this is going, is to continue with one
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 17baa9f562374ec4fa46d6d9c693b15b209a1e00 (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 318f76940f8ce5fca31c02b8caf4ce007057642f (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 1a7f705303e1f443723f63df8cac6eb41170cdc2 (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 349628cbf5715edbacb9844fd5d84f604b8cdaec (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 e3b411c3a546e30425ebdc77d69b4c01ce785073 (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 170c50da38d0735059b7729c7429b75e77683af9 (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 e1fd64837d5bc2fcb425cf9ba24fc1d136e40bde (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 0ccc53573419132434528ca287a6bc03e2632768 (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 784e6e7f15fa9b655d2b51ee29756f0d777cb071 (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 779fd101603631bfd61dc0fb03f96ba762abc92e (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 3ad5f9a075e2aa9438aeb2522a6fecd2cff74f8b (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 235c2d26dca77507ab998d6c980827086989e27f (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 9498344c9d5bec0d1d644e9e512411973721fec4 (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 8b585eed447603579c438e7ff5216927cf6b0a69 (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 3eca31f81a623e91e1b76fd6012a0645aa8d6432 (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 d86cac8a3c189ed65f0107c5116327f256d3a5d0 (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 83a37d78c0580294d75568d7cfb7e9921904b036 (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 fd2ffb42aa8f8927f2ca3bf0c183957da88da2c0 (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 26940a17b5f6bdc31de8ef2ed934f2161c4109e4 (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 c42b2b21cb10f1a7215145aeefbd35a512a538c0 (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 b80ef72b4d8e76bf5912d6d59a749a2d94bb49b2 (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 8c3c22b94e9e01e787d0db17ae67a18d63c6ff27 (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 ff31bfedbf86e48fae4533080de1ff969ea51d20 (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 d109c9b4997f56ac7b013a43f1e1d6924685b413 (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 ba191a11f0232e9b439dd9a7ba426b4ab7c7ead9 (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 4fc14932cb4a84d93731dc08b6cf3eb3fd03be2a (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 c1e71bdcf6de4dfd9f7d99ab562401ac7fe6dd1d (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 96265d7..43004cc 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 20131126
57 matches
Mail list logo
