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:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
X-Apparently-From:	<earnie?boyd AT yahoo DOT com>
Message-ID:	<3AB0C6A2.8AFE126C@yahoo.com>
Date:	Thu, 15 Mar 2001 08:41:54 -0500
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To:	cygwin-apps AT sources DOT redhat DOT com, Earnie Boyd <autoconf AT gnu DOT org>
X-Mailer:	Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	edward <tailbert AT yahoo DOT com>
CC:	Robert Collins <robert DOT collins AT itdomain DOT com DOT au>,
	cygwin-apps AT sources DOT redhat DOT com, autoconf AT gnu DOT org
Subject:	Re: updated win32 macro
References:	<035401c0ac91$3ba21fd0$0200a8c0 AT lifelesswks><022001c0accf$29b724d0$0200a8c0 AT lifelesswks><orelvz60mr DOT fsf AT guarana DOT lsd DOT ic DOT unicamp DOT br><007f01c0ad2e$f3dc5d20$0200a8c0 AT lifelesswks><00a301c0ad32$57ad0220$0200a8c0 AT lifelesswks><mv4elvz5pma DOT fsf AT nostromo DOT lrde DOT epita DOT fr><00c801c0ad36$01ec3370$0200a8c0 AT lifelesswks><mv466hb5ohw DOT fsf AT nostromo DOT lrde DOT epita DOT fr><011a01c0ad41$c0fbc9a0$0200a8c0 AT lifelesswks><mv4snkf43ot DOT fsf AT nostromo DOT lrde DOT epita DOT fr><01b801c0ad4b$9b2f1380$0200a8c0 AT lifelesswks><mv4k85r42vu DOT fsf AT nostromo DOT lrde DOT epita DOT fr><01c401c0ad4c$7e469ad0$0200a8c0 AT lifelesswks> <mv4bsr341z1 DOT fsf AT nostromo DOT lrde DOT epita DOT fr> <000001c0ad53$b37dc9b0$9865fea9 AT edward>

I still don't think all of this fuss is really worth it but I'm going to
add my 29 cents worth in this thread.

AISI, what is needed is only whether or not the the compiler supports a
-mwin32 switch.  Then the configure.in can use it.

Code for what's needed in a portable fashion and don't worry about the
what ifs.

Earnie.


edward wrote:
> 
> 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" <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 8:05 AM
> Subject: Re: updated win32 macro
> 
> > >>>>> "Robert" == Robert Collins <robert DOT collins AT itdomain DOT com DOT au> 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.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

- Raw text -