I can see that if I use the create_project.py script to make all my cross platform project files, it puts the result in a ‘projects’ directory inside the cocos2d-x-2.1.4 folder.
I can see how that is convenient, in that if you make a bunch of projects they all go there, and the samples are right beside them (in the ‘samples’ directory).
However, I wish to put my project’s folder into its own source code control repo. This is troublesome because cocos2d-x-2.1.4 is itself in a repo from source code control (assuming I want to pull directly from the repo).
Additionally, I may not want my project directory to be the root of my project’s repo. I may have a bunch of other stuff to put in its repo too: source graphics files, documentation, etc.
So my question is, how do people handle putting the project’s location outside the cocos2d-x-2.1.4 directory structure? What is the recommended way to do it?
Can the create_project.py script accommodate a specified directory for the created project?
I realize I could maybe edit my project file, but I need to do this for all platforms, not just one, so I can’t be editing them all.
I believe it’s good practice to keep the projects outside of the toolkit’s directory, so this should be a supported use case.
To summarize, here’s the directory structure I’d like:
path/cocos2d-x-2.1.4/samples contains the demonstration samples
path/cocos2d-x-2.1.4/projects contains toy projects I make using the script
path/myrepo is my own repo containing a bunch of stuff including
path/myrepo/myproject is my project dir
Basically, I want myproject to live in path/myrepo instead of in path/cocos2d-x-2.1.4/projects.
Does that make sense?