During the last few weeks I’ve been working on a template project to kick off a new project quickly and efficiently.  After it took 17 minutes to get the project to blank screen for my first OneHourGameJame entry, it was time to improve the pipeline of starting a fresh project.  The adventure started by creating the directory structure, something I’ve been tweaking for many years and finding it has become fairly stable, looking like the following:

• ProjectName (Primary Working Directory)
  • build (contains premake4 script which makes the vs/xcode project in platform sub-dir)
    • automated (contains scripts including post_build and auto_build to automate processes)
    • platform (named windows or macosx, contains vs/xcode project)
  • documentation (for frameworks generate documentation here, or place game design doc etc)
  • run (contains the files and structure of the shipped project)
    • data (contains the final art, sound and other assets for the game or project, to be shipped)
  • source (contains all source code, including headers)

In a few long term projects I have even been known to add a source_art directory, and I’ve contemplated changing source to source_code for this ambiguity but haven’t really felt the need.

The template project has several scripts to automate processes, including auto_clean and auto_build.  My hope is to eventually create a master script that recursively goes down through my entire development directory stopping at each project with an auto_clean to clean them all.  This will save on harddrive space.  I did this manually a while back, deleting all obj, debug, release directories and other build generated files and saved over 2gb of space, so an automated process has been in my mind.  The master script would also check if a project has any modifications within the last 24 hours, and if it does, build both debug and release versions with the auto_build script.

To be safer, this master script would only call auto_ scripts from within an automated directory.  So automated/auto_* and it could theoretically have an auto_deploy or auto_test that generates a report.  For now, the master script is only in my mind, but the template project is prepared for the day it is written.

About the scripts

The contents of the template_project.zip are to be used at your own risk.  I am not to be held liable if they delete all your files or tweak something on your system.  They were not designed to any of the above, and I’ve found them immensely useful.  You will need to tweak the scripts.  The directory structure and scripts are working as I intended for my work-flow, your experiences will likely be different.  For starters the scripts are pulling TurtleBrains, require Premake4 from industriousone.com and Windows needed sed.exe installed and added to environment path.  The main script: createproject_tb will ask two questions, ProjectName and project_name.  One being the display name, and the other for files.

My personal coding standards do not allow me to use spaces or uppercase characters in my filenames.  I do not know how these scripts will behave with spaces in either those answers or in directories leading to where you run the script and create the project at.  This is not a problem for my setup, I tried to make sure to use “quotes” around all areas of the scripts, but found that sed did not like spaces in DisplayName of file_name parameters.

If you do find this useful, please let me know, the scripts work on both Windows (.bat) and Mac OS X (.sh).  I highly recommend you setup a template project of your own, it reduces the redundancy of the setup task, and once working, can allow you to create throw away projects which are actually quite helpful for testing and learning.

Too Long To Read?

• Download the template_project.zip (and use at your own risk)
  • Note there may be significant issues with spaces in directory paths or parameters.
• This template project fits my personal development structure using;
  • Premake4 to build VisualStudio / XCode projects
  • Latest revision of my TurtleBrains C++ game development framework
• The createproject_tb script, and all other scripts are written in and supported for;
  • .bat files for windows
  • .sh files for mac osx

This entry was posted on Sunday, May 17th, 2015 at 12:13 am and is filed under Code Quality, OneHourGameJam, Programming. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.