By the way are you sure that 3rdparty android libs compiled with ndk r16 will work fine with latest ndk r16b? From my past experience there were very often problems with ndk. @zhangxm , @mozartalouis
The ndk16b doesn’t have any significant changes that I see would make it brake it’s current compatibility.
I think the Coco’s team should only worry about updating the ndk version when a major release comes out (Ex. 17, 18, etc.) Since updating Everytime will just add to their queue of work.
I’ve tested on a fresh branch and 16b works fine.
@zhangxm has already committed the updates libs that are compiled with c++_static.
gnu_c++ is deprecated in NDK r16 any will be deleted in r18(if i remember correctly)
gcc will be removed too
NDK uses unified header files in NDK r16
So we should change to use clang+libc++. We will focus on a specific NDK version when releasing cocos2d-x, and we will mention it on release note when releasing.
Should I test the gradle build and fix most of the LINT messages?
The main problem is, that in a quick check it was not possible to gradlew build because of two errors within the lastest github v3 commit (with a new created project). One was a corrupt proguard file and the other was a wrong order in the AndroidManifest file.
I could test it on 28. december, if this is a wish or someone (e.g. @mozartalouis) else will do it.
@anon98020523 Yep, it should work as i fixed cocos gen-libs for Android too. @mars3142 sorry, i can not catch your issue. Could you please describe it in more detail? Thanks.