It's possible I just wasn't paying attention or didn't read the right document!, but also maybe the plugin version could be made a little more visible.
#Android ndk versions upgrade
The docs I saw (for example, the final section of ) did not make it clear that the features being discussed were version-dependent or even that plugin version is something you need to be aware of (I initially assumed the android plugin automatically upgraded when you upgrade Android Studio). Using API 24, min API 9, ndk 9c, sdk 20 (buildozer. I tried several versions and the outcome is different for each trial. What I dont know is which sdk and ndk version to use. The API is 24, according to several sites.
#Android ndk versions how to
While I was getting the error I was trying to find a way of getting Gradle to tell me which versions of the plugins I was loading (in case- as eventually turned out to be happening- I was requesting 3.5.2 but actually getting something else) and wasn't able on my own to figure out how to do this. I am developing an app using buildozer on Ubuntu 18.04. Your installed version(s) of the Android Gradle plugin aren't listed in the Android Studio sdk tools like other things, it doesn't show up in gradlew -v. I created my adle by copying a adle from someone else's Android project and didn't realize a particular version of the android gradle plugin had been hardcoded by it. (This is with NDK r12b and Cocos2dx 3.As a piece of feedback, it is awkward that the version of the android gradle plugin you have installed is apparently very important, but is also relatively hidden. This is only based on what I found out with my testing, please let me know if I am wrong or I missed something We have the usual toolchain updates, improved defaults for better security and performance, and are making changes to our release process to better accommodate users that need stability without hindering those that want new features. If you are using Eclipse: I can’t help as I don’t know what effect changing project.properties will have on Java Android build with Eclipse. Android NDK r21 is now in beta It’s been a longer than usual development cycle (three months since NDK r20), so there’s quite a lot to discuss for this release. (As said, this behavior of cocos compile to search for any other available SDK will be changed in next release.).
#Android ndk versions update
Otherwise cocos compile command will try to use any version it can find, and also update your project.properties file. Important: Check in your android studio sdk manager that Android SDK for BOTH your gradle compile sdk version and the project.properties sdk version is installed. This will not effect the Java build in Android Studio, this is only for NDK build. Set that as the minimum version you want to support, but at least version 13. Both cocos compile and NDK build ignore all these settings in your gradle file, instead they read the API version set in project.properties files. But you can use any versions you want without worrying about any NDK related build issues or crashes. I prefer to use the latest 23 or 24 for compile SDK and 22 for target SDK to not trigger Android 6 permissions, and I use min SDK as 14 as our app can’t run well on very old devices with very low power GPUs. You can use ANY version that you want to use. In your gradle files, set the compile SDK version, the min SDK version, and target SDK version as you want. If you are using Android Studio, do this: And i am not sure if there is better way to fix it. Cocos console will stop if it doesn’t find the specified API level. So changed the logic a few days ago in this patch, it will be included in v3.14. And it works great until API 21, because API 21 break compatibility. We design like this is because developers may not have API 13, so it will be convenient to find a API that >= 13. For example, the content of project.properties is target=android-13Ĭocos console will find 13 first, if not found then will found 14, and 15 until it found a API level that >= 13.
But in pervious, cocos console will find the API level >= specified API level defined in project.properties. In previous, cocos command will select an API level equal or higher than specified API level, and now(after v3.13), it changed the strategy, it will find the specific API level and will stop if not found.ĭefault API level lies in APP_ROOT/proj.android/project.properties.
0 kommentar(er)
