[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: |
David Byron |
Subject: |
RE: [bug-libunistring] mixing MSVC and mingw-built libunistring |
Date: |
Sun, 31 May 2009 08:01:22 -0700 |
Not using "normal" quoting since the line wrapping, etc. makes it hard to
read.
My recipe for creating an import library from libunistring-0.dll:
$ 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
Then Bruno wrote:
> Cool! Thanks for publishing your recipe. I'm updating the
> ld-output-def.texi file to reflect this sequence of
> commands.
Notice the "tail -n+20" part of the dumpbin command line above. There's no
doubt a more robust way to do this. The idea is to grab everything after:
ordinal hint RVA name
and the blank link that follows it. My sed skills aren't sharp enough to
pull this off without doing some reading so I just used tail. If the output
of dumpbin changes slightly this recipe could break.
In case it's helpful, here are the tool versions I used:
dumpbin:
Microsoft (R) COFF/PE Dumper Version 8.00.50727.762
lib:
Microsoft (R) Library Manager Version 8.00.50727.762
Still curious about ideas for approaches to get libunistring working with
-MDd.
-DB