Mail Archives: djgpp/2000/06/14/11:30:43
Charles <ddoss AT columbus DOT rr DOT com> wrote:
> opened that one up. The problem i had been having was that i had
> saved the file as .c , and iostream.h is for c++.
That's one of the potential problems I suspected, and which I asked
you to show your compilation command line for.
> I do have one last, less important question now, though:
> When i have test.cpp in one directory /djgpp/myprograms/ how can i get the
> test.o and test.exe to be created in the same directory instead of just in
> /djgpp???
The output files are by default created in the current directory. 'cd'
to where the sources are, before you compile, and the .o and .exe will
be there, too.
> Also, when i click compile and then make in Rhide, where is it
> getting the instructions on what to do??
Nowhere particular. It knows how the C compiler works, and
automatically does the right thing (most of the time).
> What makefile is it using to 'make' ??
None. RHIDE doesn't call 'make'.
> I'm trying to learn what I would type at the command line if there was no
> 'compile' or 'make' button, or what i would put into a makefile.
Read 'README.1st' again, for that.
For thorough information about Makefiles, read 'info make'
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -