This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: library vis export library

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)
*Like your name except E should replace the middle C*
----- Original Message -----
From: "Lee, Robert C." <>
To: <>
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
> 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
> the difference?
> Thanks,
> Robert
> --
> Unsubscribe info:
> Problem reports:
> Documentation:
> FAQ:         

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]