C + + Engineering catalog schema

The problem of the structure of the project directory is basically a benevolent see problem, as long as their own use, what kind of directory organization structure is nothing serious. Of course, if the project is large, the number of people involved, then a reasonable organization of the directory structure will be a great benefit. Different types of projects also have different directory structures, and here is a simple demonstration of the basic directory structure of the C + + project I am using.

Project--+---Build---+---debug
| |---release
|---Dist
|---doc
|---include---+---module1
| |---module2
|---lib
|---Module1
|---module2
|---Res
|---samples---+---sample1
| |---sample2
|---Tools
|---copyleft
|---Makefile
|---README
|--- ...

The following sections describe the purpose of each directory and file

build/: Project compilation directory, all kinds of compiled temporary files and final target files are stored here, divided into debug/and release/sub-directories

dist/: distribution directory, the final release of executable programs and various running support files in this directory, packaging this directory to complete project distribution

doc/: Saving a project's various documents

include/: Common header file directory, can be divided into the organization directory to save module related header files

lib/: external Dependent Library directory

res/: Resource Directory

samples/: Sample program Directory

tools/: Project support Tool catalogue

copyleft: copyright Notice file, of course, can also be called copyright:-)

Makefile: The project build configuration file, of course, may also be other types of build configuration files, such as Bjam

README: General documentation of the project

C + + Engineering catalog schema