DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Hg/yabm6B+L24n+fECMbx7RhUhBFREhTO2rdN5bZRdO
	TFw5wF8lW2Rc3u0jqhpHwYeRtTEjvfYMzaEaEtgJnHyaftoD1UUEbsyUAmE32NJF
	c8uuMATsor+Qo0beOv5Fl/7gFtOn9bgWm3mASbk9/ltpd4KSUr3eD3AshjLWlLu8
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <8e9bfbb4-2139-639d-afaa-dfbacac1a8d9@t-online.de>
References: <5fbb6229-da17-c056-19b9-9819c684a8ad@agner.org> <8e9bfbb4-2139-639d-afaa-dfbacac1a8d9@t-online.de>
From: Lee <ler762@gmail.com>
Date: Sun, 12 May 2019 16:29:36 -0400
Message-ID: <CAD8GWsunE-dWOGmvOd18d6Q1L-WhYQWHA8xkwb5sazaZZ0pQJw@mail.gmail.com>
Subject: Re: Why is __unix__ defined, and not __WINDOWS__ ?
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On 5/12/19, Hans-Bernhard Bröker wrote:
> Am 12.05.2019 um 20:22 schrieb Agner Fog:
>
>> I have noticed that the gcc and clang compilers have defined the
>> preprocessing macro __unix__, but not __WINDOWS__, _WIN32, or _WIN64
>> when compiling a windows executable.
>>
>> Why is this?
>
> Because it's correct that way.  Cygwin runs on Windows, but it _is_ not
> Windows.

Or you can use a cross-compiler to create a 'native' windows
executable that doesn't require any of the cygwin dlls.

$ echo | gcc -dM -E -xc - | grep '#define _WIN32 '

$ echo | i686-w64-mingw32-gcc -dM -E -xc - | grep '#define _WIN32 '
#define _WIN32 1

Lee

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple