Works!! I got it linking correctly... I actually found the libtool template
code inside configure, so it was pretty simple to delete it from there and
now I got a proper configure patch which generates a patched libtool.

Although it links correctly now, I'm not getting any DLLs out of it... just
.la and .a and it should be dumping the DLLs as weel... could it be because
I took the objects out? or it is missing some command line that instructs it
to generate dlls?

I tried to build openexr (ilmbase is a dependency for openexr) with the .la
and .a libs, but openexr build complains about not finding references
again... I know from past experience with mingw that I was only able to
build openexr if I used the DLLs intead of the .la files, or else I would
get those same missing references... that's why I need to get the DLLs out
of ilmbase!

-H


On Mon, May 31, 2010 at 7:26 PM, JonY <[email protected]> wrote:

> On 6/1/2010 10:30, Hradec wrote:
>
>> yeah... I already find it... the problem is that libtool is being
>> generated
>> after the configure script, and my automatic build system runs before
>> configure, so I would have to patch configure in order to get it to output
>> libtool already patched... (kinda confusing)...
>>
>> That's why I was wondering if there was a way to get configure to get the
>> right parameters from outside instead of patching it...
>>
>> I'll try removing the objects manually and see if that fixes the link...
>> hopefully it will fix it all! :)
>>
>> thanks for the great help !!! really appreciate! :)
>>
>> -H
>>
>>
> Hi,
>
> instead of editing configure, edit libtool instead. It is generated at the
> directory you ran configure in.
>



-- 
Hradec
------------------------------------------------------------------------------

_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to