public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: Re: Built XWin on mingw - with patches
Date: Wed, 09 Nov 2011 18:46:00 -0000	[thread overview]
Message-ID: <4EBACA74.3090704@dronecode.org.uk> (raw)
In-Reply-To: <4EB83346.8090007@cwilson.fastmail.fm>

On 07/11/2011 19:36, Charles Wilson wrote:
> On 11/7/2011 1:10 PM, Jon TURNEY wrote:
>> I see what you are trying to do here, but I'm not sure it actually adds
>> any clarity.
>>
>> I think I'd just prefer to assume the knowledge that WIN32 and CYGWIN
>> are mutually exclusive, so '#if defined(WIN32)&&  !defined(__CYGWIN__)'
>> can just be written '#ifdef WIN32'
>
> But this isn't true if you ever #include any of the w32api headers. Then
> you get WIN32 defined, even on cygwin...

True.  I guess what I meant to say is that there isn't any compiler which 
defines both WIN32 and CYGWIN (I hope :-)).

Any portable code which includes w32api headers before checking if WIN32 is 
defined isn't going to be very portable :-)

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

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


  reply	other threads:[~2011-11-09 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 20:40 Ryan Pavlik
2011-11-03 19:18 ` Jon TURNEY
2011-11-04 23:39   ` Ryan Pavlik
2011-11-07 18:10     ` Jon TURNEY
2011-11-07 19:36       ` Charles Wilson
2011-11-09 18:46         ` Jon TURNEY [this message]
2011-11-09 19:11           ` Charles Wilson
     [not found]             ` <CABMFTE8wrNqbNLX+jmd7WcxT-xqfxYctB-ZgmxfwBg38_g5xmw@mail.gmail.com>
2011-11-10 22:58               ` Charles Wilson
2011-11-10 16:50       ` Ryan Pavlik
2011-11-22  2:55         ` SeongNam Oh
2012-01-09 19:31         ` Jon TURNEY

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=4EBACA74.3090704@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@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).