Mail Archives: cygwin-developers/1998/06/10/19:09:10

From: noer AT cygnus DOT com (Geoffrey Noer)
Subject: How programs can check which Cygwin32 version is running
10 Jun 1998 19:09:10 -0700
Message-ID: <19980611011518 DOT I7978 DOT cygnus DOT cygwin32 DOT developers AT cygnus DOT com>
References: <3 DOT 0 DOT 3 DOT 32 DOT 19980530102201 DOT 0106d6f0 AT exchange DOT parallax DOT co DOT uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Andy Piper <andyp AT parallax DOT co DOT uk>, Sergey Okhapkin <sos AT prospect DOT com DOT ru>
Cc: cygwin32-developers AT cygnus DOT com

On Wed, Jun 03, 1998 at 08:38:53AM +0100, Andy Piper wrote:
> I thought if something else while I was driving in this morning. I know
> cygwin32 is "beta" but with XEmacs (and I guess other things as well) there
> is no way to tell which beta version someone is running. Obviously the
> version has implications on the features supported and the include
> files.

Well, configuration mechanisms can currently check the version output
from uname.  That's one way to do it.

> It would be great if you could start shiping a version include file that 
> developers could test to see whether a feature is supported or not. Between
> b18 and b19 I had to do a nasty hack of checking for something I knew was
> in one and not the other.
> The ideal solution would be for __CYGWIN32__ to be a number defined by gcc
> so that you could do
> #if __CYGWIN32__ > 19_1

The easiest thing to do would be to move the winsup/version.h file
into winsup/include/cygwin32 and let people check the major and minor
versions from that file.

Would that be sufficient for what you had in mind?

Geoffrey Noer
noer AT cygnus DOT com

- Raw text -

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