cocos2dx-3.x compiling Android (lua,c++)

Environment variables Nothing to say, the online mass;

The direct compilation section here, if you are the CPP project, then the compilation is very clear, direct CD to Android project, and then run the build_native.py, what parameters need to be filled directly, and patiently wait for it;

But, I believe many comrades in the cocos2dx-3.x after the work of the LUA Project, the compilation of Android, the project a look, no build_native.py, suddenly dumbfounded. How can this be good? Oh..

If you are careful when you compile the CPP project, open the build_native.py file and look at it, you will find the mystery, the most central place lies in this sentence:

Command = ' Cocos compile-p android-s%s-m%s '% (App_android_root, Build_mode)

It's just a matter of invoking the Cocos engine to compile, so is there any build_native.py in your LUA project?

We can call this command ourselves:

CD LUA Engineering catalog ..../proj.android

Cocos compile-p android-m Release

If the project outside to compile the project, then add a (-s path) is good, it is best to search the Internet Cocos compile, all kinds of parameter description will come

Here, the compilation section ends

cocos2dx-3.x compiling Android (lua,c++)