Game Development Reference
In-Depth Information
tion should be avoided, as regenerating the solution file will remove all the local
changes.
• The
decoda
folder contains the individual Decoda IDE project files that corres-
pond to each chapter demo. These project files are not generated from build
scripts.
• The
lib
folder is an intermediate output folder where static libraries are com-
piled. It is safe to delete this folder, as Visual Studio will build any missing librar-
ies during the next build of the sandbox.
• The
media
folder contains all the shared assets used within the chapter demos.
Assets used by the sandbox exist as both loose files and ZIP bundles.
• The
premake
folder contains the build script used to configure the sandbox's
solution and project files. Any desired changes to the Visual Studio solution or
projects should be made in the Premake script.
Note
The Premake script will detect any additional C++ or Lua files within the pro-
ject's folder structure. When adding a new Lua script or C++ files, simply rerun
the build scripts to update the Visual Studio solution.
• The
src
folder contains the source code for each open source library as well as
the sandbox itself. Every project within the sandbox solution file will have a cor-
responding
src
folder, with separate folders for header files and source files.
Chapter demos have an additional script folder that contains every Lua script for
that particular chapter.
Note
Each open source library contains both a
VERSION.txt
and
LICENSE.txt
file, which states the version number of the open source library used as well as
the license agreement that must be followed by all users.
• The
tools
folder contains the installer for the Decoda IDE as well as the Pre-
make utility program that is used to create the Visual Studio solution.
