This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin now supports shared libraries?
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin-L <cygwin at cygwin dot com>
- Date: Mon, 18 Aug 2014 12:37:58 -0600
- Subject: Re: cygwin now supports shared libraries?
- Authentication-results: sourceware.org; auth=none
- References: <DUB129-W60CA1A2C80B8F61EDB78D7B0D60 at phx dot gbl>
On 8/16/2014 05:12, Gery . wrote:
so, Cygwin now supports shared libraries or always did?
Cygwin's binutils could link to DLLs (shared libraries) from the
beginning, if only because Windows' own APIs are all DLL-based.
I did a fair bit of Googling to try and find out when gcc -shared
started working, but couldn't find a reference. I'd guess it was pretty
early on, since I can't remember a time when Cygwin couldn't create
DLLs. (I've been using Cygwin since B18, the first packaged release.)
There have been occasional problems. For instance, I seem to recall a
problem where C++ library DLLs failed when thrown exceptions crossed the
DLL boundary, many years ago. While that problem existed, the standard
recommendation was to build affected libraries statically, since they
wouldn't work right otherwise. But, that's very much not the same thing
as "Cygwin cannot create DLLs."
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple