Error: No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
I want to compile an open source android project (Netguard) using gradel (gradlew clean build) But I encountered this Error:
A problem occurred configuring project ':app'.
> Exception thrown while executing model rule: NdkComponentModelPlugin.Rules#cre
ateToolchains
> No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
I serached but didn't find enything helping. Here is the main build.gradle:
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle-experimental:0.6.0-alpha1'
}
}
allprojects {
repositories {
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
And here is the build.gradle of the app project:
apply plugin: 'com.android.model.application'
model {
android {
compileSdkVersion = 23
buildToolsVersion = "23.0.2"
defaultConfig.with {
applicationId = "eu.faircode.netguard"
minSdkVersion.apiLevel = 21
targetSdkVersion.apiLevel = 23
versionCode = 2016011801
versionName = "0.76"
archivesBaseName = "NetGuard-v$versionName-$versionCode"
}
}
android.ndk {
moduleName = "netguard"
toolchain = "clang"
ldLibs.add("log")
}
android.sources {
main {
jni {
source {
srcDir "src/main/jni/netguard"
}
exportedHeaders {
}
}
}
}
android.buildTypes {
release {
minifyEnabled = true
proguardFiles.add(file('proguard-rules.pro'))
ndk.with {
debuggable = true
}
}
}
android.buildTypes {
debug {
ndk.with {
debuggable = true
}
}
}
android.productFlavors {
create("all") {
}
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.android.support:appcompat-v7:23.1.+'
compile 'com.android.support:recyclerview-v7:23.1.+'
compile 'com.squareup.picasso:picasso:2.5.+'
}
And I'm using gradle-2.9-all and android-ndk-r10e. I don't know if I should mention anything else, so comment if you need any information.
add a comment |
I want to compile an open source android project (Netguard) using gradel (gradlew clean build) But I encountered this Error:
A problem occurred configuring project ':app'.
> Exception thrown while executing model rule: NdkComponentModelPlugin.Rules#cre
ateToolchains
> No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
I serached but didn't find enything helping. Here is the main build.gradle:
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle-experimental:0.6.0-alpha1'
}
}
allprojects {
repositories {
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
And here is the build.gradle of the app project:
apply plugin: 'com.android.model.application'
model {
android {
compileSdkVersion = 23
buildToolsVersion = "23.0.2"
defaultConfig.with {
applicationId = "eu.faircode.netguard"
minSdkVersion.apiLevel = 21
targetSdkVersion.apiLevel = 23
versionCode = 2016011801
versionName = "0.76"
archivesBaseName = "NetGuard-v$versionName-$versionCode"
}
}
android.ndk {
moduleName = "netguard"
toolchain = "clang"
ldLibs.add("log")
}
android.sources {
main {
jni {
source {
srcDir "src/main/jni/netguard"
}
exportedHeaders {
}
}
}
}
android.buildTypes {
release {
minifyEnabled = true
proguardFiles.add(file('proguard-rules.pro'))
ndk.with {
debuggable = true
}
}
}
android.buildTypes {
debug {
ndk.with {
debuggable = true
}
}
}
android.productFlavors {
create("all") {
}
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.android.support:appcompat-v7:23.1.+'
compile 'com.android.support:recyclerview-v7:23.1.+'
compile 'com.squareup.picasso:picasso:2.5.+'
}
And I'm using gradle-2.9-all and android-ndk-r10e. I don't know if I should mention anything else, so comment if you need any information.
Try to update the gradle tools. classpath 'com.android.tools.build:gradle:3.2.0-beta05'
– Photon Point
Aug 13 at 7:50
use developer.android.com/ndk/downloads/older_releases and Android NDK, Revision 16b (December 2017) version to download required folders and fix the issue.
– Panache
Oct 2 at 9:15
add a comment |
I want to compile an open source android project (Netguard) using gradel (gradlew clean build) But I encountered this Error:
A problem occurred configuring project ':app'.
> Exception thrown while executing model rule: NdkComponentModelPlugin.Rules#cre
ateToolchains
> No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
I serached but didn't find enything helping. Here is the main build.gradle:
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle-experimental:0.6.0-alpha1'
}
}
allprojects {
repositories {
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
And here is the build.gradle of the app project:
apply plugin: 'com.android.model.application'
model {
android {
compileSdkVersion = 23
buildToolsVersion = "23.0.2"
defaultConfig.with {
applicationId = "eu.faircode.netguard"
minSdkVersion.apiLevel = 21
targetSdkVersion.apiLevel = 23
versionCode = 2016011801
versionName = "0.76"
archivesBaseName = "NetGuard-v$versionName-$versionCode"
}
}
android.ndk {
moduleName = "netguard"
toolchain = "clang"
ldLibs.add("log")
}
android.sources {
main {
jni {
source {
srcDir "src/main/jni/netguard"
}
exportedHeaders {
}
}
}
}
android.buildTypes {
release {
minifyEnabled = true
proguardFiles.add(file('proguard-rules.pro'))
ndk.with {
debuggable = true
}
}
}
android.buildTypes {
debug {
ndk.with {
debuggable = true
}
}
}
android.productFlavors {
create("all") {
}
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.android.support:appcompat-v7:23.1.+'
compile 'com.android.support:recyclerview-v7:23.1.+'
compile 'com.squareup.picasso:picasso:2.5.+'
}
And I'm using gradle-2.9-all and android-ndk-r10e. I don't know if I should mention anything else, so comment if you need any information.
I want to compile an open source android project (Netguard) using gradel (gradlew clean build) But I encountered this Error:
A problem occurred configuring project ':app'.
> Exception thrown while executing model rule: NdkComponentModelPlugin.Rules#cre
ateToolchains
> No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
I serached but didn't find enything helping. Here is the main build.gradle:
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle-experimental:0.6.0-alpha1'
}
}
allprojects {
repositories {
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
And here is the build.gradle of the app project:
apply plugin: 'com.android.model.application'
model {
android {
compileSdkVersion = 23
buildToolsVersion = "23.0.2"
defaultConfig.with {
applicationId = "eu.faircode.netguard"
minSdkVersion.apiLevel = 21
targetSdkVersion.apiLevel = 23
versionCode = 2016011801
versionName = "0.76"
archivesBaseName = "NetGuard-v$versionName-$versionCode"
}
}
android.ndk {
moduleName = "netguard"
toolchain = "clang"
ldLibs.add("log")
}
android.sources {
main {
jni {
source {
srcDir "src/main/jni/netguard"
}
exportedHeaders {
}
}
}
}
android.buildTypes {
release {
minifyEnabled = true
proguardFiles.add(file('proguard-rules.pro'))
ndk.with {
debuggable = true
}
}
}
android.buildTypes {
debug {
ndk.with {
debuggable = true
}
}
}
android.productFlavors {
create("all") {
}
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.android.support:appcompat-v7:23.1.+'
compile 'com.android.support:recyclerview-v7:23.1.+'
compile 'com.squareup.picasso:picasso:2.5.+'
}
And I'm using gradle-2.9-all and android-ndk-r10e. I don't know if I should mention anything else, so comment if you need any information.
asked Feb 1 '16 at 10:29
Saeed
3,06293256
3,06293256
Try to update the gradle tools. classpath 'com.android.tools.build:gradle:3.2.0-beta05'
– Photon Point
Aug 13 at 7:50
use developer.android.com/ndk/downloads/older_releases and Android NDK, Revision 16b (December 2017) version to download required folders and fix the issue.
– Panache
Oct 2 at 9:15
add a comment |
Try to update the gradle tools. classpath 'com.android.tools.build:gradle:3.2.0-beta05'
– Photon Point
Aug 13 at 7:50
use developer.android.com/ndk/downloads/older_releases and Android NDK, Revision 16b (December 2017) version to download required folders and fix the issue.
– Panache
Oct 2 at 9:15
Try to update the gradle tools. classpath 'com.android.tools.build:gradle:3.2.0-beta05'
– Photon Point
Aug 13 at 7:50
Try to update the gradle tools. classpath 'com.android.tools.build:gradle:3.2.0-beta05'
– Photon Point
Aug 13 at 7:50
use developer.android.com/ndk/downloads/older_releases and Android NDK, Revision 16b (December 2017) version to download required folders and fix the issue.
– Panache
Oct 2 at 9:15
use developer.android.com/ndk/downloads/older_releases and Android NDK, Revision 16b (December 2017) version to download required folders and fix the issue.
– Panache
Oct 2 at 9:15
add a comment |
32 Answers
32
active
oldest
votes
1 2
next
Two years has passed, now if you come across here, you may possibly encounterd error message like this:
No toolchains found in the NDK toolchains folder for ABI with prefix mips64el-linux-android
or
No toolchains found in the NDK toolchains folder for ABI with prefix mipsel-linux-android
Latest NDK removed support for mips abi, and earler version of android gradle plugin still check for the existance of mips toolchain. see here for more info.
Solution: Upgrade android gradle plugin to 3.1 or newer.
e.g. Add following in the project level gradle [28-Sept-2018]
classpath "com.android.tools.build:gradle:3.2.0"
Workaround: Create mipsel-linux-android folder structure to fool the tool. The easiest way would be to symbolic link to aarch64-linux-android-4.9.
# on Mac
cd ~/Library/Android/sdk/ndk-bundle/toolchains
ln -s aarch64-linux-android-4.9 mips64el-linux-android
ln -s arm-linux-androideabi-4.9 mipsel-linux-android
4
Tried with gradle 4.1, didn't work, but workaround (creation of folder mipsel-linux-android-dummy) worked. Thanks @lazybug.
– user7154703
Sep 9 at 2:54
2
@Girish upgrade Android Gradle Plugin in top levelbuild.gradlefile, something likecom.android.tools.build:gradle:3.2.0-rc02, not Gradle version
– lazybug
Sep 10 at 8:52
thanks for correcting me
– user7154703
Sep 10 at 10:45
3
The Workaround mentioned here is the correct one:# on Mac cd ~/Library/Android/sdk/ndk-bundle/toolchains ln -s aarch64-linux-android-4.9 mips64el-linux-android ln -s arm-linux-androideabi-4.9 mipsel-linux-android
– Avijeet Dutta
Oct 3 at 3:43
10
On Windows:mklink /d mips64el-linux-android aarch64-linux-android-4.9andmklink /d mipsel-linux-android arm-linux-androideabi-4.9worked for me too.
– Mitch
Oct 7 at 6:02
|
show 9 more comments
I fixed this Error by uninstalling the NDK in the SDK-Tools.
So, if you don't need the NDK, uninstall it.
4
What if I need NDK?
– IgorGanapolsky
Jul 31 at 18:13
same here if we want NDK then what is the solution for it?
– Brijesh Joshi
Aug 29 at 11:57
Its fixed if uninstall the NDK but if you required to use NDK then please Check this stackoverflow.com/a/51589406/6533853
– Ninja
Sep 24 at 10:04
add a comment |
I have faced the same problem while update Android studio from 2.0 to 2.1 in my Windows 8 machine.
I found a solution for that.Please use the following steps.
- Download the android NDK for windows from https://developer.android.com/ndk/downloads/index.html.
- Extract the same and copy the "toolchain" folder from the bundle.
- Paste the folder under installed NDK folder under C:android-sdk-winndk-bundle.[Installed the path may vary based on your installation]
- Restart android studio.
This is happening because Android studio won't gets full NDK update in the stable channel. If you are not using NDK for your project development you can simply remove the NDK folder from your SDK directory.
1
Thanks it works in Windows 10 too!
– Ciro Mine
Sep 20 at 14:21
1
Works with Android Studio 3.2!
– maxwellnewage
Oct 2 at 15:13
1
This also worked for me for fixing the error "Error : Android MIPS ToolChain directory "" does not exist" in Game Maker Studio 2 on a Mac. But I needed to get version 17c of the NDK from here : developer.android.com/ndk/downloads/older_releases (as per: reddit.com/r/gamemaker/comments/9m958a/…) Thank You @nithinjith ! ... still not building however, need to solve :Android NDK: Please fix the APP_ABI definition in /Users/../Library/Android/sdk/ndk-bundle/build/core/default-application.mk
– kris
Oct 27 at 5:56
add a comment |
For Android studio 3.2.1+
Upgrade your Gradle Plugin
classpath 'com.android.tools.build:gradle:3.2.1'
and see the Magic Error gone.
Happy Coding -:)
add a comment |
Error message: “No toolchains found in the NDK toolchains folder for ABI with prefix: llvm” .
After fresh web installation of Android Studio with NDK, I imported an Android code sample that used NDK from GitHub and tried to compile it.
As a result had an Error:
No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
Solution:
for some reasons standard installation process on macOS had failed to install a complete set:
~/Library/Android/sdk/ndk-bundle had missed folder toolchains with all tools,
(it should be like this: ~/Library/Android/sdk/ndk-bundle/toolchains)
The solution was to download NDK separately, open it, copy folder toolchain and paste it to the folder:
~/Library/Android/sdk/ndk-bundle
After that it worked well for me.
2
It worked for me!
– Thinsky
Aug 24 '16 at 1:57
in my case it's there but no file there with prefix aarch64-linux-android. Any suggestion !!
– CoDe
Jul 28 '17 at 3:17
folder 'mips64el-linux-android-4.9' & 'mipsel-linux-android-4.9' are not available after ndk bundle 16, so i have to download and add these two folder in android sdk bundle inside toolchains folder hence issue solved, still didn't understand why this error?
– Fazal
Oct 29 at 8:42
add a comment |
Step-by-step:
1) Open the page with old NDK versions:
https://developer.android.com/ndk/downloads/older_releases

2) Agree the Terms:

3) Download the older version of NDK (for example 16b):

4) Open your toolchains directory.
5) Transfer files that you need from toolchains folder of downloaded zip-file to your toolchains folder:

