This is the mail archive of the
mailing list for the Cygwin project.
Re: updated win32 macro
>>>>> "Robert" == Robert Collins <firstname.lastname@example.org> writes:
>> Then it seems to me that the interface is not right. Maybe
>> something like
Robert> Good suggestion. Then the developer can simply check for
Robert> HAVE_WINDOWS_H afterwards.. I like :] What about the language
Robert> specific issues? Or should AC_HEADER_WINDOWS look for _every_
Robert> compiler that it knows how to set WIN32 on?
Nope, I'd say the current compiler, adn you should provide a variable
that contains the needed switch. Then it is up to the user to give it
to her CXX if it is G++ etc.
Or maybe give two interfaces, one being low level computing this
switch for the current compiler (and *no caching*), so that the low
level user can test all her compilers, and a high level one: that
>> which would do the whole thing might be what you need. Also, why
>> do you set CC and not CFLAGS (and maybe LDFLAGS)? This is a tricky
>> question, I often wondered, not only in the present case.
Robert> Because I misunderstood the ac_* variable vs the CAPITALISED
Robert> ONES. Does this mean I get to set CC again?
There are two things. One is that the interface with the user is
typically in capitals, but that is not really required. It makes
sense in the present case to capitalize it (the difference is more or
less, lower case variables are shell variables only, and upper case
denotes values which might escape configure, eg, be AC_SUBST'd in a
The second thing is that in any case ac_/AC_ etc. variables are
private to Autoconf, no user should ever have to use them.