This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Is cygwin1.dll backward compatible?
- To: Dario Alcocer <alcocer at helixdigital dot com>
- Subject: Re: Is cygwin1.dll backward compatible?
- From: egor duda <deo at logos-m dot ru>
- Date: Sat, 20 Oct 2001 18:56:45 +0400
- CC: cygwin at cygwin dot com
- Organization: deo
- References: <15313.35640.955278.459904@coyote.priv.helixdigital.com>
- Reply-To: egor duda <cygwin at cygwin dot com>
Hi!
Saturday, 20 October, 2001 Dario Alcocer alcocer@helixdigital.com wrote:
DA> I have a custom application that was compiled with the 1.1.8-2 version
DA> of the Cygwin DLL. I've since upgraded the Cygwin DLL to 1.3.2. The
DA> custom app seems to run fine under 1.3.2, but I'm worried that there
DA> might be some potential problems lurking in this setup.
DA> So, is cygwin1.dll designed for this type of backward compatibility?
DA> Do all applications which where compiled for version A of cygwin1.dll
DA> need to be re-compiled to run with version B of cygwin1.dll?
DA> I've never seen any of the app tar balls be re-done whenever the DLL
DA> changes, but I wanted to make sure that this was by design.
yes. if/when cygwin team is about to make backward-incompatible
changes to cygwin, dll is supposed to be renamed to cygwin2.dll
you can look at "api major" and "api minor" lines in output from
'cygcheck -v -s'. "api minor" is incremented whenever anybody makes
forward-incompatible changes to dll (such as exporting new function or
data from dll). "api major" is incremented whenever backward-
incompatible change is made.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/