Mail Archives: djgpp/1999/01/27/20:46:27
"Raju K.V" <rajukv AT wipinfo DOT soft DOT net> wrote:
> actually my idea is that each project can be associated with one or more
> makefiles. so if i can run make from rhide it should compile the source
> code in the current directory. another possibility is to associate a
> makefile with a project. the user should have an option of either creating
> a new makefile or use an existing one.
> i came across this problem when i compile unix/linux based utilities in
> dos. usually i run configure from bash prompt. then when i run make i run
> into compilation errors due to some settings in the source code which is
> unix specific. so i have to open rhide with the particular source file
> change it, go to bash prompt and run make again. this becomes tedious when
> the no. of source files to be changed in very large.
> i hope u got an idea of my problem.
For this use I think you should use the standalone editor (edi0417b.zip)
because you can do it and for that you don't need the RHIDE make and debug
features (the features not included in the standalone editor). Using RHIDE
you'll need to tweak the things because that isn't the normal use, with the
standalone editor that's the normal use. Note: the editor is the same used by
RHIDE, just linked with other .o files.
> another thing i noticed in rhide compared to BC++ is that when compiling
> if an error is detected in one of the header files, if i click on the
> error message rhide does not open the header file automatically.
Hmmm... are you sure? What exactly do you mean? Pressing enter doesn't load
the file?
SET
------------------------------------ 0 --------------------------------
Visit my home page: http://welcome.to/SetSoft
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013
- Raw text -