From: kalum AT myflat DOT com
Message-Id: <199910091206.GAA05120@lakdiva.slt.lk>
To: <GKinney AT nextransport DOT com>
Date: Sat, 9 Oct 1999 06:06:59 +0600
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: RE: Please Help.  RHIDE generated makefiles don't support dependencies?
CC: djgpp AT delorie DOT com
In-reply-to: <DB85AFBE7C0DD311BF260004ACB80BFCEC3B@nex_server.nextransport.com>
X-mailer: Pegasus Mail for Win32 (v3.12)
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 8 Oct 99, at 9:44, George Kinney 
<GKinney AT nextransport DOT com> wrote:
> 	make sure 'all dependencies in makefile' is checked, and you might
> want to check
> 	'only #include "..." in depencies' as well (so you aren't listing
> std headers as dependencies).
> 
> 	Now, and this is the important part: Rhide doesn't know what the
> file's dependencies are
> 	until it has compiled it. So click a source file, and go to
> run->compile. Then generate a 
> 	makefile and take a look. 
> 
> 	A little example, before compile I get:
> 	DEPS_1=bmp.c
> 	bmp.o:: $(DEPS_1)
> 		$(RHIDE_COMPILE.c.o)
> 
> 	After compile, and re-generate makefile, I get:
> 	DEPS_1=bmp.c\
> 			e:/src/pic2html/bmp.h\
> 			e:/src/pic2html/defs.h\
> 			e:/bin/djgpp/include/sys/version.h\
> 			e:/src/pic2html/pinfo.h
> 	bmp.o:: $(DEPS_1)
> 		$(RHIDE_COMPILE.c.o)
> 
> 	So I think that if you compile the individual source files, then
> generate a makefile, you'll
> 	be ok. (I guess Rhide was designed with the assumption that you'd be
> doing 
> 	incremental testing and compilation, which isn't a bad design
> methodology IMHO, 
> 	but it could still stand to have a 'generate dependencies' option.)
> 
> 	Good luck.
> 

salvador <salvador AT inti DOT gov DOT ar> wrote
> I don't know what exactly do you have wrongly configured, I use 
RHIDE for
> SETEdit and Turbo Vision (both part of RHIDE ;-) and I generate 
the makefiles
> from the project all the time. The make works perfect. I use 
RHIDE 1.4.7,
> perhaps you should take a look to the v2tk/tv108s.zip package to 
see what is
> enabled in the djgpp/librhtv.gpr project.
> 
> SET

Thank's my friends for your patience in replying to me but it still 
doesn't work. I tried what george suggested exactly(compiled then 
generated a makefile).
When  examined the makefile has -:
DEPS_1=test.cpp\
                d:/d/test.h
test.o:: $(DEPS_1)
        $(RHIDE_COMPILE.cpp.o)
However after exiting to dos and modifying test.h and running make 
it still gave the same message 'nothing to be done for"all"'. So I ran 
make with the -d option and had a look at the dump and I could'nt 
find any references to test.h ! 
Here's the dump of 'make -f  test.mak -d'  

      No need to remake target `d:/d/test.cpp'.
     Finished dependencies of target file `d:/d/test.o'.
     Dependency `d:/d/test.cpp' is older than dependent `d:/d/test.o'.
    No need to remake target `d:/d/test.o'.
   Finished dependencies of target file `test.exe'.
   Dependency `d:/d/test.o' is older than dependent `test.exe'.

As you note there is no mention of test.h as a dependency of 
test.o.
Is it probably that I'm missing a additional switch to make ?
Any ideas are most welcome as I don't understand the makefile 
syntax that much.
> perhaps you should take a look to the v2tk/tv108s.zip package to 
>see what is
> enabled in the djgpp/librhtv.gpr project.
Will do as soon as possible (I am very busy just now).
Also I will try to get RHIDE 1.4.7 (I use 1.4).
Thank you very much all.
Kalum S <kalum AT myflat DOT com>