This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
RE: ordinal linking for cygwin ld
- From: "Ralf Habacker" <Ralf dot Habacker at freenet dot de>
- To: "Charles Wilson" <cwilson at ece dot gatech dot edu>
- Cc: "Kde-Cygwin" <kde-cygwin at kde dot org>,"Binutils" <binutils at sources dot redhat dot com>,"Cygwin-Apps" <cygwin-apps at cygwin dot com>
- Date: Sat, 27 Apr 2002 02:11:30 +0200
- Subject: RE: ordinal linking for cygwin ld
> > If you use a .def file to generate your DLL, will the auto-import stuff
> > get added to it? Can auto-import even work, if you're linking by
> > ordinal -- I thought the _nm_ hints were based on the symbol name,
>
> no, the symbol name was build from the undef section, if a corresponding
> _imp_symbol was found, that means from the client side. There was no access
> (except of the dll name) to the implibs data.
>
Of course are the sections of the implib imported in the resulting binary,
but currently I have an idea, how to save additional space in the implib.
(for example the qt2.3.1 implib is about 8MB and contains 12079 symbols)
At least each symbol name exist twice. Perhaps this can be put together
d012073.o:
00000000 i .idata$4
00000000 i .idata$5
00000000 i .idata$6
00000000 i .idata$7
00000000 t .text
U __head_qt_2_3_dll
(a) 00000000 I __imp__y__C13QIconViewItem
(b) 00000000 T _y__C13QIconViewItem
->(a) __imp__y__C13QIconViewItem
^
(b) points to (a) + offset
If this is possible there is no space need to build a import
lib without names, because it will be a little about the half of the current
size. I will see.
Regards
Ralf