6) Rebuild the Project:

UPD 30 Sep 2018:
I used Android NDK Revision r16b for fix this error in my own case. So I present the example with this version.
But it's better to use the Android NDK, Revision r17c (June 2018). It is the last one, supporting mips (reasonable reccomendation from Weekend's comment).
Instead of(for example 16b), it's better to clarify which NDK version is the last one supporting mips. via release note of Android NDK Revision r17c (June 2018): Support for ARMv5 (armeabi), MIPS, and MIPS64 has been removed. Attempting to build any of these ABIs will result in an error. It's16bexactly.
– Weekend
Sep 30 at 6:02
@Weekend Thanks for your recommendation. I added it to my answer.
– V.March
Sep 30 at 19:37
@vmarch Sorry but It's16bexactly. r17c is the first version which removed the support for MIPS :)
– Weekend
Oct 8 at 7:10
1
@Oh, I read your previous comment so very quickly. That's why I missed the point. My apologize! But these files are still present in the Android NDK, Revision r17c (June 2018). And in version 18 they were finally removed. Just look into the archive. developer.android.com/ndk/downloads/…
– V.March
Oct 8 at 14:15
@vmarch Well done! I didn't check r17c archive, just inferred the previous conclusion from release notes.
– Weekend
Oct 9 at 2:03
|
show 1 more comment
Without downloading, copying, or symlinking anything, I was able to "fix" the error by simply creating an empty directory where the older version of the Android Gradle plugin expects the removed mips toolchain:
mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/linux-x86_64
Obviously, $ANDROID_HOME points to the root of the Android SDK installation here. If you are using MacOS, replace linux-x86_64 with darwin-x86_64 in the command above. On Windows use windows-x86_64.
Worked like charm.
– Akbar Sha Ebrahim
Oct 10 at 12:17
Worked for me in Linux. dint work in mac
– Jay
Oct 15 at 10:00
add a comment |
I uninstalled the NDK since I didn't need it . Go to SDK manager on Android studio ( Tools -> Android -> SDK Manager ) . If NDK is installed . Just uncheck the box and click OK . The installed components will be deleted .
add a comment |
In my case, this error occured when creating a new Android Studio (Android studio 3.2.1) Java Project with
classpath 'com.android.tools.build:gradle:2.0.0-beta6'
So I´ve downgraded to
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
Not the best solution stay at an older version, but maybe it´s just a temporary bug in the beta as the NDK path in local.properties is still the same, but the IDE doesn´t complain anymore
I think this is a bug of outdated gradle plugin. Just update to the latest one. It helped to me (from 3.0 to 3.2.0-beta05 in my case)
– AnoDest
Aug 17 at 11:56
add a comment |
Android NDK 18.0* seems has an issue not creating all the files in folders after extraction. Due to it, your app compilation will fail which uses ndk builds.
Better is to use NDK 17.1* (https://developer.android.com/ndk/downloads/) etc version and you can extract or use the android studio extraction to ndk-bundle by default will work good.
add a comment |
Open Android Studio, Go to Tools then Android and then SDK, uncheck NDK If you do not need this, and restart android studio.
2
Thank you. It worked well for Unity.
– Carson
Oct 10 at 16:14
Great thank. It worked for my Unity project
– Leo Nguyen
Oct 22 at 8:47
add a comment |
In your project level Gradle file increase the dependencies
classpath version low to high like
dependencies {
classpath 'com.android.tools.build:gradle:3.0.0'
}
to change like
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
add a comment |
Find your own local android-SDK, if you download the relevant SDK of ndk, there will be a folder called "ndk-bundle"

There is a folder called "toolchains" inside.

We noticed that there are no mips64el related files inside.

The solution is as follows:
Click here to download the NDK package separately through the browser.
After unzipping, open the "toolchains" folder, compare it with the android-sdk->ndk-bundle->toolchains folder, find the missing folder, copy the past
3. Recompile, the problem is solved.
Hope it helps you mate
add a comment |
I've had a similar problem, but I wanted to use NDK version r9d due to project requirements.
In local.properties the path was set to ndk.dir=C:\Android\ndk\android-ndk-r9d but that lead to the problem:
No toolchains found in the NDK toolchains folder for ABI with prefix: [toolchain-name]
The solution was to:
- Install the newest NDK using sdk manager
- Copy the missing toolchain [toolchain-name] from the new ndk to the old. In my case from
sdkndk-bundletoolchainstondkandroid-ndk-r9dtoolchains
- Repeat the process till all the required toolchains are there
It looks to me that the copied toolchains are not used, but for some reason it is needed to for them be there.
add a comment |
I solved this question by unInstalled ndk, becasuse I dont't need it
add a comment |
Here is the fix.
When compiling a project in android studio, I occasionally encounter:
Error: No toolchains found in the NDK toolchains folder for ABI with
prefix: arm-linux-androideabi/llvm
This may be caused by updating related components. The solution is to Android studio ( Tools -> Android -> SDK Manager ) .
Select the ndk item and delete it. If the program needs it, you can re-install it. This will ensure that the folder location is correct and there will be no such problem.
add a comment |
Solved it by adding google() dependency into both repositories in build.gradle(Project: ProjectName). then sync your project
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.3.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
add a comment |
For me I think there might be some issue in installing android NDK from android studio. I was able to resolve this in following manner
Downloaded android ndk from
https://developer.android.com/ndk/downloads/index.html
and placed inside ndk-bundle (where your android sdk is installed ). For more info check this screens.
https://app.box.com/s/dfi4h9k7v4h0tmbu3z9qnqx3d12fdejn
add a comment |
If you are using Ionic 3 Remove ndk from android studio sdk tools.
Great, as a temporary solution for the specific need of building ionic android projects, although is not ideal.
– MFAL
Oct 12 at 8:12
add a comment |
[https://github.com/tensorflow/tensorflow/tree/master/tensorflow/examples/android][1]
For people trying out this example and facing issues with latest NDK. Can follow this solution.
In build.gradle
change this
classpath 'com.android.tools.build:gradle:3.0.1'
To
classpath 'com.android.tools.build:gradle:3.1.2'
The reason is mips are deprecated in the latest ndk versions, Gradle version 3.1.2 will not have a compulsion for mips. It assumes the presence for these missing folders.
add a comment |
Facing same issue.
I got success following ways.
Open your buldle.gradle file and upgrade the versions for following both classpath
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'
Then Sync and after get one dilaog for update Gradle version as well then click that link and wait for download all required updates(Hope internet available). After taking long time you got Success.
add a comment |
If you don't use the NDK, unset the environment variable ANDROID_NDK_HOME.
add a comment |
Steps I have followed to fix the issue as follows,
Analyze -> Code Cleanup
File -> Project Structures -> Select project from the list and update the gradle version to latest.
Build -> Clean Project
Build -> Make Project
Now the issue related to the build may get reported like using compile instead of implementation etc.
Please fix those and hopefully it should fix the issue.
add a comment |
I fixed the issue by reinstalling the NDK.
add a comment |
I have same error while adding NDK. I tried much and later I find below solution which works perfectly for me.
if you want to add NDK in your project then follow below step.
1. If you installed NDK using SDK Manager then uninstall first. (untick from SDK tools and apply)
2. Download manually NDK from its official site. (any version) if project old then prefer version 17.
3. Extract that file.
4. Go to your project structure > NDK path > add Extracted file path here.
5. Build Project. and its work.
add a comment |
just update classpath 'com.android.tools.build:gradle:X.X.X' in Project Build.Gradle and replace X to the latest version do you have
add a comment |
I faced same issue and I resolved this by
changing gradle version of project-label .gradle file to Latest
classpath 'com.android.tools.build:gradle:3.2.1'
and add these checks on app label .gradle file
packagingOptions{
doNotStrip '*/mips/*.so'
doNotStrip '*/mips64/*.so'
}
Hope This will help.
nice, thanks for copying my stackoverflow.com/a/50944898/192373
– Alex Cohn
Dec 13 at 16:30
@AlexCohn Our answers are similar . It doesn't implies that someone copied others answer. Btw Thanks for the info...
– Prinkal Kumar
Dec 13 at 16:43
add a comment |
I navigated to local.properties, and in there the
ndk.dir=/yo/path/for/NDK
line needs to be updated to where your ndk lies.
I was using Crystax NDK, and didn't realize the original Android NDK was still in use.
add a comment |
After three days I figured it out:
The problem can be solved by downloading an older version of the NDK (14b) and going to Android Studio to File | Project Structure and selecting it.
add a comment |
Upgrade your Gradle Plugin
com.android.tools.build:gradle:3.1.4
Upgrade gradle wraperpropeties
distributionUrl=https://services.gradle.org/distributions/gradle-4.4-all.zip
add a comment |
1 2
next
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: false,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f35128229%2ferror-no-toolchains-found-in-the-ndk-toolchains-folder-for-abi-with-prefix-llv%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
StackExchange.ready(function () {
$("#show-editor-button input, #show-editor-button button").click(function () {
var showEditor = function() {
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
};
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True') {
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup({
url: '/post/self-answer-popup',
loaded: function(popup) {
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
}
})
} else{
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true) {
showEditor();
}
}
});
});
32 Answers
32
active
oldest
votes
32 Answers
32
active
oldest
votes
active
oldest
votes
active
oldest
votes
1 2
next
Two years has passed, now if you come across here, you may possibly encounterd error message like this:
No toolchains found in the NDK toolchains folder for ABI with prefix mips64el-linux-android
or
No toolchains found in the NDK toolchains folder for ABI with prefix mipsel-linux-android
Latest NDK removed support for mips abi, and earler version of android gradle plugin still check for the existance of mips toolchain. see here for more info.
Solution: Upgrade android gradle plugin to 3.1 or newer.
e.g. Add following in the project level gradle [28-Sept-2018]
classpath "com.android.tools.build:gradle:3.2.0"
Workaround: Create mipsel-linux-android folder structure to fool the tool. The easiest way would be to symbolic link to aarch64-linux-android-4.9.
# on Mac
cd ~/Library/Android/sdk/ndk-bundle/toolchains
ln -s aarch64-linux-android-4.9 mips64el-linux-android
ln -s arm-linux-androideabi-4.9 mipsel-linux-android
4
Tried with gradle 4.1, didn't work, but workaround (creation of folder mipsel-linux-android-dummy) worked. Thanks @lazybug.
– user7154703
Sep 9 at 2:54
2
@Girish upgrade Android Gradle Plugin in top levelbuild.gradlefile, something likecom.android.tools.build:gradle:3.2.0-rc02, not Gradle version
– lazybug
Sep 10 at 8:52
thanks for correcting me
– user7154703
Sep 10 at 10:45
3
The Workaround mentioned here is the correct one:# on Mac cd ~/Library/Android/sdk/ndk-bundle/toolchains ln -s aarch64-linux-android-4.9 mips64el-linux-android ln -s arm-linux-androideabi-4.9 mipsel-linux-android
– Avijeet Dutta
Oct 3 at 3:43
10
On Windows:mklink /d mips64el-linux-android aarch64-linux-android-4.9andmklink /d mipsel-linux-android arm-linux-androideabi-4.9worked for me too.
– Mitch
Oct 7 at 6:02
|
show 9 more comments
Two years has passed, now if you come across here, you may possibly encounterd error message like this:
No toolchains found in the NDK toolchains folder for ABI with prefix mips64el-linux-android
or
No toolchains found in the NDK toolchains folder for ABI with prefix mipsel-linux-android
Latest NDK removed support for mips abi, and earler version of android gradle plugin still check for the existance of mips toolchain. see here for more info.
Solution: Upgrade android gradle plugin to 3.1 or newer.
e.g. Add following in the project level gradle [28-Sept-2018]
classpath "com.android.tools.build:gradle:3.2.0"
Workaround: Create mipsel-linux-android folder structure to fool the tool. The easiest way would be to symbolic link to aarch64-linux-android-4.9.
# on Mac
cd ~/Library/Android/sdk/ndk-bundle/toolchains
ln -s aarch64-linux-android-4.9 mips64el-linux-android
ln -s arm-linux-androideabi-4.9 mipsel-linux-android
4
Tried with gradle 4.1, didn't work, but workaround (creation of folder mipsel-linux-android-dummy) worked. Thanks @lazybug.
– user7154703
Sep 9 at 2:54
2
@Girish upgrade Android Gradle Plugin in top levelbuild.gradlefile, something likecom.android.tools.build:gradle:3.2.0-rc02, not Gradle version
– lazybug
Sep 10 at 8:52
thanks for correcting me
– user7154703
Sep 10 at 10:45
3
The Workaround mentioned here is the correct one:# on Mac cd ~/Library/Android/sdk/ndk-bundle/toolchains ln -s aarch64-linux-android-4.9 mips64el-linux-android ln -s arm-linux-androideabi-4.9 mipsel-linux-android
– Avijeet Dutta
Oct 3 at 3:43
10
On Windows:mklink /d mips64el-linux-android aarch64-linux-android-4.9andmklink /d mipsel-linux-android arm-linux-androideabi-4.9worked for me too.
– Mitch
Oct 7 at 6:02
|
show 9 more comments
Two years has passed, now if you come across here, you may possibly encounterd error message like this:
No toolchains found in the NDK toolchains folder for ABI with prefix mips64el-linux-android
or
No toolchains found in the NDK toolchains folder for ABI with prefix mipsel-linux-android
Latest NDK removed support for mips abi, and earler version of android gradle plugin still check for the existance of mips toolchain. see here for more info.
Solution: Upgrade android gradle plugin to 3.1 or newer.
e.g. Add following in the project level gradle [28-Sept-2018]
classpath "com.android.tools.build:gradle:3.2.0"
Workaround: Create mipsel-linux-android folder structure to fool the tool. The easiest way would be to symbolic link to aarch64-linux-android-4.9.
# on Mac
cd ~/Library/Android/sdk/ndk-bundle/toolchains
ln -s aarch64-linux-android-4.9 mips64el-linux-android
ln -s arm-linux-androideabi-4.9 mipsel-linux-android
Two years has passed, now if you come across here, you may possibly encounterd error message like this:
No toolchains found in the NDK toolchains folder for ABI with prefix mips64el-linux-android
or
No toolchains found in the NDK toolchains folder for ABI with prefix mipsel-linux-android
Latest NDK removed support for mips abi, and earler version of android gradle plugin still check for the existance of mips toolchain. see here for more info.
Solution: Upgrade android gradle plugin to 3.1 or newer.
e.g. Add following in the project level gradle [28-Sept-2018]
classpath "com.android.tools.build:gradle:3.2.0"
Workaround: Create mipsel-linux-android folder structure to fool the tool. The easiest way would be to symbolic link to aarch64-linux-android-4.9.
# on Mac
cd ~/Library/Android/sdk/ndk-bundle/toolchains
ln -s aarch64-linux-android-4.9 mips64el-linux-android
ln -s arm-linux-androideabi-4.9 mipsel-linux-android
edited Sep 28 at 8:53
Killer
1,81621838
1,81621838
answered Sep 6 at 12:28
lazybug
2,73611010
2,73611010
4
Tried with gradle 4.1, didn't work, but workaround (creation of folder mipsel-linux-android-dummy) worked. Thanks @lazybug.
– user7154703
Sep 9 at 2:54
2
@Girish upgrade Android Gradle Plugin in top levelbuild.gradlefile, something likecom.android.tools.build:gradle:3.2.0-rc02, not Gradle version
– lazybug
Sep 10 at 8:52
thanks for correcting me
– user7154703
Sep 10 at 10:45
3
The Workaround mentioned here is the correct one:# on Mac cd ~/Library/Android/sdk/ndk-bundle/toolchains ln -s aarch64-linux-android-4.9 mips64el-linux-android ln -s arm-linux-androideabi-4.9 mipsel-linux-android
– Avijeet Dutta
Oct 3 at 3:43
10
On Windows:mklink /d mips64el-linux-android aarch64-linux-android-4.9andmklink /d mipsel-linux-android arm-linux-androideabi-4.9worked for me too.
– Mitch
Oct 7 at 6:02
|
show 9 more comments
4
Tried with gradle 4.1, didn't work, but workaround (creation of folder mipsel-linux-android-dummy) worked. Thanks @lazybug.
– user7154703
Sep 9 at 2:54
2
@Girish upgrade Android Gradle Plugin in top levelbuild.gradlefile, something likecom.android.tools.build:gradle:3.2.0-rc02, not Gradle version
– lazybug
Sep 10 at 8:52
thanks for correcting me
– user7154703
Sep 10 at 10:45
3
The Workaround mentioned here is the correct one:# on Mac cd ~/Library/Android/sdk/ndk-bundle/toolchains ln -s aarch64-linux-android-4.9 mips64el-linux-android ln -s arm-linux-androideabi-4.9 mipsel-linux-android
– Avijeet Dutta
Oct 3 at 3:43
10
On Windows:mklink /d mips64el-linux-android aarch64-linux-android-4.9andmklink /d mipsel-linux-android arm-linux-androideabi-4.9worked for me too.
– Mitch
Oct 7 at 6:02
4
4
Tried with gradle 4.1, didn't work, but workaround (creation of folder mipsel-linux-android-dummy) worked. Thanks @lazybug.
– user7154703
Sep 9 at 2:54
Tried with gradle 4.1, didn't work, but workaround (creation of folder mipsel-linux-android-dummy) worked. Thanks @lazybug.
– user7154703
Sep 9 at 2:54
2
2
@Girish upgrade Android Gradle Plugin in top level
build.gradle file, something like com.android.tools.build:gradle:3.2.0-rc02, not Gradle version– lazybug
Sep 10 at 8:52
@Girish upgrade Android Gradle Plugin in top level
build.gradle file, something like com.android.tools.build:gradle:3.2.0-rc02, not Gradle version– lazybug
Sep 10 at 8:52
thanks for correcting me
– user7154703
Sep 10 at 10:45
thanks for correcting me
– user7154703
Sep 10 at 10:45
3
3
The Workaround mentioned here is the correct one:
# on Mac cd ~/Library/Android/sdk/ndk-bundle/toolchains ln -s aarch64-linux-android-4.9 mips64el-linux-android ln -s arm-linux-androideabi-4.9 mipsel-linux-android– Avijeet Dutta
Oct 3 at 3:43
The Workaround mentioned here is the correct one:
# on Mac cd ~/Library/Android/sdk/ndk-bundle/toolchains ln -s aarch64-linux-android-4.9 mips64el-linux-android ln -s arm-linux-androideabi-4.9 mipsel-linux-android– Avijeet Dutta
Oct 3 at 3:43
10
10
On Windows:
mklink /d mips64el-linux-android aarch64-linux-android-4.9 and mklink /d mipsel-linux-android arm-linux-androideabi-4.9 worked for me too.– Mitch
Oct 7 at 6:02
On Windows:
mklink /d mips64el-linux-android aarch64-linux-android-4.9 and mklink /d mipsel-linux-android arm-linux-androideabi-4.9 worked for me too.– Mitch
Oct 7 at 6:02
|
show 9 more comments
I fixed this Error by uninstalling the NDK in the SDK-Tools.
So, if you don't need the NDK, uninstall it.
4
What if I need NDK?
– IgorGanapolsky
Jul 31 at 18:13
same here if we want NDK then what is the solution for it?
– Brijesh Joshi
Aug 29 at 11:57
Its fixed if uninstall the NDK but if you required to use NDK then please Check this stackoverflow.com/a/51589406/6533853
– Ninja
Sep 24 at 10:04
add a comment |
I fixed this Error by uninstalling the NDK in the SDK-Tools.
So, if you don't need the NDK, uninstall it.
4
What if I need NDK?
– IgorGanapolsky
Jul 31 at 18:13
same here if we want NDK then what is the solution for it?
– Brijesh Joshi
Aug 29 at 11:57
Its fixed if uninstall the NDK but if you required to use NDK then please Check this stackoverflow.com/a/51589406/6533853
– Ninja
Sep 24 at 10:04
add a comment |
I fixed this Error by uninstalling the NDK in the SDK-Tools.
So, if you don't need the NDK, uninstall it.
I fixed this Error by uninstalling the NDK in the SDK-Tools.
So, if you don't need the NDK, uninstall it.
edited Aug 14 at 16:27
Robert Columbia
5,56782132
5,56782132
answered Mar 11 '16 at 15:16
Herzi
41533
41533
4
What if I need NDK?
– IgorGanapolsky
Jul 31 at 18:13
same here if we want NDK then what is the solution for it?
– Brijesh Joshi
Aug 29 at 11:57
Its fixed if uninstall the NDK but if you required to use NDK then please Check this stackoverflow.com/a/51589406/6533853
– Ninja
Sep 24 at 10:04
add a comment |
4
What if I need NDK?
– IgorGanapolsky
Jul 31 at 18:13
same here if we want NDK then what is the solution for it?
– Brijesh Joshi
Aug 29 at 11:57
Its fixed if uninstall the NDK but if you required to use NDK then please Check this stackoverflow.com/a/51589406/6533853
– Ninja
Sep 24 at 10:04
4
4
What if I need NDK?
– IgorGanapolsky
Jul 31 at 18:13
What if I need NDK?
– IgorGanapolsky
Jul 31 at 18:13
same here if we want NDK then what is the solution for it?
– Brijesh Joshi
Aug 29 at 11:57
same here if we want NDK then what is the solution for it?
– Brijesh Joshi
Aug 29 at 11:57
Its fixed if uninstall the NDK but if you required to use NDK then please Check this stackoverflow.com/a/51589406/6533853
– Ninja
Sep 24 at 10:04
Its fixed if uninstall the NDK but if you required to use NDK then please Check this stackoverflow.com/a/51589406/6533853
– Ninja
Sep 24 at 10:04
add a comment |
I have faced the same problem while update Android studio from 2.0 to 2.1 in my Windows 8 machine.
I found a solution for that.Please use the following steps.
- Download the android NDK for windows from https://developer.android.com/ndk/downloads/index.html.
- Extract the same and copy the "toolchain" folder from the bundle.
- Paste the folder under installed NDK folder under C:android-sdk-winndk-bundle.[Installed the path may vary based on your installation]
- Restart android studio.
This is happening because Android studio won't gets full NDK update in the stable channel. If you are not using NDK for your project development you can simply remove the NDK folder from your SDK directory.
1
Thanks it works in Windows 10 too!
– Ciro Mine
Sep 20 at 14:21
1
Works with Android Studio 3.2!
– maxwellnewage
Oct 2 at 15:13
1
This also worked for me for fixing the error "Error : Android MIPS ToolChain directory "" does not exist" in Game Maker Studio 2 on a Mac. But I needed to get version 17c of the NDK from here : developer.android.com/ndk/downloads/older_releases (as per: reddit.com/r/gamemaker/comments/9m958a/…) Thank You @nithinjith ! ... still not building however, need to solve :Android NDK: Please fix the APP_ABI definition in /Users/../Library/Android/sdk/ndk-bundle/build/core/default-application.mk
– kris
Oct 27 at 5:56
add a comment |
I have faced the same problem while update Android studio from 2.0 to 2.1 in my Windows 8 machine.
I found a solution for that.Please use the following steps.
- Download the android NDK for windows from https://developer.android.com/ndk/downloads/index.html.
- Extract the same and copy the "toolchain" folder from the bundle.
- Paste the folder under installed NDK folder under C:android-sdk-winndk-bundle.[Installed the path may vary based on your installation]
- Restart android studio.
This is happening because Android studio won't gets full NDK update in the stable channel. If you are not using NDK for your project development you can simply remove the NDK folder from your SDK directory.
1
Thanks it works in Windows 10 too!
– Ciro Mine
Sep 20 at 14:21
1
Works with Android Studio 3.2!
– maxwellnewage
Oct 2 at 15:13
1
This also worked for me for fixing the error "Error : Android MIPS ToolChain directory "" does not exist" in Game Maker Studio 2 on a Mac. But I needed to get version 17c of the NDK from here : developer.android.com/ndk/downloads/older_releases (as per: reddit.com/r/gamemaker/comments/9m958a/…) Thank You @nithinjith ! ... still not building however, need to solve :Android NDK: Please fix the APP_ABI definition in /Users/../Library/Android/sdk/ndk-bundle/build/core/default-application.mk
– kris
Oct 27 at 5:56
add a comment |
I have faced the same problem while update Android studio from 2.0 to 2.1 in my Windows 8 machine.
I found a solution for that.Please use the following steps.
- Download the android NDK for windows from https://developer.android.com/ndk/downloads/index.html.
- Extract the same and copy the "toolchain" folder from the bundle.
- Paste the folder under installed NDK folder under C:android-sdk-winndk-bundle.[Installed the path may vary based on your installation]
- Restart android studio.
This is happening because Android studio won't gets full NDK update in the stable channel. If you are not using NDK for your project development you can simply remove the NDK folder from your SDK directory.
I have faced the same problem while update Android studio from 2.0 to 2.1 in my Windows 8 machine.
I found a solution for that.Please use the following steps.
- Download the android NDK for windows from https://developer.android.com/ndk/downloads/index.html.
- Extract the same and copy the "toolchain" folder from the bundle.
- Paste the folder under installed NDK folder under C:android-sdk-winndk-bundle.[Installed the path may vary based on your installation]
- Restart android studio.
This is happening because Android studio won't gets full NDK update in the stable channel. If you are not using NDK for your project development you can simply remove the NDK folder from your SDK directory.
edited Aug 24 '16 at 5:33
answered Jul 11 '16 at 12:02
Nithinjith
1,048921
1,048921
1
Thanks it works in Windows 10 too!
– Ciro Mine
Sep 20 at 14:21
1
Works with Android Studio 3.2!
– maxwellnewage
Oct 2 at 15:13
1
This also worked for me for fixing the error "Error : Android MIPS ToolChain directory "" does not exist" in Game Maker Studio 2 on a Mac. But I needed to get version 17c of the NDK from here : developer.android.com/ndk/downloads/older_releases (as per: reddit.com/r/gamemaker/comments/9m958a/…) Thank You @nithinjith ! ... still not building however, need to solve :Android NDK: Please fix the APP_ABI definition in /Users/../Library/Android/sdk/ndk-bundle/build/core/default-application.mk
– kris
Oct 27 at 5:56
add a comment |
1
Thanks it works in Windows 10 too!
– Ciro Mine
Sep 20 at 14:21
1
Works with Android Studio 3.2!
– maxwellnewage
Oct 2 at 15:13
1
This also worked for me for fixing the error "Error : Android MIPS ToolChain directory "" does not exist" in Game Maker Studio 2 on a Mac. But I needed to get version 17c of the NDK from here : developer.android.com/ndk/downloads/older_releases (as per: reddit.com/r/gamemaker/comments/9m958a/…) Thank You @nithinjith ! ... still not building however, need to solve :Android NDK: Please fix the APP_ABI definition in /Users/../Library/Android/sdk/ndk-bundle/build/core/default-application.mk
– kris
Oct 27 at 5:56
1
1
Thanks it works in Windows 10 too!
– Ciro Mine
Sep 20 at 14:21
Thanks it works in Windows 10 too!
– Ciro Mine
Sep 20 at 14:21
1
1
Works with Android Studio 3.2!
– maxwellnewage
Oct 2 at 15:13
Works with Android Studio 3.2!
– maxwellnewage
Oct 2 at 15:13
1
1
This also worked for me for fixing the error "
Error : Android MIPS ToolChain directory "" does not exist" in Game Maker Studio 2 on a Mac. But I needed to get version 17c of the NDK from here : developer.android.com/ndk/downloads/older_releases (as per: reddit.com/r/gamemaker/comments/9m958a/…) Thank You @nithinjith ! ... still not building however, need to solve : Android NDK: Please fix the APP_ABI definition in /Users/../Library/Android/sdk/ndk-bundle/build/core/default-application.mk – kris
Oct 27 at 5:56
This also worked for me for fixing the error "
Error : Android MIPS ToolChain directory "" does not exist" in Game Maker Studio 2 on a Mac. But I needed to get version 17c of the NDK from here : developer.android.com/ndk/downloads/older_releases (as per: reddit.com/r/gamemaker/comments/9m958a/…) Thank You @nithinjith ! ... still not building however, need to solve : Android NDK: Please fix the APP_ABI definition in /Users/../Library/Android/sdk/ndk-bundle/build/core/default-application.mk – kris
Oct 27 at 5:56
add a comment |
For Android studio 3.2.1+
Upgrade your Gradle Plugin
classpath 'com.android.tools.build:gradle:3.2.1'
and see the Magic Error gone.
Happy Coding -:)
add a comment |
For Android studio 3.2.1+
Upgrade your Gradle Plugin
classpath 'com.android.tools.build:gradle:3.2.1'
and see the Magic Error gone.
Happy Coding -:)
add a comment |
For Android studio 3.2.1+
Upgrade your Gradle Plugin
classpath 'com.android.tools.build:gradle:3.2.1'
and see the Magic Error gone.
Happy Coding -:)
For Android studio 3.2.1+
Upgrade your Gradle Plugin
classpath 'com.android.tools.build:gradle:3.2.1'
and see the Magic Error gone.
Happy Coding -:)
edited Dec 1 at 8:33
answered Oct 20 at 6:28
Nikunj Paradva
2,24421426
2,24421426
add a comment |
add a comment |
Error message: “No toolchains found in the NDK toolchains folder for ABI with prefix: llvm” .
After fresh web installation of Android Studio with NDK, I imported an Android code sample that used NDK from GitHub and tried to compile it.
As a result had an Error:
No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
Solution:
for some reasons standard installation process on macOS had failed to install a complete set:
~/Library/Android/sdk/ndk-bundle had missed folder toolchains with all tools,
(it should be like this: ~/Library/Android/sdk/ndk-bundle/toolchains)
The solution was to download NDK separately, open it, copy folder toolchain and paste it to the folder:
~/Library/Android/sdk/ndk-bundle
After that it worked well for me.
2
It worked for me!
– Thinsky
Aug 24 '16 at 1:57
in my case it's there but no file there with prefix aarch64-linux-android. Any suggestion !!
– CoDe
Jul 28 '17 at 3:17
folder 'mips64el-linux-android-4.9' & 'mipsel-linux-android-4.9' are not available after ndk bundle 16, so i have to download and add these two folder in android sdk bundle inside toolchains folder hence issue solved, still didn't understand why this error?
– Fazal
Oct 29 at 8:42
add a comment |
Error message: “No toolchains found in the NDK toolchains folder for ABI with prefix: llvm” .
After fresh web installation of Android Studio with NDK, I imported an Android code sample that used NDK from GitHub and tried to compile it.
As a result had an Error:
No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
Solution:
for some reasons standard installation process on macOS had failed to install a complete set:
~/Library/Android/sdk/ndk-bundle had missed folder toolchains with all tools,
(it should be like this: ~/Library/Android/sdk/ndk-bundle/toolchains)
The solution was to download NDK separately, open it, copy folder toolchain and paste it to the folder:
~/Library/Android/sdk/ndk-bundle
After that it worked well for me.
2
It worked for me!
– Thinsky
Aug 24 '16 at 1:57
in my case it's there but no file there with prefix aarch64-linux-android. Any suggestion !!
– CoDe
Jul 28 '17 at 3:17
folder 'mips64el-linux-android-4.9' & 'mipsel-linux-android-4.9' are not available after ndk bundle 16, so i have to download and add these two folder in android sdk bundle inside toolchains folder hence issue solved, still didn't understand why this error?
– Fazal
Oct 29 at 8:42
add a comment |
Error message: “No toolchains found in the NDK toolchains folder for ABI with prefix: llvm” .
After fresh web installation of Android Studio with NDK, I imported an Android code sample that used NDK from GitHub and tried to compile it.
As a result had an Error:
No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
Solution:
for some reasons standard installation process on macOS had failed to install a complete set:
~/Library/Android/sdk/ndk-bundle had missed folder toolchains with all tools,
(it should be like this: ~/Library/Android/sdk/ndk-bundle/toolchains)
The solution was to download NDK separately, open it, copy folder toolchain and paste it to the folder:
~/Library/Android/sdk/ndk-bundle
After that it worked well for me.
Error message: “No toolchains found in the NDK toolchains folder for ABI with prefix: llvm” .
After fresh web installation of Android Studio with NDK, I imported an Android code sample that used NDK from GitHub and tried to compile it.
As a result had an Error:
No toolchains found in the NDK toolchains folder for ABI with prefix: llvm
Solution:
for some reasons standard installation process on macOS had failed to install a complete set:
~/Library/Android/sdk/ndk-bundle had missed folder toolchains with all tools,
(it should be like this: ~/Library/Android/sdk/ndk-bundle/toolchains)
The solution was to download NDK separately, open it, copy folder toolchain and paste it to the folder:
~/Library/Android/sdk/ndk-bundle
After that it worked well for me.
edited Oct 1 at 5:38
James T Snell
6091719
6091719
answered Jun 5 '16 at 19:39
user6427706
2
It worked for me!
– Thinsky
Aug 24 '16 at 1:57
in my case it's there but no file there with prefix aarch64-linux-android. Any suggestion !!
– CoDe
Jul 28 '17 at 3:17
folder 'mips64el-linux-android-4.9' & 'mipsel-linux-android-4.9' are not available after ndk bundle 16, so i have to download and add these two folder in android sdk bundle inside toolchains folder hence issue solved, still didn't understand why this error?
– Fazal
Oct 29 at 8:42
add a comment |
2
It worked for me!
– Thinsky
Aug 24 '16 at 1:57
in my case it's there but no file there with prefix aarch64-linux-android. Any suggestion !!
– CoDe
Jul 28 '17 at 3:17
folder 'mips64el-linux-android-4.9' & 'mipsel-linux-android-4.9' are not available after ndk bundle 16, so i have to download and add these two folder in android sdk bundle inside toolchains folder hence issue solved, still didn't understand why this error?
– Fazal
Oct 29 at 8:42
2
2
It worked for me!
– Thinsky
Aug 24 '16 at 1:57
It worked for me!
– Thinsky
Aug 24 '16 at 1:57
in my case it's there but no file there with prefix aarch64-linux-android. Any suggestion !!
– CoDe
Jul 28 '17 at 3:17
in my case it's there but no file there with prefix aarch64-linux-android. Any suggestion !!
– CoDe
Jul 28 '17 at 3:17
folder 'mips64el-linux-android-4.9' & 'mipsel-linux-android-4.9' are not available after ndk bundle 16, so i have to download and add these two folder in android sdk bundle inside toolchains folder hence issue solved, still didn't understand why this error?
– Fazal
Oct 29 at 8:42
folder 'mips64el-linux-android-4.9' & 'mipsel-linux-android-4.9' are not available after ndk bundle 16, so i have to download and add these two folder in android sdk bundle inside toolchains folder hence issue solved, still didn't understand why this error?
– Fazal
Oct 29 at 8:42
add a comment |
Step-by-step:
1) Open the page with old NDK versions:
https://developer.android.com/ndk/downloads/older_releases

