On Mon, Jan 16, 2012 at 10:21 AM, John Drescher <dresche...@gmail.com> wrote: > On Mon, Jan 16, 2012 at 1:15 PM, J Decker <d3c...@gmail.com> wrote: >> On Mon, Jan 16, 2012 at 10:08 AM, Rolf Eike Beer <e...@sf-mail.de> wrote: >>> J Decker wrote: >>>> I just use >>>> include_directories( ... ) >>> >>> This is right. >>> >>>> LINK_DIRECTORIES( ...} ) >>> >>> This is almost surely wrong. LINK_DIRECTORIES is only needed for very seldom >>> special cases and only causes headache in all other cases. >> >> oh, what's the preferred method to specify the directory where the >> library is then? >> > > I believe the full path on the target_link_libraries.
I think the problem with that is if built with gcc, then the full path to the library is encoded and you can't load the library from the library path, but only from where it was specified. > > John -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
