ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2001/10/20/10:33:44

Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
From: Dario Alcocer <alcocer AT helixdigital DOT com>
MIME-Version: 1.0
Message-ID: <15313.35640.955278.459904@coyote.priv.helixdigital.com>
Date: Sat, 20 Oct 2001 07:33:28 -0700
To: cygwin-apps AT cygwin DOT com
Subject: Is cygwin1.dll backward compatible?
X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid

I have a custom application that was compiled with the 1.1.8-2 version
of the Cygwin DLL.  I've since upgraded the Cygwin DLL to 1.3.2.  The
custom app seems to run fine under 1.3.2, but I'm worried that there
might be some potential problems lurking in this setup.

So, is cygwin1.dll designed for this type of backward compatibility?
Do all applications which where compiled for version A of cygwin1.dll
need to be re-compiled to run with version B of cygwin1.dll?

I've never seen any of the app tar balls be re-done whenever the DLL
changes, but I wanted to make sure that this was by design.

-- 
Dario Alcocer -- Sr. Software Developer, Helix Digital Inc.
alcocer AT helixdigital DOT com -- http://www.helixdigital.com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019