Re: updated win32 macro

[edward]

it's a language feature.

it attempts to answer the following question:

how do i get a windows C-based [.c, .cc, .m] file to an object file?

it's just syntactic sugar for -mwin32, which itself is syntactic sugar for
setting some defines, some include paths.

iirc, it doesn't set the *link* parameters though. that's a separate issue
on cygwin systems, which may want to target cygwin or mingw backends.

this is a fine mess we're in =)

cheers,
edward

----- Original Message -----
From: "Akim Demaille" <address@hidden>
To: "Robert Collins" <address@hidden>
Cc: "Alexandre Oliva" <address@hidden>;
<address@hidden>; <address@hidden>
Sent: Thursday, March 15, 2001 8:05 AM
Subject: Re: updated win32 macro


> >>>>> "Robert" == Robert Collins <address@hidden> writes:
>
> >> 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.
>
> Robert> Doesn't that just check the _current_ support ?
>
> Sorry, I don't understand.
>
> Is the feature your trying to test related to the compiler, or to the
> system?  If the language is relevant, then indeed AC_SYS is wrong.  If
> the language is not, then I don't understand your sentence: all that
> matters is whether we are running this system or not, to decide, for
> instance, of the programs to compile.