[ANNOUNCEMENT] Shadow Framebuffer Test 12

Robert Collins robert.collins@itdomain.com.au
Thu Apr 5 03:08:00 GMT 2001


----- Original Message -----
From: "Smith, Martin" <martin@exchange.Scotland.NCR.COM>
To: "Cygx (E-mail)" <cygwin-xfree@sources.redhat.com>
Sent: Thursday, April 05, 2001 8:01 PM
Subject: RE: [ANNOUNCEMENT] Shadow Framebuffer Test 12


> Aha. Thanks for the explanation of why multiple cygwin dlls is a 'bad
> thing'. I was aware of the recommendation to avoid this but wasn't
clear on
> why (since, in my experience, this is not usually a problem with other
> Windows DLLs as long as they are kept in separate paths). Apologies if
this
> detailed explanation is already covered in the FAQ.

It is.

> On a related note, has the 'signature' of the cygwin dll changed with
> releases as well? ie. Have the exported functions changed? If so, does
this
> imply that sticking with the latest version might 'break' programs
expecting
> an earlier version?

>From B20.1 to now, only new functions have been exported. (AFAIK). I.E.
the ABI of B20.1 is a strict subset of the current ABI. The API has
changed somewhat, so newer compiles won't necessarily be able to work
with older cygwin1.dll's.

Rob



More information about the Cygwin-xfree mailing list