From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Why is __unix__ defined, and not __WINDOWS__ ?
Date: Mon, 13 May 2019 04:40:00 -0000 [thread overview]
Message-ID: <b5cce884-1654-255c-fe5c-0ec460368b53@SystematicSw.ab.ca> (raw)
In-Reply-To: <75d7872a826c01b59f2576fa0bd5bf73@smtp-cloud8.xs4all.net>
On 2019-05-12 14:54, Houder wrote:
> On Sun, 12 May 2019 13:33:30, Mike Gran via cygwin" wrote:
>> I think these days the canonical defines are (somebody correct me if
>> I'm wrong)
>> __CYGWIN__ for Cygwin
>> _WIN32 as 1 on MinGW when the compilation target is Windows 32-bit
>> ARM, 64-bit ARM, x86, or x64. Otherwise, undefined.
>> _WIN64 as 1 on MinGW when the compilation target is Windows 64-bit
>> ARM or x64. Otherwise, undefined
> https://sourceforge.net/p/predef/wiki/Home/
That information is 15 years out of date, a lot of the platforms are dead or
obsolete, and compilers are gone or changed a lot. There is no attempt at
discrimination across clang or gcc platforms, and no mention of Cygwin or Mingw
platforms, newlib or musl libraries, nor mention of other feature test macros:
better do "man feature_test_macros" for currently useful information.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
next prev parent reply other threads:[~2019-05-13 4:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 18:22 Agner Fog
2019-05-12 19:52 ` Houder
2019-05-12 19:54 ` Hans-Bernhard Bröker
2019-05-12 20:29 ` Lee
2019-05-13 4:12 ` Agner Fog
2019-05-13 5:40 ` Brian Inglis
2019-05-13 14:49 ` Agner Fog
2019-05-13 16:16 ` Yaakov Selkowitz
2019-05-13 7:56 ` Soegtrop, Michael
2019-05-12 20:33 ` Mike Gran via cygwin
2019-05-12 20:54 ` Houder
2019-05-13 4:40 ` Brian Inglis [this message]
2019-05-13 10:04 ` Houder
2019-05-12 22:00 ` Houder
2019-05-12 23:12 ` Houder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5cce884-1654-255c-fe5c-0ec460368b53@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).