This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: ordinal linking for cygwin ld
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- To: Martin Hollmichel <martin dot hollmichel at sun dot com>
- Cc: kde-cygwin at mail dot kde dot org, binutils at sources dot redhat dot com, cygwin-apps at cygwin dot com
- Date: Fri, 26 Apr 2002 17:35:58 -0400
- Subject: Re: ordinal linking for cygwin ld
- References: <00db01c1eb76$239e4dd0$651c440a@BRAMSCHE> <3CC9C213.5060002@ece.gatech.edu> <3CC9C689.9020108@sun.com>
Martin Hollmichel wrote:
> Maybe you may look to openoffice.org how do the ensure that ordinals
> keep the same over some time. There's a tool named ldump (located in
> project tools, modules soltools) which keep's a database to keep the
> ordinals in track. Maybe this helps.
> at openoffice.org we're able to keep track of about 100 dll, maybe it's
> usable for 1000 also.
Well, if maintaining the .def files and ordinals is supported *from the
top* -- as seems to be the case in openoffice -- then it wouldn't be so
bad. I was trying to do it, for the cygwin project, "downstream" of the
actual maintainers of certain unnamed packages
(<cough>readline<cough>ncurses<cough>gettext).
However, gcc only supports a subset of the .def file language that MSVC
does, so one would either need to maintain two different .def files, or
munge the cygwin/mingw one from the msvc one at build time (assuming the
msvc .def file was maintained by the "real" KDE folks using some tool
like yours). OTOH, I've never heard of a mingw or MSVC port of kde, so
maybe KDE just needs cygwin .def files....
--Chuck