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 Date: Fri, 27 Aug 2004 14:29:27 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com cc: Oliver Subject: Re: questions about DLL's: .a, .def, and .dll In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Fri, 27 Aug 2004, Igor Pechtchanski wrote: > On Fri, 27 Aug 2004, Oliver wrote: > > > Hi folks, I'm confused about the files that dllwrap > > creates. On Unix (where I've been programming forever) all you > > have to do is create a .so shared library. But dllwrap ends up > > creating a .a file, a .def file, and a .dll file, yet I can > > build a program that links to, e.g., mylib.dll, with only "-L. -lmylib", > > *wihtout* having the .def or .a available. So where and when are the .a and > > .def files needed? > > The newer versions of gcc apparently allow you to link directly to a .dll ^/binutils > file. The .def and .a are needed for older versions of gcc, and possibly ^/binutils > for some other tools. > [snip] > Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing." -- Dr. Jubal Harshaw -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/