![]() ![]() ![]() But I don't know whether that might cause some other problems, especially if you eventually decide to actually use the NDK. Note that you may be able to just type the expected folder into this field I did not try that. This will be something like:Ĭlick the OK button and build again. Once the installation completes and you close the installation progress dialog, the location of the NDK will be automatically written into the Android NDK location field. In that case, below that field will be a link for installing the NDK. ![]() If you have not installed the NDK, this field will be empty. Introduction 1. Since disk space is cheap, and my time is precious to me, I humored this bug by installing the NDK, even though I do not intend to use it.įile -> Project Structure -> SDK LocationĪnd look in the Android NDK location field. Terms and Conditions This is the Android Software Development Kit License Agreement 1. This is just a warning and does not prevent your build from completing, but it is annoying. The problem is that Gradle is computing the location of an NDK folder by just tacking on the string "/ndk-bundle" to the SDK folder location, even if you have never installed the NDK.Īfter establishing this false expectation of an NDK folder existing in a particular location, each time you build, Gradle gives you a warning that you're "missing" that folder. In contrast to the other options available in the NDK, there is no. However, as mentioned in another answer here by xsveda, this is a Gradle bug that is documented here:Īnd so even the "NDK-innocent" may become its victims. You can unlock the developer options on any Android smartphone or tablet by locating. I am not using the NDK at all, and had never installed the NDK. I was able to prevent this annoying message here is what worked for me. Sdk.dir=C\:\\Users\\Emily Thacker\\AppData\\Local\\Android\\SdkĪlso I do not see a ANDROID_NDK_HOME file in my directory. # For customization when using a Version Control System, please read the # as it contains information specific to your local configuration. # This file should *NOT* be checked into Version Control Systems, # Do not modify this file - YOUR CHANGES WILL BE ERASED! I am pretty sure I am not using NDK and I dont see how I can fix this problem here is my local.properties # This file is automatically generated by Android Studio. If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning." It is currently set to C:\Users\Emily Thacker\AppData\Local\Android\Sdk\ndk-bundle. It contains the toolchains (such as compiler and. If you are using NDK, verify the ndk.dir is set to a valid NDK directory. If you are using the IL2CPP scripting back end for Android, you need the Android Native Development Kit (NDK). "Configuration on demand is an incubating feature. So I cant use the gradle console to debug my app because I have this warning. I'm assuming it's a bug since I didn't have any problems until the new update. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |