Last time I tested my game with android was with V3.0 and it worked well back then.
I just thought even it is official not supported some devs use Apportable with V3.49…
But this is probably not the case and android clean up should be in V3.5
Currently this give me a lot of problems, when I'm trying to fix SpriteBuilder project errors with 3.5 code. So, this is a not really a good idea to separate them.
I'm using SB 2.0 code from here - https://github.com/spritebuilder/SpriteBuilder.git
Code in 3.5 branch should not be used in any way. It is temporary one. I will let everyone know when we will be ready to present an alpha version.
I'm not using it to find bugs, I just want to compile it SB, but if you changed structure in this way, it probably won't be compiled at all in future.. or really hard to fix.
We won't compile SB on our own. SB should be used as an app from AppStore. 3.5 will be backwards compatible with SB1.5, but won't be used to compile SB as nobody really wanna do it.
As you see, I'm trying to do so, but I don't know if I able to do so, especially with such changes. However, I will try later, when 3.5 will arrive.
I agree with kamikaze, trying to compile SB with your version can be interesting, and maybe fixing a couple of bugs the same time ... I tried too with your 3.5-dev branch
Unless there is somebody who want to do it, sb won't be ported to 3.5 version.
at least let us try ...
Would also be nice if we could get rid of all the private headers, and just make everything available.
I also never did understand why some things made into private headers in the first place. There is nothing really that unsafe. It is kind of routine work, but ok, we really should do this.
Btw, did you recieve my last PM?
looks like your CCProjectGenerator was a good idea http://cocos2d-x.org/docs/cocos/cocos/
They seem to be have far more robust generator, we can't afford this due to we have to use Xcode