[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: updated win32 macro
From: |
Akim Demaille |
Subject: |
Re: updated win32 macro |
Date: |
15 Mar 2001 10:41:27 +0100 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) |
| > My opinion is that AC_PROG_CC_WIN32 should contain an AC_REQUIRE of
| > AC_CANONICAL_HOST, and should ensure the case $host itself.
|
| Why?
To make it easier to read and write where it is used.
| There is no side effect if it is tested for on platforms other than
| cygwin.
Nor in my proposal. I'm just saying the AC_CANONICAL_HOST and case
should get into it, nothing more.
| And by being a little bit more generic less changes will be
| needed to work with (say) WINE. Or on a cross-compile chain.
We are probably misunderstanding each other. I don't understand what
you mean here.
| And the developer writing the configure test will still need to decide
| what to do if it fails && they are compiling on cygwin, so they still
| need a case statement.
It was not clear to me that ac_cc_win32 was the main point, I
understood that setting CC was the main point.
So if that's the case, then I have further comments to make. Don't
use the ac_cc name space at all when interacting with the user. Use
some upper case thing such as CC_MWIN32. I have no idea about it, but
I guess the C++ compiler will also want something similar?
- Re: updated win32 macro, (continued)
- win32 v4, Robert Collins, 2001/03/15
- Re: updated win32 macro, Robert Collins, 2001/03/15
- Re: updated win32 macro, Christopher Faylor, 2001/03/15
- Re: updated win32 macro, Lars J. Aas, 2001/03/15
- Re: updated win32 macro, Lars J. Aas, 2001/03/15
Re: updated win32 macro, Akim Demaille, 2001/03/15
Re: updated win32 macro, edward, 2001/03/15
Re: updated win32 macro, Robert Collins, 2001/03/15
Re: updated win32 macro, edward, 2001/03/15