I have a completely insulated boostrapped toolchain+binaries setup (located under /home/tools), following much of the Linux From Scratch book, that has been able to build everything that I throw at it. Most things just work with a simple --prefix option, as I have also edited the GCC specs file to include my /home/tools/include directory (using -isystem) and link against my /home/tools/lib directory (also with an rpath set, so that all binaries I build are complete insulated from the host libraries). The lone exception to this is Cmake. It appears to have a lot of hardcoded paths in its build environment to standard /usr/* directories.
I first got wind that something was awry when Cmake 3.10.2 claimed my compiler, GCC 7.3.0, isn't C++11 compliant. Clearly this isn't the case, given that it's the latest release. So I then tried building Cmake 3.9.6, which doesn't require C++11, and it was finding zlib and other libraries under /usr/lib as opposed to my /home/tools/lib. I don't even have LD_LIBRARY_PATH set, as I use rpath in the specs file like I mentioned. Can anyone provide any help into how I can get Cmake to build against non-standard include and library locations? Thank you, Ben
-- 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: https://cmake.org/mailman/listinfo/cmake