build-template should sync the changes with cocos2d-x-lite/template about example-projects HOT 9 CLOSED

Those files are used to cover the engine original template files, so we need to keep them in the example-case in order to make the example scene feature will be ok

from example-projects.

what's the engine original template files, do you means template in cocos2d-x-lite? and what time the cover behavior occurs, can you describe it in detail.

from example-projects.

yes， when we build the project to native platform, the editor will check the build-template folder if there any file could be cover, the editor will help you to do that

from example-projects.

those files will cover the original files that in cocos2d-x-lite

from example-projects.

so what's the meaning to do this work? keep both template is not convenient to maintain. and the build-template folder have not changed for 2 years.

you can compare the AppActivity.java between build-template and template to see the difference. some changes isn't sync to build-template/.../AppActivity.java

from example-projects.

I tried how this part of the feature to work just now ...

That is the example-case, I built to the Android platform. There has been added a new fold named proj.android and check the proj.android-studio you will find its AppActivity.cpp has been covered by the files that exist in proj.android.

from example-projects.

I think those files do not get any change because this part of feature has not got any change for two years. It only calls a custom function in AppActivity.java

from example-projects.

thanks for explain, it shouldn't be removed, but modified, I will change the title.

build-template/.../AppActivity.java should sync the changes with build/AppActivity.java

from example-projects.

ok, I already get what's kind of problem will happen if we did not fixe the AppActivity.java with this pr
cocos/engine-native#808
and as I just test, that problem still exists.

from example-projects.