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 Message-ID: <01c401c0ad4c$7e469ad0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Akim Demaille" Cc: "Alexandre Oliva" , , 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> Subject: Re: updated win32 macro Date: Thu, 15 Mar 2001 23:35:56 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 15 Mar 2001 12:30:07.0310 (UTC) FILETIME=[AB37FEE0:01C0AD4B] ----- Original Message ----- From: "Akim Demaille" To: "Robert Collins" Cc: "Alexandre Oliva" ; ; Sent: Thursday, March 15, 2001 11:45 PM Subject: Re: updated win32 macro > >>>>> "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. > Doesn't that just check the _current_ support ? Rob