I thought I had turned the final corner and only had the “home stretch” left to get to the finish line… and then a brick wall suddenly appeared to block my way…
So the configuration/bootstrap script seems to blissfully get all the way to the end and even displays the following: --------------------------------------------- CMake has bootstrapped. Now run make. Except when I looked… it had not created the Makefile. I ran the same basic process on one of my Linux systems and noticed that in addition to NOT creating the Makefile… it also did not create the bin subdirectory. I tried simply adding the –trace option on the bootstrap’s cmake command (the last thing it does before posting the text above), but that didn’t seem to reveal any clues. I would love to simply comment out large swaths of the 3000+ lines of cmake-3.3.2\Tests\CMakeLists.txt but at this point I don’t have sufficient understanding of what impact doing this would have and fear that without the understanding doing so would probably do little to help me isolate where things appear to have gone awry. Does anyone know where (specifically) I should investigate to determine where the Makefile itself should get generated? What about what triggers the creation of the bin folder? Jay
-- 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
