Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-15 Thread Michael Hertling
On 11/14/2011 09:15 PM, Robert Dailey wrote: On Mon, Nov 14, 2011 at 1:59 PM, Michael Hertling mhertl...@online.dewrote: On 11/14/2011 06:17 PM, Robert Dailey wrote: Well maybe you can tell me I'm doing this wrong then, but based on how I am currently setting up my third party libraries, it

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-15 Thread Robert Dailey
On Tue, Nov 15, 2011 at 4:49 AM, Michael Hertling mhertl...@online.dewrote: As David has outlined in the meantime, the advice is not about using FIND_LIBRARY() - which has not been mentioned a single time - but to assemble full paths from the libraries' directories and the libraries

[CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Arunmozhi
Hi, For a static library target, I used TARGET_LINK_LIBRARIES and LINK_DIRECTORIES to link with a third party library. As we can see that in cmake, this linking information is propagated and used only in an executable/shared library target which depends on the former static library. But the

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Michael Wild
On 11/14/2011 11:46 AM, Arunmozhi wrote: Hi, For a static library target, I used TARGET_LINK_LIBRARIES and LINK_DIRECTORIES to link with a third party library. As we can see that in cmake, this linking information is propagated and used only in an executable/shared library target which

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Robert Dailey
On Mon, Nov 14, 2011 at 6:42 AM, Michael Wild them...@gmail.com wrote: Hi Arun Consider LINK_DIRECTORIES to be obsolete and to be avoided at all cost. I don't really agree with this advice. There are circumstances where link_directories() is absolutely necessary, so advocating to completely

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Michael Wild
On 11/14/2011 03:36 PM, Robert Dailey wrote: On Mon, Nov 14, 2011 at 6:42 AM, Michael Wild them...@gmail.com mailto:them...@gmail.com wrote: Hi Arun Consider LINK_DIRECTORIES to be obsolete and to be avoided at all cost. I don't really agree with this advice. There are

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread David Cole
On Mon, Nov 14, 2011 at 9:36 AM, Robert Dailey rcdai...@gmail.com wrote: On Mon, Nov 14, 2011 at 6:42 AM, Michael Wild them...@gmail.com wrote: Hi Arun Consider LINK_DIRECTORIES to be obsolete and to be avoided at all cost. I don't really agree with this advice. There are circumstances where

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Robert Dailey
On Mon, Nov 14, 2011 at 11:00 AM, David Cole david.c...@kitware.com wrote: On Mon, Nov 14, 2011 at 9:36 AM, Robert Dailey rcdai...@gmail.com wrote: On Mon, Nov 14, 2011 at 6:42 AM, Michael Wild them...@gmail.com wrote: Hi Arun Consider LINK_DIRECTORIES to be obsolete and to be avoided at

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Mateusz Łoskot
On 14 November 2011 17:17, Robert Dailey rcdai...@gmail.com wrote: So basically all third party libraries we use are not installed individually, instead we have a server on our intranet that contains precompiled versions of all libraries in a specific and consistent hierarchy. For this reason,

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Michael Hertling
On 11/14/2011 06:17 PM, Robert Dailey wrote: On Mon, Nov 14, 2011 at 11:00 AM, David Cole david.c...@kitware.com wrote: On Mon, Nov 14, 2011 at 9:36 AM, Robert Dailey rcdai...@gmail.com wrote: On Mon, Nov 14, 2011 at 6:42 AM, Michael Wild them...@gmail.com wrote: Hi Arun Consider

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Robert Dailey
On Mon, Nov 14, 2011 at 1:59 PM, Michael Hertling mhertl...@online.dewrote: On 11/14/2011 06:17 PM, Robert Dailey wrote: Well maybe you can tell me I'm doing this wrong then, but based on how I am currently setting up my third party libraries, it is required. So basically all third

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Alexander Neundorf
On Monday 14 November 2011, Robert Dailey wrote: On Mon, Nov 14, 2011 at 1:59 PM, Michael Hertling mhertl...@online.dewrote: On 11/14/2011 06:17 PM, Robert Dailey wrote: Well maybe you can tell me I'm doing this wrong then, but based on how I am currently setting up my third

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread David Cole
If you already know where all the libraries are, please just use the full paths to those libraries, and do not use find_library. On Mon, Nov 14, 2011 at 3:15 PM, Robert Dailey rcdai...@gmail.com wrote: On Mon, Nov 14, 2011 at 1:59 PM, Michael Hertling mhertl...@online.de wrote: On 11/14/2011

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Clinton Stimpson
That's what I do sometimes. To make that easier, CMake gives some convenience variables for library prefixes and suffixes if you are on multiple platforms. Clint On Monday, November 14, 2011 01:20:29 pm David Cole wrote: If you already know where all the libraries are, please just use the

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Robert Dailey
What is the difference between CMAKE_LINK_LIBRARY_SUFFIX and CMAKE_IMPORT_LIBRARY_SUFFIX? Which should I use? - Robert Dailey On Mon, Nov 14, 2011 at 2:49 PM, Clinton Stimpson clin...@elemtech.comwrote: That's what I do sometimes. To make that easier, CMake gives some convenience

Re: [CMake] Problem with LINK_DIRECTORIES

2011-11-14 Thread Clinton Stimpson
From the Modules/Platform/* files, it looks like the only difference between the two is when using CYGWIN or MinGW. I'm not sure which to use. Clint On Monday, November 14, 2011 01:51:49 pm Robert Dailey wrote: What is the difference between CMAKE_LINK_LIBRARY_SUFFIX and