|
Notes |
|
|
(0008567)
|
|
Alex Neundorf
|
|
2007-08-21 16:27
|
|
|
|
|
(0009600)
|
|
Alex Neundorf
|
|
2007-11-01 06:07
|
|
Allen, what's the use case ?
Alex |
|
|
|
(0009601)
|
|
Josef Karthauser
|
|
2007-11-01 07:26
|
|
It is sometimes necessary for cmake to test things and terminate if the conditions aren't met.
For instance, when adding files to a project, it is possible to write macros so that a file is automatically created from a template file during the cmake process. It may be an error if the template for a given file type isn't found, which would warrant a termination with an error message. I've found that raising a MESSAGE(FATAL_ERROR "some error message") doesn't always terminate, from deep within a macro. |
|
|
|
(0010092)
|
|
Alex Neundorf
|
|
2008-01-07 17:30
|
|
Some ideas:
how about BREAK ?
in a loop: terminate loop
in a macro/function: "return" from that macro/function
on file level: stop processing this file
Alex |
|
|
|
(0010237)
|
|
Ken Martin
|
|
2008-01-23 12:34
|
|
return and break both implemented. return effectively stops processing of the CMakeLists file at that point. So...
message ("unable to find foo")
return()
should help address this issue |
|