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 To: "Robert Collins" Cc: "Alexandre Oliva" , , Subject: Re: updated win32 macro References: <035401c0ac91$3ba21fd0$0200a8c0 AT lifelesswks> <022001c0accf$29b724d0$0200a8c0 AT lifelesswks> <007f01c0ad2e$f3dc5d20$0200a8c0 AT lifelesswks> <00a301c0ad32$57ad0220$0200a8c0 AT lifelesswks> <00c801c0ad36$01ec3370$0200a8c0 AT lifelesswks> <011a01c0ad41$c0fbc9a0$0200a8c0 AT lifelesswks> <01b801c0ad4b$9b2f1380$0200a8c0 AT lifelesswks> From: Akim Demaille Date: 15 Mar 2001 13:45:25 +0100 In-Reply-To: <01b801c0ad4b$9b2f1380$0200a8c0@lifelesswks> Message-ID: Lines: 21 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii >>>>> "Robert" == Robert Collins writes: >> | What does the high level interface do ? (I suggest it sets the Robert> variables >> | named above, setting them to " " as a minimum if WIN32 is found, >> and | nothing if it is not. >> >> What's the point? Just define a user var to the proper flags if >> needed, and set the current compiler to use it. Robert> To enable the user to test for the win32 API in Robert> configure.in. Robert> (A few emails back now - the second half of the issue). I know Robert> a lot of users will just be compiling a win32 only program and Robert> don't care, but I work openBSD to windows _all the time_... On Robert> second thought, lets just set WIN32="yes" if we found Robert> it. That's fairly intuitive. Then there is yet another thing to introduce IMHO, AC_SYS_WIN32 or so, which does define this symbol to yes/no. You high level macro ac_requires it.