This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: 4.2 Project: "@file" support

From: Mark Mitchell <mark at codesourcery dot com>
To: Christoph Hellwig <hch at infradead dot org>
Cc: DJ Delorie <dj at redhat dot com>, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org, ian at airs dot com
Date: Thu, 25 Aug 2005 00:40:57 -0700
Subject: Re: 4.2 Project: "@file" support
References: <200508250450.j7P4oWkW029722@sparrowhawk.codesourcery.com> <xn3boyy47y.fsf@greed.delorie.com> <20050825071400.GA914@infradead.org>

Christoph Hellwig wrote:

That's what I meant with my comment btw.  It's a horrible idea to
put in all the junk to support inferior OSes into gcc and all other
other programs, and with cygwin and djgpp there are already two nice
enviroments for that.  If Mark wants to duplicate that in MinGw that's
of course fine aswell..

I cannot see any way to "fix" MinGW so that a user using a Windows command shell can invoke GCC with a long command line; by the time GCC is invoked, the command has already been truncated. That's why most (all?) compilers for Windows have "@file" or equivalent.

The obvious suggestion is that the user should use a "real" shell. However, since the user is often not invoking the compiler directly, but is instead using an IDE or some make program, that's not a practical option.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304

References:
- 4.2 Project: "@file" support
  - From: Mark Mitchell
- Re: 4.2 Project: "@file" support
  - From: DJ Delorie
- Re: 4.2 Project: "@file" support
  - From: Christoph Hellwig

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]