Broken NDK build

[sevar83]

Log: https://jitpack.io/com/github/sevar83/android-spatialite/2.0.0-RC0/build.log

Looks like some of the latest NDK update have broken my build. The issue is in the NDK but fixed in NDK R15c: android/ndk#332

Please, could you tell me the NDK version used in JitPack?

[jitpack-io]

Hi @sevar83

The current version is 15.2.4203891 and it gets updated automatically.

[sevar83]

For future readers: I've fixed it by adding APP_DEPRECATED_HEADERS := true to Application.mk. Not the best solution but works for now ™.

[alvminvm]

try adding _FILE_OFFSET_BITS=32 to Android.mk

[kishorejethava]

@sevar83 I have published library at Jitpack but log showing build failed.

Log

Execution failed for task ':ImageLibrary:ndkBuild'.
> A problem occurred starting process 'command 'D:/AndroidSDK/ndk-bundle/ndk-build''

So the question is how to set NDK path?

right now I have written local path in local.properties

ndk.dir=D\:\\AndroidSDK\\ndk-bundle

Please help me!!

[jitpack-io]

@kishorejethava JitPack provides a NDK_HOME environment variable.
Would recommend removing ndk.dir from local.properties and then building that on JitPack.

[kishorejethava]

Thanks @jitpack-io, I have already done it and it's worked!!

[feresr]

Wondering what should NDK_HOME be set to?
Shouldn't this be configured by jitpack on the host machine (the one running the build)
I have ndkVersion "22.1.7171670" defined in my build.gradle but I'm still getting

NDK from ndk.dir at /opt/android-sdk-linux/ndk-bundle had version [21.1.6352462] which disagrees with android.ndkVersion [22.1.7171670]

I have not defined ndk.dir anywhere in my project, I'm not sure where that is coming from
Appreciate any help. I suck at devops

[sevar83]

I think the local jitpack defines ndk.dir and your project defines ndkVersion and they different which causes the conflict. I don't know how to deal with this. The ndkVersion property is something new to me.

…

On Tue, Jun 1, 2021 at 1:33 AM Fernando Raviola ***@***.***> wrote: Wondering what should NDK_HOME be set to? Shouldn't this be configured by jitpack on the host machine (the one running the build) I have ndkVersion "22.1.7171670" defined in my build.gradle but I'm still getting NDK from ndk.dir at /opt/android-sdk-linux/ndk-bundle had version [21.1.6352462] which disagrees with android.ndkVersion [22.1.7171670] I have not defined ndk.dir anywhere in my project, I'm not sure where that is coming from Appreciate any help. I suck at devops — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1776 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA5FVPL22WNF75WF6EWMJ3TQQFDZANCNFSM4D3HIWVQ> .

[feresr]

I think the local jitpack defines ndk.dir and your project defines ndkVersion and they different which causes the conflict. I don't know how to deal with this. The ndkVersion property is something new to me.
…

I agree, I think this is what's happening as well... the question is, why is jitpack defining a random ndk version? AFAIK ndk.dir is legacy (deprecated) and ndkVersion should be favoured

[sevar83]

The JitPack containers or VMs or whatever were instantiated with a fixed NDK version. At least that's how it was back in few years ago when I was dealing with JitPack. Now you should ask them how they handle the new ndkVersion thingy. I'm not aware.

…

On Tue, Jun 1, 2021 at 12:40 PM Fernando Raviola ***@***.***> wrote: I think the local jitpack defines ndk.dir and your project defines ndkVersion and they different which causes the conflict. I don't know how to deal with this. The ndkVersion property is something new to me. … <#m_7854712962639247054_> I agree, I think this is what's happening as well... the question is, why is jitpack defining a random ndk version? AFAIK ndk.dir is legacy (deprecated) and ndkVersion should be favoured — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1776 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA5FVPEXCTWBTNNHM4JIUDTQSTHPANCNFSM4D3HIWVQ> .

[github-actions]

This issue is stale because it has been open for 30 days with no activity.