If a script recursively calls itself (ir indirectly causes a infinite recursion of includes) cmake silently exits, and does not tell why.
I finally managed to get cmake --trace-expand --debug-output .. to show some useful information. --debug-output with --build causes cmake to try to run in configure mode instead of building... ----- CMakeLists.txt --------- cmake_minimum_required(VERSION 3.6) include( brokenScript ) -------------------- ----- brokenScript --------- include( brokenScript ) ------------------- (Yes, this shouldn't be done in the first place; but I ended up generating a script over another script of the same name that was expecting originally to be built into a separate directory) having the above two files, and making a build directory and from the build directory doing 'cmake ..' does compiler detection then exits with an error code. Cmake-gui (on windows) trying to do a generate crashes with an exception.
-- 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
