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:
