Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Type: text/plain; charset="iso-8859-1" From: Tim Prince Reply-To: tprince@computer.org To: "Eric Belhomme" , "Eric Belhomme" , Subject: Re: how-to use _WIN32 preprocessor with cygwin ? Date: Mon, 11 Nov 2002 06:03:47 -0800 References: <20021110192754.9C6662CA74@inet1.ywave.com> <002e01c2896d$ca899510$0a01a8c0@athlon> In-Reply-To: <002e01c2896d$ca899510$0a01a8c0@athlon> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20021111140349.E2B3E2CB0F@inet1.ywave.com> On Monday 11 November 2002 02:33, Eric Belhomme wrote: > > The cygwin-specific gcc compile flag -mwin32 causes the _WIN32 macro to > > be defined. Certain cygwin applications predate that arrangement, so > > confusion > > > is understandable. > > Thanks for your answer :-) > So I wonder I have to modify the configure script to add -mwin32 flag on > gcc option if I detect cygwin environment. Question : How to detect cygwin > environment ? Often done by the uname command, as on other Unixish systems -- Tim Prince -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/