2) Agree the Terms:

3) Download the older version of NDK (for example 16b):

4) Open your toolchains directory.
5) Transfer files that you need from toolchains folder of downloaded zip-file to your toolchains folder:

6) Rebuild the Project:

UPD 30 Sep 2018:
I used Android NDK Revision r16b for fix this error in my own case. So I present the example with this version.
But it's better to use the Android NDK, Revision r17c (June 2018). It is the last one, supporting mips (reasonable reccomendation from Weekend's comment).
Instead of(for example 16b), it's better to clarify which NDK version is the last one supporting mips. via release note of Android NDK Revision r17c (June 2018): Support for ARMv5 (armeabi), MIPS, and MIPS64 has been removed. Attempting to build any of these ABIs will result in an error. It's16bexactly.
– Weekend
Sep 30 at 6:02
@Weekend Thanks for your recommendation. I added it to my answer.
– V.March
Sep 30 at 19:37
@vmarch Sorry but It's16bexactly. r17c is the first version which removed the support for MIPS :)
– Weekend
Oct 8 at 7:10
1
@Oh, I read your previous comment so very quickly. That's why I missed the point. My apologize! But these files are still present in the Android NDK, Revision r17c (June 2018). And in version 18 they were finally removed. Just look into the archive. developer.android.com/ndk/downloads/…
– V.March
Oct 8 at 14:15
@vmarch Well done! I didn't check r17c archive, just inferred the previous conclusion from release notes.
– Weekend
Oct 9 at 2:03
|
show 1 more comment
Step-by-step:
1) Open the page with old NDK versions:
https://developer.android.com/ndk/downloads/older_releases

