From fd7ada16cb7c2236aedeb829f59613b6168ded0d Mon Sep 17 00:00:00 2001 From: Charles Wilson Date: Fri, 28 May 2010 21:03:05 +0000 Subject: [PATCH] Added mingw32-pexports.xml --- mingw32/mingw32-pexports.xml | 45 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 mingw32/mingw32-pexports.xml diff --git a/mingw32/mingw32-pexports.xml b/mingw32/mingw32-pexports.xml new file mode 100644 index 0000000..d48cf55 --- /dev/null +++ b/mingw32/mingw32-pexports.xml @@ -0,0 +1,45 @@ + + + + + + + pexports can extract information from DLLs to create + corresponding .def files that list the symbols available in each + DLL. .def files can then be used by dlltool (mingw32-binutils) + to generate import libraries. pexports is similar to gendef, but + the two tools differ in how each determines the "decoration" (or + calling convention) appropriate for each symbol, since that + information is not always available directly from the DLL's + symbol table. pexports can use a C pre-processor to extract the + information, provided you have the appropriate header files. + gendef locates the symbol's code in the DLL, and uses a + disassembler to determine that information. Neither method is + foolproof, so both tools are provided. + + Note that in order for pexports to detect the calling + convention, you must specify on the command line the headers to + parse. If the symbols are not declared in those headers, then the + proper decorations cannot be computed. Originally written by + Anders Norlander, it now supports both 32bit and 64bit DLLs and + EXEs thanks to Tor Lillqvist. + + + + + + + + + + + + + + + + + + + + -- 2.11.0