From: Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Problem with Automatic linking with RHIDE
Date: 14 Feb 2000 11:18:49 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 14
Message-ID: <888oap$dk7$1@nets3.rz.RWTH-Aachen.DE>
References: <88635h$h8d$1 AT news6 DOT svr DOT pol DOT co DOT uk>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 950527129 13959 137.226.32.75 (14 Feb 2000 11:18:49 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 14 Feb 2000 11:18:49 GMT
User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586))
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Mike Collins <Mike AT no_spam DOT e-col DOT freeserve DOT co DOT uk> wrote:
> I am writing a program that has a lot of C files. When I compile, everything
> compiles OK, but it can't all link because the list of C files is too long
> for the linker input line. 

In the subject line, you say you're using RHIDE. If so, you shouldn't
be having this problem. Not unless you're not using RHIDE to its full
extent, at least. RHIDE projects are your friend, here.

RHIDE, like 'make', already knows how to pass long command lines to
the compiler and linker.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.