2) Agree the Terms:

3) Download the older version of NDK (for example 16b):

4) Open your toolchains directory.
5) Transfer files that you need from toolchains folder of downloaded zip-file to your toolchains folder:

6) Rebuild the Project:

UPD 30 Sep 2018:
I used Android NDK Revision r16b for fix this error in my own case. So I present the example with this version.
But it's better to use the Android NDK, Revision r17c (June 2018). It is the last one, supporting mips (reasonable reccomendation from Weekend's comment).
Instead of(for example 16b), it's better to clarify which NDK version is the last one supporting mips. via release note of Android NDK Revision r17c (June 2018): Support for ARMv5 (armeabi), MIPS, and MIPS64 has been removed. Attempting to build any of these ABIs will result in an error. It's16bexactly.
– Weekend
Sep 30 at 6:02
@Weekend Thanks for your recommendation. I added it to my answer.
– V.March
Sep 30 at 19:37
@vmarch Sorry but It's16bexactly. r17c is the first version which removed the support for MIPS :)
– Weekend
Oct 8 at 7:10
1
@Oh, I read your previous comment so very quickly. That's why I missed the point. My apologize! But these files are still present in the Android NDK, Revision r17c (June 2018). And in version 18 they were finally removed. Just look into the archive. developer.android.com/ndk/downloads/…
– V.March
Oct 8 at 14:15
@vmarch Well done! I didn't check r17c archive, just inferred the previous conclusion from release notes.
– Weekend
Oct 9 at 2:03
|
show 1 more comment
Step-by-step:
1) Open the page with old NDK versions:
https://developer.android.com/ndk/downloads/older_releases

