WARNING: ABIs [armeabi-v7a,armeabi] set by 'android.injected.build.abi' gradle flag contained 'ARMEABI' not targeted by this project

Question

I had this issue last time after upgrade NDK version to latest version in Android Studio. I also found solution to fix this. If anyone has this issue , I hope it is the best question and answer for you. Please check my answer.

Chivorn · Accepted Answer · 2018-09-26T04:10:44.990

23

I found solution by reading on release note here for NDK revision 16.

If you config your project with Application.mk just add the following to your Application.mk file:
```
APP_STL := c++_shared
```

If you're using CMake via Gradle, add the following to your build.gradle:

externalNativeBuild {
    cmake {
        cppFlags ""
        arguments "-DANDROID_STL=c++_shared"
    }
}

To keep up to date with new release and note, please follow this NDK Revision History to apply with new changed.

I hope it can fix your issue.

edited Sep 26 '18 at 04:10

answered May 11 '18 at 07:15

Chivorn

2,203
2
21
37

10

I have added the c++_shared to get the compilation to work at all with NDK-r18, however, I still have the same ARMEABI warning. Not sure what is trying to use this now. – Jim Leask Sep 25 '18 at 21:05
@chivorn I think NDK-r16 still supported this so it wouldn't be a problem there. It still happens for me with NDK-r18 – Jim Leask Sep 28 '18 at 18:43
@JimLeask I also use ndk-r18. Same warning from Java compiler when it is building for devices. – Graham Lee Sep 28 '18 at 18:49
1

The warning is gone, but the app crashes upon start. (gradle build, NDK 19) – Jake 'Alquimista' LEE Jan 31 '19 at 02:29
Checked for NDK 20. The warning still exists. – ranka47 Feb 26 '20 at 20:29

score 6 · Answer 2 · answered Feb 07 '19 at 19:06

6

According to Android documentation this is a known issue, and its due to the fact that the gradle plugin still includes unsupported ABIs by default. armbeabi was deprecated in NDKr16 and removed in r17 hence the warning. To fix, list your supported architectures under splits.abi:

...
splits {
    abi {
        ...
        reset()
        include "x86", "armeabi-v7a", ...
    }
}

answered Feb 07 '19 at 19:06

Filipe Oliveira

69
1
5

my build already included `reset()` but still showing warning – Chisko Apr 19 '19 at 00:17
Is the warning mentioning `"armeabi"`? After using `reset()` you may still see warnings about other architectures depending on your build file. – Filipe Oliveira Apr 22 '19 at 09:54
Yes, getting the exact same warning as OP – Chisko Apr 22 '19 at 19:04
My last guess it would be some Android Studio caching then – Filipe Oliveira Apr 26 '19 at 10:40

score 2 · Answer 3 · edited Jan 28 '19 at 04:29

Got same issue and fixed through modifying the module build.gradle file by adding below setup:

android {
    ...
    splits {
        abi {
            enable true
            reset()
            include 'x86', 'x86_64', 'armeabi-v7a', 'arm64-v8a' //select ABIs to build APKs for
            universalApk true //generate an additional APK that contains all the ABIs
        }
    }

    project.ext.versionCodes = ['armeabi': 1, 'armeabi-v7a': 2, 'arm64-v8a': 3, 'mips': 5, 'mips64': 6, 'x86': 8, 'x86_64': 9]

    android.applicationVariants.all { variant ->
        variant.outputs.each { output ->
            output.versionCodeOverride =
                   project.ext.versionCodes.get(output.getFilter(com.android.build.OutputFile.ABI), 0) * 1000000 + android.defaultConfig.versionCode
        }
    }
}

For your reference, good luck.

score 1 · Answer 4 · answered Jan 16 '20 at 03:33

1

This doesn't resolve my problem, i resolved by adding this:

        ndk {
            abiFilters "armeabi-v7a"
        }

to android.defaultConfig

answered Jan 16 '20 at 03:33

Wilson Chen

506
3
11

WARNING: ABIs [armeabi-v7a,armeabi] set by 'android.injected.build.abi' gradle flag contained 'ARMEABI' not targeted by this project

4 Answers4

Linked

Related