On Sun, Jan 3, 2010 at 2:26 PM, Alexander Neundorf
wrote:
> Isn't there some "binutil" which can tell what kind of library some .lib is ?
> Or maybe every dll (and that way the accompanying lib) has some functions
> which only dlls have ?
> Or maybe they references some special functions which may
On Monday 28 December 2009, Bill Hoffman wrote:
> Pau Garcia i Quiles wrote:
> > I'm using CMake 2.8.0 on Linux. Yes, Michael is right: I want it to
> > happen automagically. That was the whole point of this thread :-)
>
> OK, well the thread has a very bad subject then
>
> It should be "force
On 30. Dec, 2009, at 18:02 , Jed Brown wrote:
> On Wed, 30 Dec 2009 17:51:29 +0100, Michael Wild wrote:
>>
>> On 30. Dec, 2009, at 17:32 , Jed Brown wrote:
>>
>>> On Mon, 28 Dec 2009 12:29:05 +0100, Pau Garcia i Quiles
>>> wrote:
I'm using CMake 2.8.0 on Linux. Yes, Michael is right: I
On Wed, 30 Dec 2009 17:51:29 +0100, Michael Wild wrote:
>
> On 30. Dec, 2009, at 17:32 , Jed Brown wrote:
>
> > On Mon, 28 Dec 2009 12:29:05 +0100, Pau Garcia i Quiles
> > wrote:
> >> I'm using CMake 2.8.0 on Linux. Yes, Michael is right: I want it to
> >> happen automagically. That was the wh
On 30. Dec, 2009, at 17:32 , Jed Brown wrote:
> On Mon, 28 Dec 2009 12:29:05 +0100, Pau Garcia i Quiles
> wrote:
>> I'm using CMake 2.8.0 on Linux. Yes, Michael is right: I want it to
>> happen automagically. That was the whole point of this thread :-)
>
> I would argue that FindXXX.cmake is t
On Mon, 28 Dec 2009 12:29:05 +0100, Pau Garcia i Quiles
wrote:
> I'm using CMake 2.8.0 on Linux. Yes, Michael is right: I want it to
> happen automagically. That was the whole point of this thread :-)
I would argue that FindXXX.cmake is the wrong place for the decision to
be made since I may wan
Pau Garcia i Quiles wrote:
I'm using CMake 2.8.0 on Linux. Yes, Michael is right: I want it to
happen automagically. That was the whole point of this thread :-)
OK, well the thread has a very bad subject then
It should be "force find_library to choose static over shared". This
really ha
On 28. Dec, 2009, at 12:40 , Pau Garcia i Quiles wrote:
>> That sounds doable to me. However, you'd need a mechanism to express the
>> same preference when calling find_package and then have find_package
>> communicate that to find_library. Not sure how fine-grained
>> the control should be for
> That sounds doable to me. However, you'd need a mechanism to express the same
> preference when calling find_package and then have find_package communicate
> that to find_library. Not sure how fine-grained
> the control should be for FindXXX.cmake modules that find more than one
> library (or
>> What version of CMake are you using? This should work... As of 2.6.2 (I
>> think...) CMake uses full paths to libraries, see policy CMP0003:
>> http://www.cmake.org/cmake/help/cmake-2-8-docs.html#policy:CMP0003. It does
>> not matter if there are two libraries in the same directory. There
On 27. Dec, 2009, at 23:30 , Pau Garcia i Quiles wrote:
> On Sun, Dec 27, 2009 at 10:16 PM, Michael Wild wrote:
>>
>> On 27. Dec, 2009, at 20:41 , Pau Garcia i Quiles wrote:
>>
>>> On Sun, Dec 27, 2009 at 10:59 AM, Michael Wild wrote:
On 26. Dec, 2009, at 17:53 , Pau Garcia i Quile
On 28. Dec, 2009, at 5:38 , Bill Hoffman wrote:
> Pau Garcia i Quiles wrote:
>> On Sun, Dec 27, 2009 at 6:26 PM, Bill Hoffman
>> wrote:
>>> Pau Garcia i Quiles wrote:
Hello,
I think this has already been discussed and the answer is negative but
still: when I do target_link_
Pau Garcia i Quiles wrote:
On Sun, Dec 27, 2009 at 6:26 PM, Bill Hoffman wrote:
Pau Garcia i Quiles wrote:
Hello,
I think this has already been discussed and the answer is negative but
still: when I do target_link_libraries to an external library (for
instance, my application needs to link to
On Sun, Dec 27, 2009 at 10:16 PM, Michael Wild wrote:
>
> On 27. Dec, 2009, at 20:41 , Pau Garcia i Quiles wrote:
>
>> On Sun, Dec 27, 2009 at 10:59 AM, Michael Wild wrote:
>>>
>>> On 26. Dec, 2009, at 17:53 , Pau Garcia i Quiles wrote:
>>>
Hello,
I think this has already been disc
On 27. Dec, 2009, at 20:41 , Pau Garcia i Quiles wrote:
> On Sun, Dec 27, 2009 at 10:59 AM, Michael Wild wrote:
>>
>> On 26. Dec, 2009, at 17:53 , Pau Garcia i Quiles wrote:
>>
>>> Hello,
>>>
>>> I think this has already been discussed and the answer is negative but
>>> still: when I do targe
On Sun, Dec 27, 2009 at 6:26 PM, Bill Hoffman wrote:
> Pau Garcia i Quiles wrote:
>>
>> Hello,
>>
>> I think this has already been discussed and the answer is negative but
>> still: when I do target_link_libraries to an external library (for
>> instance, my application needs to link to sqlite), is
On Sun, Dec 27, 2009 at 10:59 AM, Michael Wild wrote:
>
> On 26. Dec, 2009, at 17:53 , Pau Garcia i Quiles wrote:
>
>> Hello,
>>
>> I think this has already been discussed and the answer is negative but
>> still: when I do target_link_libraries to an external library (for
>> instance, my applicati
Pau Garcia i Quiles wrote:
Hello,
I think this has already been discussed and the answer is negative but
still: when I do target_link_libraries to an external library (for
instance, my application needs to link to sqlite), is it possible to
tell CMake to link to the static version of sqlite inst
On 26. Dec, 2009, at 17:53 , Pau Garcia i Quiles wrote:
> Hello,
>
> I think this has already been discussed and the answer is negative but
> still: when I do target_link_libraries to an external library (for
> instance, my application needs to link to sqlite), is it possible to
> tell CMake to
Hello,
I think this has already been discussed and the answer is negative but
still: when I do target_link_libraries to an external library (for
instance, my application needs to link to sqlite), is it possible to
tell CMake to link to the static version of sqlite instead of the
dynamic version?
20 matches
Mail list logo
