Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: comlink.tivlab.raleigh.ibm.com: jerry owned process doing -bs Date: Tue, 18 Mar 2003 17:02:39 -0500 (EST) From: Jerry Heyman X-X-Sender: Reply-To: To: Subject: Re: idea for mixed import/static libraries and linking with DLLs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 18 Mar 2003 11:17:49 -0500, Joe Buehler wrote: > > Christoper Faylor wrote: > > > Apologies if this approach has already been mentioned. I thought > > it was kinda neat. > > AIX has something interesting. All libraries are ar libs. You can > have shared objects in them or plain .o files, or a mixture of both. > The same librry can be used for dynamic or static builds. I've always found the fact that a .a was both shared and static a problem. You loose any knowledge knowing what libraries HAVE to be installed on the machine in order to make the application execute :-( > Further, since all code is position-independent, you can easily > make a shared library from any .o file. True. but its not that simple. You have to create an exports file that lists all the symbols in the shared portion of the library, and combine all the .o files you want to be shared into a single shr.o file. Granted there are advantages to treating all libraries the same, but there are inherent limitations and added complexities here also. jerry Jerry Heyman 919.224.1442 | IBM SWG/Tivoli Software |"Software is the Build Infrastructure Architect| 3901 S Miami Blvd | difference between jheyman AT dev DOT tivoli DOT com | RTP, NC 27709 | hardware and reality" http://www.acm.org/~heymanj -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/