Re: [Mingw-users] --out-implib bug

[Luke D. <cod...@ho...>]

----- Original Message ----- 
From: "Rodrigo Hernandez" <rod...@y2...>
To: <min...@li...>
Sent: Wednesday, August 06, 2003 10:06 AM
Subject: [Mingw-users] --out-implib bug


>
> Hello,
>
> well, after spending half a day wrestling with the outdated freetype2
> code to generate a dll (shared lib) I succeded, and found a bug on the
> -shared -Wl,--out-implib,libfilename.a implementation, not sure what it
> is exactly, but when given a FULL path here, GCC fails to create the
> file, in effect:
>
> .../c/code/ft214/freetype-2.1.4/objs/.libs/winfnt.o  -lz  -o
> /c/code/ft214/freetype-2.1.4/objs/.libs/libfreetype-6.dll
> -Wl,--image-base=0x10000000
> -Wl,--out-implib,/c/code/ft214/freetype-2.1.4/objs/.libs/libfreetype.dll.a
> Can't open .lib file:
> /c/code/ft214/freetype-2.1.4/objs/.libs/libfreetype.dll.a
> make: *** [/c/code/ft214/freetype-2.1.4/objs/libfreetype.la] Error 1
>
> somehow if the --out-implib part is feed like a relative path:
> --out-implib,objs/.libs/libfreetype.dll.a
>
> it will work, first I thought it had to do with libtool, but I
> copy-pasted the GCC command and it yield the same error, also of course,
> setting no path so it will use the current instead gives no errors.
>
> anyway, thats it, sorry if this was already reported

This is an MSYS issue, and it should work if you use "c:" instead of "/c" at
the start of the path (keep using forward slashes though). I realise that
this may be difficult to change in a makefile generated by a configure
script or libtool.

Luke