Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <3CC9C83E.1030401@ece.gatech.edu>
Date: Fri, 26 Apr 2002 17:35:58 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
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
Subject: Re: ordinal linking for cygwin ld
References: <00db01c1eb76$239e4dd0$651c440a AT BRAMSCHE> <3CC9C213 DOT 5060002 AT ece DOT gatech DOT edu> <3CC9C689 DOT 9020108 AT sun DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



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