On 11/3/2010 12:23 PM, Matěj Týč wrote:
> On 2 November 2010 13:26, Charles Wilson wrote:
>> On 11/2/2010 2:14 AM, Ralf Wildenhues wrote:
>> ...
>> the problem is there are TWO different libuuid's. There's the one that
>> is part of the win32 api, and simply contains a number of static objects
>>
On 2 November 2010 13:26, Charles Wilson wrote:
> On 11/2/2010 2:14 AM, Ralf Wildenhues wrote:
>> ...
>
> the problem is there are TWO different libuuid's. There's the one that
> is part of the win32 api, and simply contains a number of static objects
> that represent UUIDs of elements of the Win
On 11/2/2010 2:14 AM, Ralf Wildenhues wrote:
> OTOH, if the w32 maintainers agree, then we can also give in and allow
> linking against static libraries plainly. I tried the trivial patch
> (set deplibs_check_method to pass_all) a while ago but that caused a
> number of test failures, so somebody
Hello Matěj,
* Matěj Týč wrote on Wed, Oct 27, 2010 at 10:44:25PM CEST:
> I have came across a libtool issue that complicates my life quite much.
> The essence of the problem is that libtool refuses to make a DLL if it
> is supposed to link a static library into the DLL. I have learned that
> this
Hello,
I have came across a libtool issue that complicates my life quite much.
The essence of the problem is that libtool refuses to make a DLL if it
is supposed to link a static library into the DLL. I have learned that
this is a good assumption since the majority static libs don't contain
PIC cod