From:	David Jenkins <me AT jenkinsdavid DOT demon DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Basic?? help with rhide needed.
Date:	Mon, 10 Mar 1997 12:09:44 +0000
Organization:	None
Distribution:	world
Message-ID:	<UXzacAAIo$IzEwGx@jenkinsdavid.demon.co.uk>
References:	<LPt7ODAM6BIzEwk$@jenkinsdavid.demon.co.uk>
	<3323D9DA DOT 48EE AT Mathematik DOT tu-chemnitz DOT de>
NNTP-Posting-Host:	jenkinsdavid.demon.co.uk
MIME-Version:	1.0
Lines:	32
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <3323D9DA DOT 48EE AT Mathematik DOT tu-chemnitz DOT de>, Robert Hoehne
<Robert DOT Hoehne AT Mathematik DOT tu-chemnitz DOT de> writes
>
>> Also when I compile a source from the DOS using gcc source.c -o
>> source.exe -lm it doesn't use/leave any .o files lying around.Why does
>> rhide, and how/where can I stop it from doing this????
>
>RHIDE does this, because it is in my opinion (and please no
>discussion about this here, because I defenitely will not change
>this) the only and best way to check all the dependencies
>of a program to build. (normally there are more than one
>source file for a program, which is not a "Hello world"-program).
>
>Robert
But can I turn this feature off temprorarily???
I have no idea of whether its good or bad, being new to C I can't discus
it with you ;-) but for now it'd make life easier not having to scan
through folders deleting these .o files.

Another thing I can only compile sources using Allegro by using -lalleg
as a compiler option, even though I have a

OOOOOPPPS ;-)
I just found out where ALL my problems are.I was setting my paths as
just include\ lib\ and obj\ instead of using G:\djgpp\include\ now
everything works fine ;-) Even the .o files are put into a convenient
folder which I can then delete.

-- 
http://www.jenkinsdavid.demo.co.uk for Newbie C programers and a larf. ;-)
David Jenkins

- Raw text -