Modules - Folder Structure
Revision as of 19:03, 8 March 2010 by Jgvictores (talk | contribs) (Created page with 'The intention of defining this should be for each project to be self-contained. Each module directory should contain the following structure (full implementation is not necessary…')
The intention of defining this should be for each project to be self-contained. Each module directory should contain the following structure (full implementation is not necessary, as it was originally designed for compiled, c++-style projects):
- doc/
- extern/
- bin/
- linux-x86/
- win32/
- ...
- include/
- lib/
- linux-x86/
- win32/
- ...
- bin/
- mk/
- msvc9/
- linux-x86/
- ...
- out/
- share/
- win32/
- linux-x86/
- ...
- src/
- AUTHORS
- INSTALL
- install-win32.txt
Notes:
- A project generating shell script has been developed for this purpose.
- svn co ((your_code_repo))/trunk/tools/mkproy
- extern/ is intended for 3rd party libraries.
- share/ is intended for inclusion of multiplatform data for execution of the program, such as 3d models, etc... (was called 'data' in an earlier version of the standard).
- out/win32/, out/linux-x86, etc, must contain the platform-specific shared libraries and other complements necesary for the execution of the resulting application or library.