[cmake-developers] Fwd: Exiting CMake (should message(send_error ) show a call stack)
William A. Hoffman
billlist at nycap.rr.com
Mon Aug 14 11:44:37 EDT 2006
Here is a message from one of the kde lists:
>Howdy CMake Gurus,
>
>Is there a little more graceful way of exiting other than message(FATAL_ERROR "message") ??
>
>For example, in the MACRO_DISPLAY_FEATURE_LOG() macro I want to exit if there
>are missing required features. I want to display the messages that some requirements
>are missing and then exit.
>
>But I don't want to panic the user with messages like:
>
> CMake Error: Error in cmake code at
> /data/kde/trunk/KDE/kdepimlibs/CMakeLists.txt:1:
> MESSAGE some message
> Current CMake stack: /data/kde/trunk/KDE/kdepimlibs/CMakeLists.txt
>
>I don't see a simple Quit() or Exit() type of cmake commands.
>
>Regards,
>Allen
In the past MESSAGE(FATAL_ERROR "some message") only printed some message and
cmake stopped processing. At some point the call stack was added. Is this
really what should happen? Maybe we need a MESSAGE(ABORT that shows the call
stack and the FATAL_ERROR goes back to the way it was. This "feature" slipped
in between 2.4.2 and 2.4.3.
-Bill
More information about the cmake-developers
mailing list