From a498410792ec2937e0b93724bb255e745d224927 Mon Sep 17 00:00:00 2001 From: Bruno Haible Date: Sat, 30 May 2009 14:25:21 +0200 Subject: [PATCH] Explain how to use dumpbin. --- ChangeLog | 6 ++++++ doc/ld-output-def.texi | 12 ++++++++---- 2 files changed, 14 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index ef4441abc..e08b1e51c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2009-05-30 Bruno Haible + + * doc/ld-output-def.texi (Visual Studio Compatibility): Explain in more + detail how to use dumpbin. + Reported by David Byron . + 2009-06-02 Simon Josefsson * tests/test-parse-duration.sh: Don't use non-portable 'read -u3'. diff --git a/doc/ld-output-def.texi b/doc/ld-output-def.texi index 8f9203930..db48ee0d4 100644 --- a/doc/ld-output-def.texi +++ b/doc/ld-output-def.texi @@ -15,11 +15,15 @@ The variants we have considered include: @itemize @bullet @item Use DUMPBIN /EXPORTS. +This is explained in @url{http://support.microsoft.com/kb/131313/en-us}. The tool does not generate DEF files directly, so its output needs to -be post processed manually. The tool is documented to potentially not -work with non-MS development tools -(@url{http://support.microsoft.com/kb/131313/en-us}), which is the -case when MinGW is used to build the library. +be post processed manually: +@smallexample +$ { echo EXPORTS; \ + dumpbin /EXPORTS libfoo-0.dll | tail -n+20 | awk '{ print $4 }'; \ + } > libfoo-0.def +$ lib /def:libfoo-0.def +@end smallexample @item Use IMPDEF. There is a tool called IMPDEF -- 2.11.0