2) Agree the Terms:

3) Download the older version of NDK (for example 16b):

4) Open your toolchains directory.
5) Transfer files that you need from toolchains folder of downloaded zip-file to your toolchains folder:

6) Rebuild the Project:

UPD 30 Sep 2018:
I used Android NDK Revision r16b for fix this error in my own case. So I present the example with this version.
But it's better to use the Android NDK, Revision r17c (June 2018). It is the last one, supporting mips (reasonable reccomendation from Weekend's comment).
Step-by-step:
1) Open the page with old NDK versions:
https://developer.android.com/ndk/downloads/older_releases

2) Agree the Terms:

3) Download the older version of NDK (for example 16b):

4) Open your toolchains directory.
5) Transfer files that you need from toolchains folder of downloaded zip-file to your toolchains folder:

6) Rebuild the Project:

UPD 30 Sep 2018:
I used Android NDK Revision r16b for fix this error in my own case. So I present the example with this version.
But it's better to use the Android NDK, Revision r17c (June 2018). It is the last one, supporting mips (reasonable reccomendation from Weekend's comment).
edited Sep 30 at 19:33
answered Sep 22 at 8:16
V.March
8501618
8501618
Instead of(for example 16b), it's better to clarify which NDK version is the last one supporting mips. via release note of Android NDK Revision r17c (June 2018): Support for ARMv5 (armeabi), MIPS, and MIPS64 has been removed. Attempting to build any of these ABIs will result in an error. It's16bexactly.
– Weekend
Sep 30 at 6:02
@Weekend Thanks for your recommendation. I added it to my answer.
– V.March
Sep 30 at 19:37
@vmarch Sorry but It's16bexactly. r17c is the first version which removed the support for MIPS :)
– Weekend
Oct 8 at 7:10
1
@Oh, I read your previous comment so very quickly. That's why I missed the point. My apologize! But these files are still present in the Android NDK, Revision r17c (June 2018). And in version 18 they were finally removed. Just look into the archive. developer.android.com/ndk/downloads/…
– V.March
Oct 8 at 14:15
@vmarch Well done! I didn't check r17c archive, just inferred the previous conclusion from release notes.
– Weekend
Oct 9 at 2:03
|
show 1 more comment
Instead of(for example 16b), it's better to clarify which NDK version is the last one supporting mips. via release note of Android NDK Revision r17c (June 2018): Support for ARMv5 (armeabi), MIPS, and MIPS64 has been removed. Attempting to build any of these ABIs will result in an error. It's16bexactly.
– Weekend
Sep 30 at 6:02
@Weekend Thanks for your recommendation. I added it to my answer.
– V.March
Sep 30 at 19:37
@vmarch Sorry but It's16bexactly. r17c is the first version which removed the support for MIPS :)
– Weekend
Oct 8 at 7:10
1
@Oh, I read your previous comment so very quickly. That's why I missed the point. My apologize! But these files are still present in the Android NDK, Revision r17c (June 2018). And in version 18 they were finally removed. Just look into the archive. developer.android.com/ndk/downloads/…
– V.March
Oct 8 at 14:15
@vmarch Well done! I didn't check r17c archive, just inferred the previous conclusion from release notes.
– Weekend
Oct 9 at 2:03
Instead of
(for example 16b), it's better to clarify which NDK version is the last one supporting mips. via release note of Android NDK Revision r17c (June 2018): Support for ARMv5 (armeabi), MIPS, and MIPS64 has been removed. Attempting to build any of these ABIs will result in an error. It's 16b exactly.– Weekend
Sep 30 at 6:02
Instead of
(for example 16b), it's better to clarify which NDK version is the last one supporting mips. via release note of Android NDK Revision r17c (June 2018): Support for ARMv5 (armeabi), MIPS, and MIPS64 has been removed. Attempting to build any of these ABIs will result in an error. It's 16b exactly.– Weekend
Sep 30 at 6:02
@Weekend Thanks for your recommendation. I added it to my answer.
– V.March
Sep 30 at 19:37
@Weekend Thanks for your recommendation. I added it to my answer.
– V.March
Sep 30 at 19:37
@vmarch Sorry but It's
16b exactly. r17c is the first version which removed the support for MIPS :)– Weekend
Oct 8 at 7:10
@vmarch Sorry but It's
16b exactly. r17c is the first version which removed the support for MIPS :)– Weekend
Oct 8 at 7:10
1
1
@Oh, I read your previous comment so very quickly. That's why I missed the point. My apologize! But these files are still present in the Android NDK, Revision r17c (June 2018). And in version 18 they were finally removed. Just look into the archive. developer.android.com/ndk/downloads/…
– V.March
Oct 8 at 14:15
@Oh, I read your previous comment so very quickly. That's why I missed the point. My apologize! But these files are still present in the Android NDK, Revision r17c (June 2018). And in version 18 they were finally removed. Just look into the archive. developer.android.com/ndk/downloads/…
– V.March
Oct 8 at 14:15
@vmarch Well done! I didn't check r17c archive, just inferred the previous conclusion from release notes.
– Weekend
Oct 9 at 2:03
@vmarch Well done! I didn't check r17c archive, just inferred the previous conclusion from release notes.
– Weekend
Oct 9 at 2:03
|
show 1 more comment
Without downloading, copying, or symlinking anything, I was able to "fix" the error by simply creating an empty directory where the older version of the Android Gradle plugin expects the removed mips toolchain:
mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/linux-x86_64
Obviously, $ANDROID_HOME points to the root of the Android SDK installation here. If you are using MacOS, replace linux-x86_64 with darwin-x86_64 in the command above. On Windows use windows-x86_64.
Worked like charm.
– Akbar Sha Ebrahim
Oct 10 at 12:17
Worked for me in Linux. dint work in mac
– Jay
Oct 15 at 10:00
add a comment |
Without downloading, copying, or symlinking anything, I was able to "fix" the error by simply creating an empty directory where the older version of the Android Gradle plugin expects the removed mips toolchain:
mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/linux-x86_64
Obviously, $ANDROID_HOME points to the root of the Android SDK installation here. If you are using MacOS, replace linux-x86_64 with darwin-x86_64 in the command above. On Windows use windows-x86_64.
Worked like charm.
– Akbar Sha Ebrahim
Oct 10 at 12:17
Worked for me in Linux. dint work in mac
– Jay
Oct 15 at 10:00
add a comment |
Without downloading, copying, or symlinking anything, I was able to "fix" the error by simply creating an empty directory where the older version of the Android Gradle plugin expects the removed mips toolchain:
mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/linux-x86_64
Obviously, $ANDROID_HOME points to the root of the Android SDK installation here. If you are using MacOS, replace linux-x86_64 with darwin-x86_64 in the command above. On Windows use windows-x86_64.
Without downloading, copying, or symlinking anything, I was able to "fix" the error by simply creating an empty directory where the older version of the Android Gradle plugin expects the removed mips toolchain:
mkdir -p $ANDROID_HOME/ndk-bundle/toolchains/mips64el-linux-android/prebuilt/linux-x86_64
Obviously, $ANDROID_HOME points to the root of the Android SDK installation here. If you are using MacOS, replace linux-x86_64 with darwin-x86_64 in the command above. On Windows use windows-x86_64.
answered Oct 2 at 12:51
friederbluemle
9,23955469
9,23955469
Worked like charm.
– Akbar Sha Ebrahim
Oct 10 at 12:17
Worked for me in Linux. dint work in mac
– Jay
Oct 15 at 10:00
add a comment |
Worked like charm.
– Akbar Sha Ebrahim
Oct 10 at 12:17
Worked for me in Linux. dint work in mac
– Jay
Oct 15 at 10:00
Worked like charm.
– Akbar Sha Ebrahim
Oct 10 at 12:17
Worked like charm.
– Akbar Sha Ebrahim
Oct 10 at 12:17
Worked for me in Linux. dint work in mac
– Jay
Oct 15 at 10:00
Worked for me in Linux. dint work in mac
– Jay
Oct 15 at 10:00
add a comment |
I uninstalled the NDK since I didn't need it . Go to SDK manager on Android studio ( Tools -> Android -> SDK Manager ) . If NDK is installed . Just uncheck the box and click OK . The installed components will be deleted .
add a comment |
I uninstalled the NDK since I didn't need it . Go to SDK manager on Android studio ( Tools -> Android -> SDK Manager ) . If NDK is installed . Just uncheck the box and click OK . The installed components will be deleted .
add a comment |
I uninstalled the NDK since I didn't need it . Go to SDK manager on Android studio ( Tools -> Android -> SDK Manager ) . If NDK is installed . Just uncheck the box and click OK . The installed components will be deleted .
I uninstalled the NDK since I didn't need it . Go to SDK manager on Android studio ( Tools -> Android -> SDK Manager ) . If NDK is installed . Just uncheck the box and click OK . The installed components will be deleted .
answered May 24 '16 at 9:38
diptia
1,4181318
1,4181318
add a comment |
add a comment |
In my case, this error occured when creating a new Android Studio (Android studio 3.2.1) Java Project with
classpath 'com.android.tools.build:gradle:2.0.0-beta6'
So I´ve downgraded to
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
Not the best solution stay at an older version, but maybe it´s just a temporary bug in the beta as the NDK path in local.properties is still the same, but the IDE doesn´t complain anymore
I think this is a bug of outdated gradle plugin. Just update to the latest one. It helped to me (from 3.0 to 3.2.0-beta05 in my case)
– AnoDest
Aug 17 at 11:56
add a comment |
In my case, this error occured when creating a new Android Studio (Android studio 3.2.1) Java Project with
classpath 'com.android.tools.build:gradle:2.0.0-beta6'
So I´ve downgraded to
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
Not the best solution stay at an older version, but maybe it´s just a temporary bug in the beta as the NDK path in local.properties is still the same, but the IDE doesn´t complain anymore
I think this is a bug of outdated gradle plugin. Just update to the latest one. It helped to me (from 3.0 to 3.2.0-beta05 in my case)
– AnoDest
Aug 17 at 11:56
add a comment |
In my case, this error occured when creating a new Android Studio (Android studio 3.2.1) Java Project with
classpath 'com.android.tools.build:gradle:2.0.0-beta6'
So I´ve downgraded to
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
Not the best solution stay at an older version, but maybe it´s just a temporary bug in the beta as the NDK path in local.properties is still the same, but the IDE doesn´t complain anymore
In my case, this error occured when creating a new Android Studio (Android studio 3.2.1) Java Project with
classpath 'com.android.tools.build:gradle:2.0.0-beta6'
So I´ve downgraded to
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
Not the best solution stay at an older version, but maybe it´s just a temporary bug in the beta as the NDK path in local.properties is still the same, but the IDE doesn´t complain anymore
edited Oct 30 at 7:23
Shomu
382213
382213
answered Mar 13 '16 at 11:20
Marian Klühspies
5,96685382
5,96685382
I think this is a bug of outdated gradle plugin. Just update to the latest one. It helped to me (from 3.0 to 3.2.0-beta05 in my case)
– AnoDest
Aug 17 at 11:56
add a comment |
I think this is a bug of outdated gradle plugin. Just update to the latest one. It helped to me (from 3.0 to 3.2.0-beta05 in my case)
– AnoDest
Aug 17 at 11:56
I think this is a bug of outdated gradle plugin. Just update to the latest one. It helped to me (from 3.0 to 3.2.0-beta05 in my case)
– AnoDest
Aug 17 at 11:56
I think this is a bug of outdated gradle plugin. Just update to the latest one. It helped to me (from 3.0 to 3.2.0-beta05 in my case)
– AnoDest
Aug 17 at 11:56
add a comment |
Android NDK 18.0* seems has an issue not creating all the files in folders after extraction. Due to it, your app compilation will fail which uses ndk builds.
Better is to use NDK 17.1* (https://developer.android.com/ndk/downloads/) etc version and you can extract or use the android studio extraction to ndk-bundle by default will work good.
add a comment |
Android NDK 18.0* seems has an issue not creating all the files in folders after extraction. Due to it, your app compilation will fail which uses ndk builds.
Better is to use NDK 17.1* (https://developer.android.com/ndk/downloads/) etc version and you can extract or use the android studio extraction to ndk-bundle by default will work good.
add a comment |
Android NDK 18.0* seems has an issue not creating all the files in folders after extraction. Due to it, your app compilation will fail which uses ndk builds.
Better is to use NDK 17.1* (https://developer.android.com/ndk/downloads/) etc version and you can extract or use the android studio extraction to ndk-bundle by default will work good.
Android NDK 18.0* seems has an issue not creating all the files in folders after extraction. Due to it, your app compilation will fail which uses ndk builds.
Better is to use NDK 17.1* (https://developer.android.com/ndk/downloads/) etc version and you can extract or use the android studio extraction to ndk-bundle by default will work good.
edited Jul 30 at 10:53
answered Jul 30 at 7:58
appapurapu
43866
43866
add a comment |
add a comment |
Open Android Studio, Go to Tools then Android and then SDK, uncheck NDK If you do not need this, and restart android studio.
2
Thank you. It worked well for Unity.
– Carson
Oct 10 at 16:14
Great thank. It worked for my Unity project
– Leo Nguyen
Oct 22 at 8:47
add a comment |
Open Android Studio, Go to Tools then Android and then SDK, uncheck NDK If you do not need this, and restart android studio.
2
Thank you. It worked well for Unity.
– Carson
Oct 10 at 16:14
Great thank. It worked for my Unity project
– Leo Nguyen
Oct 22 at 8:47
add a comment |
Open Android Studio, Go to Tools then Android and then SDK, uncheck NDK If you do not need this, and restart android studio.
Open Android Studio, Go to Tools then Android and then SDK, uncheck NDK If you do not need this, and restart android studio.
answered Oct 8 at 9:31
Muhammad Bilal
18729
18729
2
Thank you. It worked well for Unity.
– Carson
Oct 10 at 16:14
Great thank. It worked for my Unity project
– Leo Nguyen
Oct 22 at 8:47
add a comment |
2
Thank you. It worked well for Unity.
– Carson
Oct 10 at 16:14
Great thank. It worked for my Unity project
– Leo Nguyen
Oct 22 at 8:47
2
2
Thank you. It worked well for Unity.
– Carson
Oct 10 at 16:14
Thank you. It worked well for Unity.
– Carson
Oct 10 at 16:14
Great thank. It worked for my Unity project
– Leo Nguyen
Oct 22 at 8:47
Great thank. It worked for my Unity project
– Leo Nguyen
Oct 22 at 8:47
add a comment |
In your project level Gradle file increase the dependencies
classpath version low to high like
dependencies {
classpath 'com.android.tools.build:gradle:3.0.0'
}
to change like
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
add a comment |
In your project level Gradle file increase the dependencies
classpath version low to high like
dependencies {
classpath 'com.android.tools.build:gradle:3.0.0'
}
to change like
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
add a comment |
In your project level Gradle file increase the dependencies
classpath version low to high like
dependencies {
classpath 'com.android.tools.build:gradle:3.0.0'
}
to change like
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
In your project level Gradle file increase the dependencies
classpath version low to high like
dependencies {
classpath 'com.android.tools.build:gradle:3.0.0'
}
to change like
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
}
answered Nov 8 at 14:25
Karthikrider
313
313
add a comment |
add a comment |
Find your own local android-SDK, if you download the relevant SDK of ndk, there will be a folder called "ndk-bundle"

There is a folder called "toolchains" inside.

We noticed that there are no mips64el related files inside.

The solution is as follows:
Click here to download the NDK package separately through the browser.
After unzipping, open the "toolchains" folder, compare it with the android-sdk->ndk-bundle->toolchains folder, find the missing folder, copy the past
3. Recompile, the problem is solved.
Hope it helps you mate
add a comment |
Find your own local android-SDK, if you download the relevant SDK of ndk, there will be a folder called "ndk-bundle"

There is a folder called "toolchains" inside.

We noticed that there are no mips64el related files inside.

The solution is as follows:
Click here to download the NDK package separately through the browser.
After unzipping, open the "toolchains" folder, compare it with the android-sdk->ndk-bundle->toolchains folder, find the missing folder, copy the past
3. Recompile, the problem is solved.
Hope it helps you mate
add a comment |
Find your own local android-SDK, if you download the relevant SDK of ndk, there will be a folder called "ndk-bundle"

There is a folder called "toolchains" inside.

We noticed that there are no mips64el related files inside.

The solution is as follows:
Click here to download the NDK package separately through the browser.
After unzipping, open the "toolchains" folder, compare it with the android-sdk->ndk-bundle->toolchains folder, find the missing folder, copy the past
3. Recompile, the problem is solved.
Hope it helps you mate
Find your own local android-SDK, if you download the relevant SDK of ndk, there will be a folder called "ndk-bundle"

There is a folder called "toolchains" inside.

We noticed that there are no mips64el related files inside.

The solution is as follows:
Click here to download the NDK package separately through the browser.
After unzipping, open the "toolchains" folder, compare it with the android-sdk->ndk-bundle->toolchains folder, find the missing folder, copy the past
3. Recompile, the problem is solved.
Hope it helps you mate
answered Dec 15 at 9:10
D Prince
728317
728317
add a comment |
add a comment |
I've had a similar problem, but I wanted to use NDK version r9d due to project requirements.
In local.properties the path was set to ndk.dir=C:\Android\ndk\android-ndk-r9d but that lead to the problem:
No toolchains found in the NDK toolchains folder for ABI with prefix: [toolchain-name]
The solution was to:
- Install the newest NDK using sdk manager
- Copy the missing toolchain [toolchain-name] from the new ndk to the old. In my case from
sdkndk-bundletoolchainstondkandroid-ndk-r9dtoolchains
- Repeat the process till all the required toolchains are there
It looks to me that the copied toolchains are not used, but for some reason it is needed to for them be there.
add a comment |
I've had a similar problem, but I wanted to use NDK version r9d due to project requirements.
In local.properties the path was set to ndk.dir=C:\Android\ndk\android-ndk-r9d but that lead to the problem:
No toolchains found in the NDK toolchains folder for ABI with prefix: [toolchain-name]
The solution was to:
- Install the newest NDK using sdk manager
- Copy the missing toolchain [toolchain-name] from the new ndk to the old. In my case from
sdkndk-bundletoolchainstondkandroid-ndk-r9dtoolchains
- Repeat the process till all the required toolchains are there
It looks to me that the copied toolchains are not used, but for some reason it is needed to for them be there.
add a comment |
I've had a similar problem, but I wanted to use NDK version r9d due to project requirements.
In local.properties the path was set to ndk.dir=C:\Android\ndk\android-ndk-r9d but that lead to the problem:
No toolchains found in the NDK toolchains folder for ABI with prefix: [toolchain-name]
The solution was to:
- Install the newest NDK using sdk manager
- Copy the missing toolchain [toolchain-name] from the new ndk to the old. In my case from
sdkndk-bundletoolchainstondkandroid-ndk-r9dtoolchains
- Repeat the process till all the required toolchains are there
It looks to me that the copied toolchains are not used, but for some reason it is needed to for them be there.
I've had a similar problem, but I wanted to use NDK version r9d due to project requirements.
In local.properties the path was set to ndk.dir=C:\Android\ndk\android-ndk-r9d but that lead to the problem:
No toolchains found in the NDK toolchains folder for ABI with prefix: [toolchain-name]
The solution was to:
- Install the newest NDK using sdk manager
- Copy the missing toolchain [toolchain-name] from the new ndk to the old. In my case from
sdkndk-bundletoolchainstondkandroid-ndk-r9dtoolchains
- Repeat the process till all the required toolchains are there
It looks to me that the copied toolchains are not used, but for some reason it is needed to for them be there.
edited Mar 23 '17 at 11:54
answered Mar 23 '17 at 11:30
Marcin Kunert
1,26011231
1,26011231
add a comment |
add a comment |
I solved this question by unInstalled ndk, becasuse I dont't need it
add a comment |
I solved this question by unInstalled ndk, becasuse I dont't need it
add a comment |
I solved this question by unInstalled ndk, becasuse I dont't need it
I solved this question by unInstalled ndk, becasuse I dont't need it
answered May 10 at 6:20
alpha
467
467
add a comment |
add a comment |
Here is the fix.
When compiling a project in android studio, I occasionally encounter:
Error: No toolchains found in the NDK toolchains folder for ABI with
prefix: arm-linux-androideabi/llvm
This may be caused by updating related components. The solution is to Android studio ( Tools -> Android -> SDK Manager ) .
Select the ndk item and delete it. If the program needs it, you can re-install it. This will ensure that the folder location is correct and there will be no such problem.
add a comment |
Here is the fix.
When compiling a project in android studio, I occasionally encounter:
Error: No toolchains found in the NDK toolchains folder for ABI with
prefix: arm-linux-androideabi/llvm
This may be caused by updating related components. The solution is to Android studio ( Tools -> Android -> SDK Manager ) .
Select the ndk item and delete it. If the program needs it, you can re-install it. This will ensure that the folder location is correct and there will be no such problem.
add a comment |
Here is the fix.
When compiling a project in android studio, I occasionally encounter:
Error: No toolchains found in the NDK toolchains folder for ABI with
prefix: arm-linux-androideabi/llvm
This may be caused by updating related components. The solution is to Android studio ( Tools -> Android -> SDK Manager ) .
Select the ndk item and delete it. If the program needs it, you can re-install it. This will ensure that the folder location is correct and there will be no such problem.
Here is the fix.
When compiling a project in android studio, I occasionally encounter:
Error: No toolchains found in the NDK toolchains folder for ABI with
prefix: arm-linux-androideabi/llvm
This may be caused by updating related components. The solution is to Android studio ( Tools -> Android -> SDK Manager ) .
Select the ndk item and delete it. If the program needs it, you can re-install it. This will ensure that the folder location is correct and there will be no such problem.
answered Aug 1 at 8:03
0xalihn
5,783103769
5,783103769
add a comment |
add a comment |
Solved it by adding google() dependency into both repositories in build.gradle(Project: ProjectName). then sync your project
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.3.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
add a comment |
Solved it by adding google() dependency into both repositories in build.gradle(Project: ProjectName). then sync your project
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.3.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
add a comment |
Solved it by adding google() dependency into both repositories in build.gradle(Project: ProjectName). then sync your project
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.3.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
Solved it by adding google() dependency into both repositories in build.gradle(Project: ProjectName). then sync your project
buildscript {
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.3.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
edited Nov 21 at 0:58
shizhen
2,6393728
2,6393728
answered Oct 19 at 19:19
M.Zain
13114
13114
add a comment |
add a comment |
For me I think there might be some issue in installing android NDK from android studio. I was able to resolve this in following manner
Downloaded android ndk from
https://developer.android.com/ndk/downloads/index.html
and placed inside ndk-bundle (where your android sdk is installed ). For more info check this screens.
https://app.box.com/s/dfi4h9k7v4h0tmbu3z9qnqx3d12fdejn
add a comment |
For me I think there might be some issue in installing android NDK from android studio. I was able to resolve this in following manner
Downloaded android ndk from
https://developer.android.com/ndk/downloads/index.html
and placed inside ndk-bundle (where your android sdk is installed ). For more info check this screens.
https://app.box.com/s/dfi4h9k7v4h0tmbu3z9qnqx3d12fdejn
add a comment |
For me I think there might be some issue in installing android NDK from android studio. I was able to resolve this in following manner
Downloaded android ndk from
https://developer.android.com/ndk/downloads/index.html
and placed inside ndk-bundle (where your android sdk is installed ). For more info check this screens.
https://app.box.com/s/dfi4h9k7v4h0tmbu3z9qnqx3d12fdejn
For me I think there might be some issue in installing android NDK from android studio. I was able to resolve this in following manner
Downloaded android ndk from
https://developer.android.com/ndk/downloads/index.html
and placed inside ndk-bundle (where your android sdk is installed ). For more info check this screens.
https://app.box.com/s/dfi4h9k7v4h0tmbu3z9qnqx3d12fdejn
edited Aug 24 at 13:32
answered Feb 22 '17 at 17:24
Chirag Purohit
453811
453811
add a comment |
add a comment |
If you are using Ionic 3 Remove ndk from android studio sdk tools.
Great, as a temporary solution for the specific need of building ionic android projects, although is not ideal.
– MFAL
Oct 12 at 8:12
add a comment |
If you are using Ionic 3 Remove ndk from android studio sdk tools.
Great, as a temporary solution for the specific need of building ionic android projects, although is not ideal.
– MFAL
Oct 12 at 8:12
add a comment |
If you are using Ionic 3 Remove ndk from android studio sdk tools.
If you are using Ionic 3 Remove ndk from android studio sdk tools.
answered Sep 30 at 8:40
Taimoor Tariq
393
393
Great, as a temporary solution for the specific need of building ionic android projects, although is not ideal.
– MFAL
Oct 12 at 8:12
add a comment |
Great, as a temporary solution for the specific need of building ionic android projects, although is not ideal.
– MFAL
Oct 12 at 8:12
Great, as a temporary solution for the specific need of building ionic android projects, although is not ideal.
– MFAL
Oct 12 at 8:12
Great, as a temporary solution for the specific need of building ionic android projects, although is not ideal.
– MFAL
Oct 12 at 8:12
add a comment |
[https://github.com/tensorflow/tensorflow/tree/master/tensorflow/examples/android][1]
For people trying out this example and facing issues with latest NDK. Can follow this solution.
In build.gradle
change this
classpath 'com.android.tools.build:gradle:3.0.1'
To
classpath 'com.android.tools.build:gradle:3.1.2'
The reason is mips are deprecated in the latest ndk versions, Gradle version 3.1.2 will not have a compulsion for mips. It assumes the presence for these missing folders.
add a comment |
[https://github.com/tensorflow/tensorflow/tree/master/tensorflow/examples/android][1]
For people trying out this example and facing issues with latest NDK. Can follow this solution.
In build.gradle
change this
classpath 'com.android.tools.build:gradle:3.0.1'
To
classpath 'com.android.tools.build:gradle:3.1.2'
The reason is mips are deprecated in the latest ndk versions, Gradle version 3.1.2 will not have a compulsion for mips. It assumes the presence for these missing folders.
add a comment |
[https://github.com/tensorflow/tensorflow/tree/master/tensorflow/examples/android][1]
For people trying out this example and facing issues with latest NDK. Can follow this solution.
In build.gradle
change this
classpath 'com.android.tools.build:gradle:3.0.1'
To
classpath 'com.android.tools.build:gradle:3.1.2'
The reason is mips are deprecated in the latest ndk versions, Gradle version 3.1.2 will not have a compulsion for mips. It assumes the presence for these missing folders.
[https://github.com/tensorflow/tensorflow/tree/master/tensorflow/examples/android][1]
For people trying out this example and facing issues with latest NDK. Can follow this solution.
In build.gradle
change this
classpath 'com.android.tools.build:gradle:3.0.1'
To
classpath 'com.android.tools.build:gradle:3.1.2'
The reason is mips are deprecated in the latest ndk versions, Gradle version 3.1.2 will not have a compulsion for mips. It assumes the presence for these missing folders.
answered Dec 17 at 9:58
Sujit Royal
663
663
add a comment |
add a comment |
Facing same issue.
I got success following ways.
Open your buldle.gradle file and upgrade the versions for following both classpath
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'
Then Sync and after get one dilaog for update Gradle version as well then click that link and wait for download all required updates(Hope internet available). After taking long time you got Success.
add a comment |
Facing same issue.
I got success following ways.
Open your buldle.gradle file and upgrade the versions for following both classpath
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'
Then Sync and after get one dilaog for update Gradle version as well then click that link and wait for download all required updates(Hope internet available). After taking long time you got Success.
add a comment |
Facing same issue.
I got success following ways.
Open your buldle.gradle file and upgrade the versions for following both classpath
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'
Then Sync and after get one dilaog for update Gradle version as well then click that link and wait for download all required updates(Hope internet available). After taking long time you got Success.
Facing same issue.
I got success following ways.
Open your buldle.gradle file and upgrade the versions for following both classpath
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'
Then Sync and after get one dilaog for update Gradle version as well then click that link and wait for download all required updates(Hope internet available). After taking long time you got Success.
answered 2 days ago
subhash gaikwad
516
516
add a comment |
add a comment |
If you don't use the NDK, unset the environment variable ANDROID_NDK_HOME.
add a comment |
If you don't use the NDK, unset the environment variable ANDROID_NDK_HOME.
add a comment |
If you don't use the NDK, unset the environment variable ANDROID_NDK_HOME.
If you don't use the NDK, unset the environment variable ANDROID_NDK_HOME.
answered Oct 31 '17 at 9:46
Cristan
2,8752630
2,8752630
add a comment |
add a comment |
Steps I have followed to fix the issue as follows,
Analyze -> Code Cleanup
File -> Project Structures -> Select project from the list and update the gradle version to latest.
Build -> Clean Project
Build -> Make Project
Now the issue related to the build may get reported like using compile instead of implementation etc.
Please fix those and hopefully it should fix the issue.
add a comment |
Steps I have followed to fix the issue as follows,
Analyze -> Code Cleanup
File -> Project Structures -> Select project from the list and update the gradle version to latest.
Build -> Clean Project
Build -> Make Project
Now the issue related to the build may get reported like using compile instead of implementation etc.
Please fix those and hopefully it should fix the issue.
add a comment |
Steps I have followed to fix the issue as follows,
Analyze -> Code Cleanup
File -> Project Structures -> Select project from the list and update the gradle version to latest.
Build -> Clean Project
Build -> Make Project
Now the issue related to the build may get reported like using compile instead of implementation etc.
Please fix those and hopefully it should fix the issue.
Steps I have followed to fix the issue as follows,
Analyze -> Code Cleanup
File -> Project Structures -> Select project from the list and update the gradle version to latest.
Build -> Clean Project
Build -> Make Project
Now the issue related to the build may get reported like using compile instead of implementation etc.
Please fix those and hopefully it should fix the issue.
edited Sep 2 at 15:14
answered Sep 2 at 15:00
Ajay Kumar Meher
1,5171122
1,5171122
add a comment |
add a comment |
I fixed the issue by reinstalling the NDK.
add a comment |
I fixed the issue by reinstalling the NDK.
add a comment |
I fixed the issue by reinstalling the NDK.
I fixed the issue by reinstalling the NDK.
answered Sep 3 at 12:06
Rajesh Khadka
750926
750926
add a comment |
add a comment |
I have same error while adding NDK. I tried much and later I find below solution which works perfectly for me.
if you want to add NDK in your project then follow below step.
1. If you installed NDK using SDK Manager then uninstall first. (untick from SDK tools and apply)
2. Download manually NDK from its official site. (any version) if project old then prefer version 17.
3. Extract that file.
4. Go to your project structure > NDK path > add Extracted file path here.
5. Build Project. and its work.
add a comment |
I have same error while adding NDK. I tried much and later I find below solution which works perfectly for me.
if you want to add NDK in your project then follow below step.
1. If you installed NDK using SDK Manager then uninstall first. (untick from SDK tools and apply)
2. Download manually NDK from its official site. (any version) if project old then prefer version 17.
3. Extract that file.
4. Go to your project structure > NDK path > add Extracted file path here.
5. Build Project. and its work.
add a comment |
I have same error while adding NDK. I tried much and later I find below solution which works perfectly for me.
if you want to add NDK in your project then follow below step.
1. If you installed NDK using SDK Manager then uninstall first. (untick from SDK tools and apply)
2. Download manually NDK from its official site. (any version) if project old then prefer version 17.
3. Extract that file.
4. Go to your project structure > NDK path > add Extracted file path here.
5. Build Project. and its work.
I have same error while adding NDK. I tried much and later I find below solution which works perfectly for me.
if you want to add NDK in your project then follow below step.
1. If you installed NDK using SDK Manager then uninstall first. (untick from SDK tools and apply)
2. Download manually NDK from its official site. (any version) if project old then prefer version 17.
3. Extract that file.
4. Go to your project structure > NDK path > add Extracted file path here.
5. Build Project. and its work.
answered Oct 3 at 8:17
gunavant patel
17618
17618
add a comment |
add a comment |
just update classpath 'com.android.tools.build:gradle:X.X.X' in Project Build.Gradle and replace X to the latest version do you have
add a comment |
just update classpath 'com.android.tools.build:gradle:X.X.X' in Project Build.Gradle and replace X to the latest version do you have
add a comment |
just update classpath 'com.android.tools.build:gradle:X.X.X' in Project Build.Gradle and replace X to the latest version do you have
just update classpath 'com.android.tools.build:gradle:X.X.X' in Project Build.Gradle and replace X to the latest version do you have
answered Oct 6 at 16:27
A.R.B.N
308
308
add a comment |
add a comment |
I faced same issue and I resolved this by
changing gradle version of project-label .gradle file to Latest
classpath 'com.android.tools.build:gradle:3.2.1'
and add these checks on app label .gradle file
packagingOptions{
doNotStrip '*/mips/*.so'
doNotStrip '*/mips64/*.so'
}
Hope This will help.
nice, thanks for copying my stackoverflow.com/a/50944898/192373
– Alex Cohn
Dec 13 at 16:30
@AlexCohn Our answers are similar . It doesn't implies that someone copied others answer. Btw Thanks for the info...
– Prinkal Kumar
Dec 13 at 16:43
add a comment |
I faced same issue and I resolved this by
changing gradle version of project-label .gradle file to Latest
classpath 'com.android.tools.build:gradle:3.2.1'
and add these checks on app label .gradle file
packagingOptions{
doNotStrip '*/mips/*.so'
doNotStrip '*/mips64/*.so'
}
Hope This will help.
nice, thanks for copying my stackoverflow.com/a/50944898/192373
– Alex Cohn
Dec 13 at 16:30
@AlexCohn Our answers are similar . It doesn't implies that someone copied others answer. Btw Thanks for the info...
– Prinkal Kumar
Dec 13 at 16:43
add a comment |
I faced same issue and I resolved this by
changing gradle version of project-label .gradle file to Latest
classpath 'com.android.tools.build:gradle:3.2.1'
and add these checks on app label .gradle file
packagingOptions{
doNotStrip '*/mips/*.so'
doNotStrip '*/mips64/*.so'
}
Hope This will help.
I faced same issue and I resolved this by
changing gradle version of project-label .gradle file to Latest
classpath 'com.android.tools.build:gradle:3.2.1'
and add these checks on app label .gradle file
packagingOptions{
doNotStrip '*/mips/*.so'
doNotStrip '*/mips64/*.so'
}
Hope This will help.
answered Oct 18 at 12:57
Prinkal Kumar
1,2652512
1,2652512
nice, thanks for copying my stackoverflow.com/a/50944898/192373
– Alex Cohn
Dec 13 at 16:30
@AlexCohn Our answers are similar . It doesn't implies that someone copied others answer. Btw Thanks for the info...
– Prinkal Kumar
Dec 13 at 16:43
add a comment |
nice, thanks for copying my stackoverflow.com/a/50944898/192373
– Alex Cohn
Dec 13 at 16:30
@AlexCohn Our answers are similar . It doesn't implies that someone copied others answer. Btw Thanks for the info...
– Prinkal Kumar
Dec 13 at 16:43
nice, thanks for copying my stackoverflow.com/a/50944898/192373
– Alex Cohn
Dec 13 at 16:30
nice, thanks for copying my stackoverflow.com/a/50944898/192373
– Alex Cohn
Dec 13 at 16:30
@AlexCohn Our answers are similar . It doesn't implies that someone copied others answer. Btw Thanks for the info...
– Prinkal Kumar
Dec 13 at 16:43
@AlexCohn Our answers are similar . It doesn't implies that someone copied others answer. Btw Thanks for the info...
– Prinkal Kumar
Dec 13 at 16:43
add a comment |
I navigated to local.properties, and in there the
ndk.dir=/yo/path/for/NDK
line needs to be updated to where your ndk lies.
I was using Crystax NDK, and didn't realize the original Android NDK was still in use.
add a comment |
I navigated to local.properties, and in there the
ndk.dir=/yo/path/for/NDK
line needs to be updated to where your ndk lies.
I was using Crystax NDK, and didn't realize the original Android NDK was still in use.
add a comment |
I navigated to local.properties, and in there the
ndk.dir=/yo/path/for/NDK
line needs to be updated to where your ndk lies.
I was using Crystax NDK, and didn't realize the original Android NDK was still in use.
I navigated to local.properties, and in there the
ndk.dir=/yo/path/for/NDK
line needs to be updated to where your ndk lies.
I was using Crystax NDK, and didn't realize the original Android NDK was still in use.
answered Oct 22 at 21:56
Yipeng Zhang
113
113
add a comment |
add a comment |
After three days I figured it out:
The problem can be solved by downloading an older version of the NDK (14b) and going to Android Studio to File | Project Structure and selecting it.
add a comment |
After three days I figured it out:
The problem can be solved by downloading an older version of the NDK (14b) and going to Android Studio to File | Project Structure and selecting it.
add a comment |
After three days I figured it out:
The problem can be solved by downloading an older version of the NDK (14b) and going to Android Studio to File | Project Structure and selecting it.
After three days I figured it out:
The problem can be solved by downloading an older version of the NDK (14b) and going to Android Studio to File | Project Structure and selecting it.
answered Nov 20 at 12:33
Philip
1
1
add a comment |
add a comment |
Upgrade your Gradle Plugin
com.android.tools.build:gradle:3.1.4
Upgrade gradle wraperpropeties
distributionUrl=https://services.gradle.org/distributions/gradle-4.4-all.zip
add a comment |
Upgrade your Gradle Plugin
com.android.tools.build:gradle:3.1.4
Upgrade gradle wraperpropeties
distributionUrl=https://services.gradle.org/distributions/gradle-4.4-all.zip
add a comment |
Upgrade your Gradle Plugin
com.android.tools.build:gradle:3.1.4
Upgrade gradle wraperpropeties
distributionUrl=https://services.gradle.org/distributions/gradle-4.4-all.zip
Upgrade your Gradle Plugin
com.android.tools.build:gradle:3.1.4
Upgrade gradle wraperpropeties
distributionUrl=https://services.gradle.org/distributions/gradle-4.4-all.zip
answered Dec 10 at 14:02
RAHULRSANNIDHI
241216
241216
add a comment |
add a comment |
1 2
next
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f35128229%2ferror-no-toolchains-found-in-the-ndk-toolchains-folder-for-abi-with-prefix-llv%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try to update the gradle tools. classpath 'com.android.tools.build:gradle:3.2.0-beta05'
– Photon Point
Aug 13 at 7:50
use developer.android.com/ndk/downloads/older_releases and Android NDK, Revision 16b (December 2017) version to download required folders and fix the issue.
– Panache
Oct 2 at 9:15