Newbe Dev Stack

Answer : You can just download the android-NDK from their archives and integrate it with your android studio. You can download android-NDK 15 from the given URL: https://developer.android.com/ndk/downloads/older_releases To connect it with android studio, extract it into your drive and in android studio, go to File -> Project Structure -> SDK Location -> NDK Path (Put extracted path here) If you're using Gradle plugin 3.5 or later (in beta at time of writing, but will be out soon), add the following to your build.gradle: android { ndkVersion "19.2.5345600" // NDK r19c } If you're using an older Gradle plugin, you can download old NDK releases from https://developer.android.com/ndk/downloads/older_releases and point ndk.dir in your local.properties file at that instead. As stated in the docs: Use the sdkmanager tool to view versions of CMake and NDK packages that are available: sdkmanager --list Pass the sdkmanager the strings...

Answer : Instead of passing the argument --sdk_root for each single command execution, let's deep dive into the real cause. Starting from Android SDK Command-line Tools 1.0.0 (6200805) , in contrast to Android SDK 26.1.1 (4333796) , the tools directory hierarchy has been changed. Previously it was placed right inside ANDROID_HOME (which is deprecated, we will use the term ANDROID_SDK_ROOT for the rest of the paragraph), now it's still named as tools (the only thing you'll get after unpacking the downloaded commandlinetools zip file), but differently, you have to place it inside a directory called cmdline-tools on your own. The name cmdline-tools comes from its package name, where you can get from listing packages command sdkmanager --list , whose outputs include cmdline-tools;1.0 | 1.0 | Android SDK Command-line Tools . Wrapping tools directory inside cmdline-tools directory would make it work, and help you get rid of the annoying --sdk_root argument. But ...