Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Wed, 14 Mar 2001 15:33:08 +0100 From: "Lars J. Aas" To: Robert Collins Cc: cygwin-apps AT sources DOT redhat DOT com, autoconf AT gnu DOT org Subject: Re: -mwin32 test macro Message-ID: <20010314153308.A7048@sim.no> References: <035401c0ac91$3ba21fd0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <035401c0ac91$3ba21fd0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Thu, Mar 15, 2001 at 01:15:31AM +1100 On Thu, Mar 15, 2001 at 01:15:31AM +1100, Robert Collins wrote: : It sets ac_cc_win32 to yes or no as appropriate, so test writers in : configure.in can do an AC_SUBST or AC_DEFINE and switch off bits of : their code, or do as above, and fail the configure script. It's more useful to set it to "true" / "false". Then you can write if $ac_cc_win32; then ... fi instead of having to do a string comparison like if test x"$ac_cc_win32" = x"yes"; then ... fi Lars J -- Innovation is one percent inspiration and ninetynine percent perspiration, and in my case; twice that... -- Norville Barnes, `The Hudsucker Proxy'