Re: source code organization in a C++ project

From:

Victor Bazarov <v.Abazarov@comAcast.net>

Newsgroups:

comp.lang.c++

Date:

Mon, 14 Dec 2009 15:41:21 -0500

Message-ID:

<hg67ve$jjc$1@news.datemas.de>

lhommedumatch wrote:

I'm working on a C++ project on linux and I want to use autotools.

Whatever. Off-topic here anyway.

Before that I need to change the organization of the projects.

If you say so.

For the moment, this is how it is organized:

bin for binaries
DEV/Makefile : a makefile for all the project
DEV/SOC/src => source code for socket classes
DEV/SOC/include => headers of socket classes
DEV/SOC/obj => .o files

DEV/DRI/src => .cc class for drivers
DEV/DRI/include => headers of drivers
DEV/DRI/obj => .o

and so on

DEV/LIB => libraries needed by the project

On open-sources project, I see :
src/
and then directory for each package:
src/socket (in this case) where you have ".cc", ".h" and ".o"

Is there rules for the source code organization?

No.

With autotools I need to put a Makefile.am in each directory that's
why I want to reorganize everything.

OK.

Any ideas will help me.

Get a copy of "Large Scale C++ Software Design" by Lakos. Outdated in
some areas, it still contains enough wisdom (about how to organise your
projects as well) to warrant having it in one's library.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask