On 05/28/2014 05:19 PM, J Decker wrote: >> CMake would much rather use full paths rather than -L/-l because of >> ambiguity problems. > > I can get around abguity by ordering the order of -L entries..
CMake versions prior to 2.6 always did that. We had no end of trouble with the wrong library files getting found by the linker. There are often problems with cycles in the ordering dependency graph. There is also the problem of ensuring a static library is found when desired. CMake has code to add -Bstatic -lfoo -Bdynamic sequences, but that approach has its own problems you can find in the list archives. Linking by library file path eliminates all these problems. -Brad -- 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
