Alright so it sounds like you guys are just about done with this, looking forward to full C++ support around December 12th!
Given that it didn’t support C++ out of the box, what was the expected like workaround for all the devs in the meantime? I’ve been on 3.10 the whole time, waiting for this, but it’s surprising that it seems like C++ isn’t a priority for cocos.
Yes, can’t wait for this. I was shocked when building apk for simple game using Cocos Creator is way bigger in size. I hope with C++ support, it can reduce the size of exported apk. Thanks for C++ support.
some quick update:
The past days I worked on fixing bugs for v3.14, so I didn’t make any progress on it.
But I started working on it again.
We are going to support flatbuffers, and the Lua version will use the flatbuffers as well. So both Lua/C++ languages will be supported with this.
The previous work that I did (generating C++ files) helped me understand the requirements (and most of not all of the needed changes will be part of v3.14).
Now I’m working on the schema (the fbs files for Flatbuffers) and the parser of the generated files and some changes in the python script. It needs to output json files instead of c++ files.
@ricardo
Can you also add a feature to auto remove the libraries which are not used in the game?
By default all the libraries are included unless explicitly removed!
Sprites: BlendFunction seems to be broken on Creator (bottom left sprites look Ok on cocos2d-x but not on Creator). Only Raw+untrimmed sprites are supported. Not sure how to handle “trimmed” sprites.