SachinVin/citra_android

Neon Error

Nun-z opened this issue · 13 comments

Nun-z commented

I'm getting the following error message when trying to build:

arm_neon.h:65:24: error: 'neon_vector_type' attribute is not supported for this target.

In build.gradle, I have the following line:
"-DANDROID_ARM_NEON=ON" // cryptopp requires Neon to work

This matches the docs here: https://developer.android.com/ndk/guides/cpu-arm-neon.html#per-app. Where have I gone wrong?

SachinVin commented

Are you building for x86?

Nun-z commented

I'm trying to build for arm64. I left x86 commented out next to abiFilters.

Nun-z commented

Nevermind, got it to work. It runs fine when built with the backend in this project, but it crashes when launched if built with a new backend cloned from here: https://github.com/citra-emu/citra.

M220 commented

I get this error too when building on appveyor and I did several things to fix it but Nothing worked for me ( and I'm using SachinVin's Citra backend too ). Is there any specific line you've changed to get it to work? Because SachinVin's appveyor has been failing with this error too.

M220 commented

@SachinVin
Do you have any culprit in mind? 🤔
And is there a way to ignore all of the errors when building with appveyor and finish it anyway?

Nun-z commented

I get this error too when building on appveyor and I did several things to fix it but Nothing worked for me ( and I'm using SachinVin's Citra backend too ). Is there any specific line you changed to get it to work? Because SachinVin's appveyor has been failing with this error too.

Replace line 74 of citra_android\app\build.gradle with:

abiFilters "arm64-v8a"//, "x86_64", "armeabi-v7a", "x86"

SachinVin commented
M220 commented

  • Nun-z
    I did that and I've got less errors but it failed with the ":app:PackageRelease" task anyway and after a few tries to address it, I gave up XD
    But still! Thanks a lot! At least it gave me that one error instead of overflowing with errors ;)

  • SachinVin
    I did a quick analysis of past successful builds of appveyor from your repo and while I was comparing those logs with mine, the different version of Android SDK platform tools version catched my eye, in your past successful builds, appveyor used the version "28.0.1" but in my build it uses the "29.0.4" one. Can the issue be from the new Android SDK platform tools/Visual Studio image?

Nun-z commented

Is the error something about cubeb, speex?

M220 commented

No (though I had that error a year ago I think, what was causing it?!), appveyor actually succeeded to build after I commented out the "signingConfig signingConfigs.release" line of build.gradle ( after "too many errors" error, it turns out the second error that stopped appveyor from building was the Keys because It couldn't read or receive them I think so it said that those keys are empty and then failed to build) and it uploaded an unsigned apk, but I couldn't install it. It always fails to install and I dunno why, I'm pretty sure the kirin 970 uses armv8a architecture 🤔
Edit : Well now I'm getting that cubeb/speex error again after a year XD

SachinVin commented
M220 commented

I didn't know that 🤔 Thanks for telling me! And sorry if I don't know the most basic stuff about ci appveyor, I started building with it a few days ago 😅

Again, thanks for telling me that!

Nun-z commented

I think this issue should be closed.