So then there would be no difference between SEND_ERROR and FATAL_ERROR?
What's the reasoning for this change?
I like the fact that SEND_ERROR allows you to signal an error, but to
complete the configure step to see if you hit any more errors... Then
you can fix them all at once and try again. If you do as you propose,
you'll have to fix things one at a time, leading to perhaps much longer
initial configure times (and number of iterations) for large projects.
I do agree that it's confusing that SEND_ERROR doesn't stop processing
the first time you encounter it as a cmake user. But like any other
quirk, you get used to it.
What would you think about having error "levels" or adding warnings and
warning levels, like compilers do?
David
Bill Hoffman wrote:
I want to change SEND_ERROR to do a FATAL_ERROR in the MESSAGE command.
This it to make the required modules stop processing the cmakelist files
at the first SEND_ERROR. Currently it works like this:
SEND_ERROR: prevents the generate step from happening, but cmake continues
to process files during the configure step.
FATAL_ERROR: cmake sends a message and immediately stops the configure step
and does not process any more files.
I want them both to stop cmake processing.
-Bill
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
