Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3CC9DBBB.7070209@ece.gatech.edu> Date: Fri, 26 Apr 2002 18:59:07 -0400 From: Charles Wilson 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: Ralf Habacker CC: Kde-Cygwin , Binutils , Cygwin-Apps Subject: Re: ordinal linking for cygwin ld References: <006101c1ed71$27f639e0$625d07d5 AT BRAMSCHE> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Ralf Habacker wrote: > Ralf Habacker wrote: > >>I'm thinking about creating to areas, an internal and an external. >>New releases of kdelibs and perhaps kdebase for example are build together. So >>ordinal linking is not problem. -> internal area. Any other app may >>be linked by name -> external area. >> >> > That would cause the second solution I have told, normal import library and > using a special linker switch for using ordinal linking. Yeah, I think I like this -- but it should be used carefully in foundation libraries like KDE (and Gnome), and only where you're guaranteed that the ordinal-linked apps/dlls will always be upgraded together. The potential for muck-up is high... --Chuck