From: "Mike Collins" <Mike AT NO_SPAM DOT e-col DOT freeserve DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Problem with Automatic linking with RHIDE
Date: Mon, 14 Feb 2000 20:18:08 -0000
Organization: Customer of Planet Online
Lines: 41
Message-ID: <889nk1$tr$1@news8.svr.pol.co.uk>
References: <88635h$h8d$1 AT news6 DOT svr DOT pol DOT co DOT uk> <888oap$dk7$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
NNTP-Posting-Host: modem-128.elros.dialup.pol.co.uk
X-Trace: news8.svr.pol.co.uk 950559169 955 62.136.189.128 (14 Feb 2000 20:12:49 GMT)
NNTP-Posting-Date: 14 Feb 2000 20:12:49 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Well, thanks for the comment, but I assure you that I *am* having this
problem. When RHIDE tries to link the program, it shows the link command in
a window, and the whole line is there, but the end of the line is

"... menu.o window.o"

The link dies with the comment "No such file as wind"  (half of the last
file, window.o).
I used RHIDE to write a makefile automatically (very nice feature!), and ran
a MAKE under DOS, and it worked.

Is there a way of calling the MAKE without going out of RHIDE first? Doing
an RHIDE MAKE only simulates it - it doesn't call the MAKE program.

I may have an old version - I'm not sure what differences are in any later
version - but I'm running V1.3 (June, 1997)

Thanks again,

Mike.

Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de> wrote in
message news:888oap$dk7$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE...
> 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.