This document outlines how the Wargamer project is laid out. What modules do what and how they rely on each other
I have tidied this up a bit from how it was in the original version.
Notably by moving all the makefile includes into a
and moving the source code modules into a
This keeps the root folder fairly clean
+--config +--src | +--<moduleName> | | \--o | | \--debug | | \--final +--lib | \--debug | \--final +--utils +--doc +--res | \--nap1813 +--o | \--debug | \--debug \--exe \--nap1813
The root also contains various makefile for building the project. There are different makefiles for building just the battle game, campaign game or the combination, as well as campaign editor, battle editor, and various utility and test programs.
The only other stuff left in the root are things such as README, the Gnu Licence, INSTALL, etc
src folder contains a seperate subfolder for each module,
as well as a few utility and test projects. (which should probably be moved into a
Each module contains
.hpp files all mingled together.
A few of the utility projects seperate out the C and H files into subfolders.
Currently there is no distinction between public includes and module includes,
so if one module uses another, the module folder is included in the INCLUDE path during compilation.
Object Files are stored in subfolders within the module's folder.
final depending on whether you
are compiling a debug or release version.