Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<3952FF9A.F9A68E9E@ece.gatech.edu>
Date:	Fri, 23 Jun 2000 02:11:38 -0400
From:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
X-Mailer:	Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	nhv AT cape DOT com
CC:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: New GCC available for testing (TRY 3) -- fixes -mno-cygwin pr oblem
References:	<000001bfdcc1$ce9a97e0$ec36ba8c AT nhv>

Norman Vine wrote:
> 

> 
> Also IMHO it seems as if the _WIN32 define is sometimes useful
> for instance when building DLL's
> 
> #if defined(_WIN32)
>    #if defined(MAKEDLL)
>    #  define INTERFACE __declspec(dllexport)
>    #elif defined(USEDLL)
>    #  define INTERFACE __declspec(dllimport)
>    #else
>    #  define INTERFACE
>    #endif
> #else
> #  define INTERFACE
> #endif
> 
> I maintain it would be a GOOD THING if we the Cygwin user
> community came up with a 'standard way' of doing this.

Why not:

#if defined(__CYGWIN__)
  #if defined(MAKEDLL) ...
etc.

__CYGWIN__ implies WIN32, but WIN32 does not always imply cygwin. The
build rules for making dlls will be different for 'typical' Win32 (e.g.
MSVC or Borland, or mingw-gcc & cygwin-gcc -mno-cygwin)  and cygwin
(gcc). The former category should use WIN32 (or __MINGW__ etc); the
latter ought to use __CYGWIN__.

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -