Hi there,
it would be useful for KDE Frameworks to have ALIAS targets in CMake 2.8.12.
http://thread.gmane.org/gmane.comp.kde.devel.core/80233/focus=80247
I finished the topic and pushed it to next in case it can go into that
release.
I won't be available most of today to change it if
On 08/01/2013 05:26 AM, Stephen Kelly wrote:
it would be useful for KDE Frameworks to have ALIAS targets in CMake 2.8.12.
http://thread.gmane.org/gmane.comp.kde.devel.core/80233/focus=80247
I finished the topic and pushed it to next in case it can go into that
release.
I won't be
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14331
==
Reported By:d3x0r
Assigned To:
Alexander Neundorf wrote:
On Friday 19 July 2013, Rolf Eike Beer wrote:
Ok, I've pushed an updated version to the rework branch. A test for the
component check is missing, but all of your other suggestions should have
been addressed.
The variable is case-sensitive, so it is
thank you Zaak!
you are right, after some more reading on this issue i should stick to .f90
as you suggest.
thank you for the clarification.
best regards,
radovan
On Wed, Jul 31, 2013 at 10:44 PM, Zaak Beekman zbeek...@gmail.com wrote:
dear all,
it seems that CMake currently does not
Hi list,
I'm using Visual Studio 2010 to create Python modules in C++. In order to
run those modules, I need to execute something like:
C:\Python33\python.exe some_script_that_uses_the_module.py
To generate the VS2010 solution we use CMake. What I'm looking for is to
configure the above command
Hello,
I set up cmake to use a external project. This 3rd party library writes out a
file which contains all include paths set by this library. For the master cmake
project I need to read this information at build time into a cmake variable to
set the include directories correctly.
Is there a
On 7/31/2013 7:59 PM, Michael R. Dilworth wrote:
Building a 64bit version of cmake, however a 32bit version worked before ~2.8.8
(sorry it's late...)
You should not need a 64bit cmake. The 32 bit version should build
64/32 bits. I am not sure what you are looking for?
-Bill
--
Powered
) are read-only. Is there any way to solve this?
Best,
--
Sybren A. St?vel
http://stuvel.eu/
-- next part --
An HTML attachment was scrubbed...
URL:
http://www.cmake.org/pipermail/cmake/attachments/20130801/8b79b095/attachment-0001.htm
On 7/31/2013 7:59 PM, Michael R. Dilworth wrote:
Building a 64bit version of cmake, however a 32bit version worked before
~2.8.8
(sorry it's late...)
You should not need a 64bit cmake. The 32 bit version should build
64/32 bits. I am not sure what you are looking for?
He’s
Patrick,
On 08/01/2013 01:41 PM, David Cole wrote:
He's probably just looking for the generator itself in the cmake
--help output. They are listed in the dropdown gui if you use cmake-gui...
The Win64 generators are not listed explicitly in the command line
--help output anymore, although
On 07/31/2013 03:08 PM, Orion Poplawski wrote:
Is there a way to pass arguments to ctest via the make check target?
Okay, here's what's up. This recipe:
http://www.cmake.org/Wiki/CMakeEmulateMakeCheck :
add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND})
is not terribly useful in
://stuvel.eu/
-- next part --
An HTML attachment was scrubbed...
URL:
http://www.cmake.org/pipermail/cmake/attachments/20130801/8b79b095/attachment-0001.htm
--
Message: 2
Date: Thu, 1 Aug 2013 14:07:31 +
From: Rothbauer, Stefan
On Thu, Aug 1, 2013 at 7:07 PM, Moreland, Kenneth kmo...@sandia.gov wrote:
The easiest solution is to simply copy UseLATEX.cmake to your project
and update it by hand when necessary, which is probably never. That's what
I do.
-Ken
Sent from my iPad so blame autocorrect.
I am using a
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 1cc328390a69d132ad5afd1e5fe809401d4a8743 (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 5e0be1d2be4172150daa9eecae900d9b0ce9c74b (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 cc49b6138acbab19d8a2ac08d3f4e54bf84d7d8f (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 c25e5d9602611e102b312090853d2b8dad1f4486 (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 94e1da30b6926e40c6f6ea8049b73a1464de06eb (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 cb20d01d636a0322b4ac09b894839c03c28b70ec (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 a26e7d0782dbe0cd2e7958419212e534439245c9 (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 75af0cbfe7c62cd73ae6eb25b06eb0f7d8566007 (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 1a88bbf3f06f0858cf6957d80623d43dcd323a22 (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 89085f34117364031de9d17e0b22f18563680d64 (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 b341bf2178e3923636735ae1df53a33e5857df7d (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 bd1c269eba532e0b5576daa8342326b5ea3f270d (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 de6899f241b4bd3030f8c60e81e3d1c073cffa5b (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 7ef7569806e6b0a81ed742c0123dff58954d77f6 (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 c690998f2233ad24d7ee3aa447bf6a46813494de (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 0d165d2..001ed8f 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 11)
-set(CMake_VERSION_TWEAK 20130801
30 matches
Mail list logo
