[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-libunistring] mixing MSVC and mingw-built libunistring

From: Bruno Haible
Subject: Re: [bug-libunistring] mixing MSVC and mingw-built libunistring
Date: Sat, 30 May 2009 14:25:55 +0200
User-agent: KMail/1.9.9

David Byron wrote:
> > The documentation that Simon wrote in
> > gnulib/doc/ld-output-def.texi also mentions a recipe in
> > <http://support.microsoft.com/kb/131313/en-us>. It should
> > apply, because libunitring consists only of C API. Can you
> > try that?
> It works.    I tried this before I wrote but I must have only tried with the
> Debug configuration (-MDd), not Release (-MD).  Here's what I did.
> $ cd /usr/local/mingw/bin
> $ echo EXPORTS >libunistring-0.def
> $ dumpbin /EXPORTS libunistring-0.dll | tail -n+20 | awk '{ print $4 }'
> >>libunistring-0.def
> $ lib /def:libunistring-0.def
> which created libunistring-0.exp and libunistring-0.lib
> Then I add libunistring-0.lib to linker input and set the linker path to
> include (the windows version of) /usr/local/mingw/bin and I get no more
> linker warnings.
> The Debug configuration (using -MDd) crashes in free as before but the
> Release configuration (using -MD) works, at least with the few functions I'm
> calling so far.

Cool! Thanks for publishing your recipe. I'm updating the ld-output-def.texi
file to reflect this sequence of commands.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]