On Sat, Sep 29, 2001 at 07:12:28AM +0200, Ralf Corsepius wrote:
Am Fre, 2001-09-28 um 19.15 schrieb 1001697323:
Do you think this is a logical way to do this?? Or this is weird?
Well, this is the way imake applied (still applies ?).
IMHO, it is weird, error-prone and hard to maintain :)
I never had problems with letting header and source files
be in the same subdir which has the name of the project itself.
Instead it gets easier to build different-named subprojects
together at the same time. W.r.t. to a prodesk I'd simply
bind all *.h and *.c into a subdir prodesk/prodesk,
On Fri, Sep 28, 2001 at 07:45:25PM +0200, Guido Draheim wrote:
I never had problems with letting header and source files
be in the same subdir which has the name of the project itself.
Instead it gets easier to build different-named subprojects
together at the same time. W.r.t. to a prodesk
Hi all,
I'm wondering about how to organize the header (.h) files on my project.
The structure is like the following: the directory prodesk, which is
the toplevel directory, contains a subdirectory named core, and another
one named include, both hanging from the topdir.
In my header files, I
Am Fre, 2001-09-28 um 19.15 schrieb 1001697323:
Hi all,
I'm wondering about how to organize the header (.h) files on my project.
The structure is like the following: the directory prodesk, which is
the toplevel directory, contains a subdirectory named core, and another
one named include,
