From: Max B. <ma...@uk...> - 2002-09-16 21:48:19
|
Guido Draheim wrote: > hmm, perhaps, the LD can now link with dlls directly, and that should > be checked throughoughly. That was achieved by pushing code from the > dlltool into the LD, what I now wonder if it wouldn't be right to put > the other part of dlltool into objdump. The LD is used to create a > dll, and objdump is used to examine a dll, that's the scheme. > > As noted by Rob Collins, the objdump does already exhibit the symbol > tables and he did guess that there is also the export table which is > fetched with the impgen.c extra code in libtool - but in a format > unusable by other compile steps. > > Now, we have dlltool-z to take a .dll and create a .def file. Can we > have a w32-specific objdump call to not only print the export-table, > but have in a def-style format? That we can then use for other > compile steps? Why not just make sure libfoo.dll.a is always available ??? See how Cygwin does it in libtool.m4. Libtool is told that libfoo.dll.a is the library, and postinstall commands put libfoo.dll into ../bin. Max. |