Here is one more extremely simple idea for solving this bug.
Assuming all of CMake always errors out using the same piece of error-processing code, couldn't enable_language(OPTIONAL) immediately set an internal variable which is honored by that error-processing code to turn all further errors into warnings? Then the last thing enable_language(OPTIONAL) should do is unset that variable (so all further errors are treated as errors) before returning control to the logic that called enable_language(OPTIONAL). Of course, this idea depends on the assumption that all CMake errors are handled by the same piece of error-processing code, but if that is true this fix should be extremely easy to implement. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
