Skip to main content
1 of 2

Version Control

Recently I've started thinking about how to layout the directory structure for my game engine. And well, I kinda hit a little snag.

There's going to be 2 people working on this project. Me and one of my friends. The problem is how do I do the layout of the directories so that it works nicely with version control (I'm using plastic scm. It has really nice features).

I'm thinking of deviding it up into 3 seperate ideas:

  1. A source code respository for storing all the C++ code

  2. A exported asset repo where my friend can store all his exported data. (Exported as in final version that can be used by the engine).

  3. And a raw asset directory where all my friends raw assets go into. These include stuff like psd files and mb files for easier backup and versioning.

What do you guys think of this structure. Any comments are welcome. I'm really down in the dirt with this one.