> CMake would much rather use full paths rather than -L/-l because of > ambiguity problems. > > > While I can see that; I can get around abguity by ordering the order of -L entries... like if one was buliding an upgrade to an already installed library, one would want the current version to link against what's being built not what's installed
It would appear that LD has no internal default paths so they're all specified on the command line or in linker scripts http://stackoverflow.com/questions/9922949/how-to-print-the-ldlinker-search-path So I personally didn't understand why it was specifying full path to .so's anyway. I think maybe there was one-off systems that were considered 'standard' when developing these things....(should have been the exception not the rule) And maybe I'm way off base
-- 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/cgi-bin/mailman/listinfo/cmake-developers
