I've always wanted to know if there is a default directory layout for C projects. You know, which folders should i put which files and such.
So I've downloaded lots of project's source codes on SourceForge and they were all different than each other. Generally, I found more or less this structure:
/project (root project folder, has project name) | |____/bin (the final executable file) | | |____/doc (project documentation) | | | |____/html (documentation on html) | | | |____/latex (documentation on latex) | | |____/src (every source file, .c and .c) | | | |____/test (unit testing files) | | |____/obj (where the generated .o files will be) | | |____/lib (any library dependences) | | |____BUGS (known bugs) | |____ChangeLog (list of changes and such) | |____COPYING (project license and warranty info) | |____Doxyfile (Doxygen instructions file) | |____INSTALL (install instructions) | | |____Makefile (make instructions file) | |____README (general readme of the project) | |____TODO (todo list)
Is there a default standard somewhere?
Edit: Sorry, really. I realised there are numerous similar questions for recommended C project directory files. But I've seen people say what they think is best. I'm looking for a standard, something that people usually follow.
Related Questions:
C - Starting a big project. File/Directory structure and names. Good example required
Folder structure for a C project
File and Folder structure of a App/Project based in C
Project Organization in C Best Practices
The src stands for source. The /src folder comprises of the raw non-minified code. The /src folder is used to store the file with the primary purpose of reading (and/or editing) the code. The /src folder contains all the sources, i.e. the code which is required to be manipulated before it can be used.
A project directory provides details of the organisations involved in a design and construction project. This may include their role, organisation name, address, phone numbers, email addresses and names of key contacts.
The src directory contains all of the source material for building the project, its site and so on. It contains a subdirectory for each type: main for the main build artifact, test for the unit test code and resources, site and so on.
Projects and folders are used to organize and structure the data in the database and can be created anywhere in the database hierarchy. A project or folder that contains a project, folder, or module is called the parent project or parent folder.
I would say "no", and your empirical evidence seems to support that.
I usually get confused right around when I need to decide between doc/
and docs/
...
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With