From:	"Sean L. Palmer" <seanpalmer AT mindspring DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Rhide:long command lines problem
Date:	28 Mar 1997 18:44:22 GMT
Organization:	MindSpring Enterprises
Lines:	30
Message-ID:	<01bc3ba6$9d52f200$260b1d26@ghost.artnet.net>
References:	<5g92lk$p0a$1 AT ict DOT cec DOT uchile DOT cl> <33293102 DOT 5829 AT Mathematik DOT tu-chemnitz DOT de> <01bc3a1e$957601a0$ee0b1d26 AT ghost DOT artnet DOT net>
Reply-To:	"Sean L. Palmer" <spalmer AT pobox DOT com>
NNTP-Posting-Host:	ip38.van-nuys2.ca.pub-ip.psi.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

> I'm a different guy with essentially the same problem.
> 
> I JUST NOW DOWNLOADED v2.01, RHIDE1.2, Make 3.75.  I have never before
used
> DJGPP, so mixing is not an issue.
> 
> I have about 300 files that need to be compiled. I put them all in the
> project and do a build, and voila I get "Command line too long" in the
info
> window back.
> 
> Now what?  Is the command line too long for Windows 95?  Will getting rid
> of/shortening include paths, disabling compiler options (these are far
too
> wordy IMHO) and such help, or if I have that many files am I just screwed
> no matter what?
> 
> I've compiled projects with just a few files before, no problem.

Actually I found the issue, it was that I'd made a file type out of the
.gpr extension which associated .gpr files with rhide.exe... unfortunately
when doing this there was no shell loaded at all I guess.  So I made it run
4dos.com instead and had it shell to rhide with -crhide %1, and it compiles
now.

Just thought you'd like to know.

But the compiler is failing to find an intermediary file (*.cc.sched) in
the ENOENT directory I guess...

- Raw text -