Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Thu, 20 Mar 2003 13:54:25 +0100 From: Corinna Vinschen To: cygwin-developers AT cygwin DOT com Subject: Re: Bump version to 1.5.0 Message-ID: <20030320125425.GM21269@cygbert.vinschen.de> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20030319211947 DOT GA29068 AT redhat DOT com> <3E78E3DA DOT 7060408 AT yahoo DOT com> <20030320012217 DOT GA32105 AT redhat DOT com> <3E79B303 DOT 8060608 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E79B303.8060608@yahoo.com> User-Agent: Mutt/1.4i On Thu, Mar 20, 2003 at 07:24:35AM -0500, Earnie Boyd wrote: > > I can also see the possibility for 32/64 bit versions for each new > > release with 32bit versions using libcygwin1.a while 64bit versions > > using libcygwin2.a. An arbitrary date would be set to remove support > > for a 32bit versions. That's the whole idea. Since old and new apps should still work together (e.g. share a common process table) the real work still should be done by the cygwin dll which is then called cygwin2.dll. All 32/64 apps directly call cygwin2.dll. cygwin1.dll is the DLL which consists enirely of entry points for the old 16/32 apps but with no real functionality except for converting datatypes and calling the appropriate function in cygwin2.dll. There wouldn't even be a need to remove support for 16/32 apps since cygwin1.dll is not a big deal to maintain when it's finished. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.