-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicating source #5
Comments
Thank you for the feedback :) The reason it's like this is so that ChilliSource can be included as a git sub-module in your project. That has two benefits. First of all it's easy to keep the project up to date with the latest version of the engine. Secondly, if you need to hop back to a previous version of your project you don't need to keep track of which version of ChilliSource was used to build it. This isn't made clear to a first time user however and it's a common complaint, so we're currently looking into alternatives. |
I see but make changes to my fork, commit/push, update submodule and build the lib multiple times for each test project is a little tiring and each copy is more than 500 mb. |
What I've done is make a config.py script which setup what path all the other scripts will take. I also configured the CS project to build on its project directory. This way you can customize to point to any path or environment variable. |
Using config files like that comes with a number of issues of their own:
Config files are still being considered, but we're currently leaning towards a different approach. This would involve two different versions of the engine:
This is all still up for debate though, so we'll have to see how it turns out :) |
You have some points. I currently using an environment variable. The copy_windows_resources.py for example uses the project dir to link to the game source and the CS framework too. |
Is it really necessary to make a copy of the ChilliSource each new project?
Why not link to the source instead?
It reminds me a traumatic experience with cocos.
The text was updated successfully, but these errors were encountered: