Path: chuka.playstation.co.uk!news
From: SCEE Developer Support <ps_yaroze@interactive.sony.com>
Newsgroups: scee.yaroze.programming.gnu_compiler
Subject: Re: gcc DOS line length limit
Date: Mon, 21 Apr 1997 12:21:35 +0100
Organization: Sony Computer Entertainment Europe
Lines: 41
Message-ID: <335B4DBF.46E6@interactive.sony.com>
References: <335815c1.4298411@news.playstation.co.uk> <3358B3EC.120EBF4C@ulthwe.foobar.co.uk> <335c0c99.2878832@news.playstation.co.uk>
NNTP-Posting-Host: 194.203.13.10
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01 (Win95; I)

Alex Amsel wrote:
> 
> On Sat, 19 Apr 1997 13:00:44 +0100, Dave Smethurst
> <djs@ulthwe.foobar.co.uk> did quoth at me:
> 
> >SOURCE =       source.cpp
> >OBJ    =       source.o
> 
> >Anyway ... you can set any variable really. But there are some which
> >Make usually
> >likes to reserve.... can't list all of them.
> 
> That doesn't solve the problem - they are macros rather than
> environmental variables aren't they?
> 
> It is when the macros are expanded that problems occur.
> 
> Source = blah1.c blah2.c ... blah256.c
> 
> -> gcc blah1.c ... blah256.c
> 
> -> Command line > input limit
> 
> What is need is something like gcc @file where file contains the
> command line. (like in Watcom).
> 
> * Alex Amsel * Into Beyond Web Design & JAVA Programming *
> * http://www.intobeyond.com  *  WWFC Utter Rubbish 1996-7*
> MM - "Steve Corica is every bit as good as that Kinkladze"


You can split a long line over several lines using the '\'
ie line1 \
line2 \
line3 \
line4

Note that the text-parsing of 'make' is very poor,
so ensure there are no characters at all after the backslash.

Lewis