Re: library vis export library

["Martin Gainty" <mgainty at hotmail dot com>]

When referencing a dll function you must know its full signature to property
reference it..thus the need for an export specification
when creating a Static Lib *.a you can statically link in the entire library
into the binary and not worry about linker hunting down an exported function
(since it is already bound to the binary)
Hth,
Martin
*Like your name except E should replace the middle C*
----- Original Message -----
From: "Lee, Robert C." <rc.lee@ngc.com>
To: <cygwin@cygwin.com>
Sent: Thursday, August 21, 2003 1:40 PM
Subject: library vis export library


> I apologize in advance if this is a stupid question. In the Cygwin User's
> Guide, it shows how to create a dll with gcc with the -shared switch in
much
> the way you create a shareable library, but it also shows how to create a
> export library with gcc. In one case you end up with a dll; in the other,
> you have a dll and a .a file. Why would I use one over the other? And
what's
> the difference?
>
> Thanks,
> Robert
>
> --
> 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/
>
>

--
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/