On 04/12/13 14:28, Brad King wrote:
I think the option should be called EXCLUDE_FROM_MAIN or something
without ALL in it. Otherwise it looks related to the EXCLUDE_FROM_ALL
settings used for the make all CMake builtin target.
Ok, changed to EXCLUDE_FROM_MAIN.
Cheers,
Daniele
--
Powered
On 12/04/2013 08:20 AM, Brad King wrote:
On 12/04/2013 04:57 AM, Daniele E. Domenichelli wrote:
+1, since this is a very useful feature.
Actually after thinking about this over night I realized that converting
to a C++ implementation is the best way to fix the empty argument handling
too.
On 12/04/2013 10:41 AM, Brad King wrote:
On 12/04/2013 07:22 AM, Daniele E. Domenichelli wrote:
Done and merged to next again.
Now the ExternalProject tests fail on the continuous builds.
Please take a look.
Thanks for the fixes this morning. However, I do not like having
to update all the
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14632
==
Reported By:ivchups
Assigned To:
On 2013-12-05 02:36, Alan W. Irwin wrote:
Sorry, this turned out to be a false alarm. Despite which cmake
telling me I was using cmake-2.8.12.1 [snip]
...which is, of course, why you should always use type in bash rather
than which :-). type, being a shell built-in, will tell you what
bash
On 2013-12-05 12:27-0500 Matthew Woehlke wrote:
On 2013-12-05 02:36, Alan W. Irwin wrote:
Sorry, this turned out to be a false alarm. Despite which cmake
telling me I was using cmake-2.8.12.1 [snip]
...which is, of course, why you should always use type in bash rather than
which :-). type,
If you design a simple test case such as
project(test_loop_fatal_errors NONE)
cmake_minimum_required(VERSION 2.8.12.1 FATAL_ERROR)
while(1)
message(FATAL_ERROR Should stop loop?)
message(STATUS Did I make it by FATAL_ERROR?)
endwhile(1)
The result is the expected one; the loop stops
06.12.2013 1:19 пользователь Rolf Eike Beer e...@sf-mail.de написал:
Hi,
I noticed that the message backtrace facility detected in default set of
libraries appears every time CMake is run, and not just when the library
is
searched for, which is not what the modules usually do. Can this be
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14633
==
Reported By:Sean Patrick Santos
Assigned To:
Hi Eric-
Thanks for the response! See inline-
On 12/4/2013 11:17 PM, Eric Noulard wrote:
2013/12/5 David Erickson daviderick...@cs.stanford.edu:
Hi All-
We would like to use cmake for our build infrastructure, and Eclipse for
code editing/debugging. I found and read
Hi all,
I was trying to figure out whether the source file property
COMPILE_DEFINITIONS supports generator expressions and I found no clear way
how to do so (so I assume it does not, because genexes aren't mentioned in
its docs).
This got me thinking: is there a list somewhere of all contexts
I used to use Eclipse for coding with CMake and the what worked the best for me
was the following (This assumes you are on Unix/Linux/OSX).
Start in Project A. Create a directory Build. Have CMake generate
Makefiles using Build as the build directory.
Start up Eclipse. Create a new Existing
2013/12/5 David Erickson daviderick...@cs.stanford.edu:
Hi Eric-
Thanks for the response! See inline-
On 12/4/2013 11:17 PM, Eric Noulard wrote:
2013/12/5 David Erickson daviderick...@cs.stanford.edu:
Hi All-
We would like to use cmake for our build infrastructure, and Eclipse for
code
I found this 2009 thread:
http://marc.info/?l=cmakem=123851619629929w=2
discussing this issue and I tried all suggestions but still cannot get
C files compiled with C++.
The last suggestion was to glob all C source files and set a LANGUAGE
CXX property on each. I put this at the very top of
Should have been posted here
-- Forwarded message --
From: Tom Browder tom.brow...@gmail.com
Date: Thu, Dec 5, 2013 at 12:31 PM
Subject: Re: [CMake] Compile C files with C++
To: J Decker d3c...@gmail.com
On Thu, Dec 5, 2013 at 12:21 PM, J Decker d3c...@gmail.com wrote:
I mean
On Thu, Dec 5, 2013 at 12:38 PM, J Decker d3c...@gmail.com wrote:
then maybe just stripping the names, and/or adding the
CMAKE_CURRENT_SOURCE_DIR for each one as appropriate
No, I still need choice, so, e.g., I'm using these lines in each
CMakeLists.txt (modified as necessary, of course; and it
Hello,
If you have more than 200 CMakeLists.txt, IMHO you should create two macros
to wrap add_executable/add_library: add_executable_maybe_cxx /
add_library_maybe_cxx
On Thu, Dec 5, 2013 at 7:54 PM, Tom Browder tom.brow...@gmail.com wrote:
On Thu, Dec 5, 2013 at 12:38 PM, J Decker
On Thu, Dec 5, 2013 at 1:44 PM, Pau Garcia i Quiles
pgqui...@elpauer.org wrote:
Hello,
If you have more than 200 CMakeLists.txt, IMHO you should create two macros
to wrap add_executable/add_library: add_executable_maybe_cxx /
add_library_maybe_cxx
Good idea, but the changes needed I think
I'm sure this has come up before but I'm curious if CMake-GUI would ever
consider adding a Build button? This seems like a logical step after
Configure and Generate, if it was available on the command line it could
also help automate CMake based builds on different systems. Right now scripts
Hi Jon,
You'd have to invoke the command prompt to execute this I think. On
Windows this should be the value of the COMSPEC environment
variable, so your command would be something like:
execute_process(COMMAND
$ENV{COMSPEC} /c date /t
OUTPUT_VARIABLE
2013/12/5 Macumber, Daniel daniel.macum...@nrel.gov:
I’m sure this has come up before but I’m curious if CMake-GUI would ever
consider adding a “Build” button? This seems like a logical step after
“Configure” and “Generate”, if it was available on the command line it could
also help automate
On 2013-12-05 15:46, Fraser Hutchison wrote:
If you can specify CMake version 2.8.11 as a minimum, you could use
the string(TIMESTAMP ...) command instead:
string(TIMESTAMP _output %d/%m/%Y)
Bear in mind that these only execute when CMake runs (i.e. at configure time)
rather than at build
I've run into a problem after updating my cmake in using the FindQt4 module.
It used to be the case that when QT_QMAKE_EXECUTABLE was changed by the
user or by a SET(... FORCE) command, all the derived cache entries would be
refreshed, however this does not work anymore.
The cause seems to be
Hi
I am trying to write a toolchain cmake script in order to crosscompile a
cpp program for Tizen emulator. Here is the cmake script I am using:
SET(CMAKE_SYSTEM_NAME Linux)
SET(CMAKE_SYSTEM_VERSION 1)
SET(CMAKE_C_COMPILER
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 0a956ea9e6bd8b8d381f097b82ced12b60cef906 (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 9245b5e072560f07e1b11c2341caeee386812086 (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 c974f9c252be30b61659a2dbd9b96bff80016a9e (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 998d7c8f4af27346aab11dfc89a9432d277de676 (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 520ead7200334fddcbef94c657de025abe5cf134 (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 e1af1d359297aab9f1fccd93ac7e5d6eeffc5083 (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 b5d5a543490faf62bf52bbad53cba3c8b33f051c (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 73f8e7f06aeac0740769d7350bf23b9b418258a0 (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 5c87f57191ec5d137e9d51df10c0a2f8d85f1249 (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 148a506e334ae247726b7d45afaa1da8a547c67b (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 38dc376b5ae0f550979912398782cd0e75ff976e (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 b5f27dd140db8600c32ecd266ab902a307144f2e (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 9dfac4695e4d83b19af0169e775b8b401adc0503 (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index d507535..4b8a9ec 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 20131205
38 matches
Mail list logo
