www.delorie.com/archives/browse.cgi | search |
----- Original Message ----- From: "Akim Demaille" <akim AT epita DOT fr> To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au> Cc: "Alexandre Oliva" <oliva AT lsd DOT ic DOT unicamp DOT br>; <cygwin-apps AT sources DOT redhat DOT com>; <autoconf AT gnu DOT org> Sent: Thursday, March 15, 2001 11:45 PM Subject: Re: updated win32 macro > >>>>> "Robert" == Robert Collins <robert DOT collins AT itdomain DOT com DOT au> 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |