Mail Archives: djgpp/2004/04/03/05:45:23
Bryan Parkoff <bryan DOT nospam DOT parkoff AT nospam DOT com> wrote:
> The only one problem is that I am not allowed to include *.h (header
> files) into RHIDE's project group otherwise error message says, "Don't know
> how to build "*.h".
That's primarily a target conflict. Putting files into the project is
how you teach RHIDE which ones to *compile*, not as a shortcut to
opening them.
I haven't even tried to use RHIDE myself in ages, being a firm
believer in emacs and makefiles, but I seem to remember the
recommended method to edit header files in this kind of IDE is to open
one of the source files including them and then typing a special
hotkey with the cursor on their filename (Ctrl-Return?).
This organization makes more sense with C programs, where you almost
certainly wouldn't ever start a modification by editing a header file,
but rather have to update the header after you made some change to the
source, so it's natural to jump from the source to the header. C++ is
different because it has inline member functions in the headers.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -