chrisb
Junior Member
Posts: 10
|
Post by chrisb on Mar 20, 2023 10:41:27 GMT
Hi all
Has anyone had success building with ndk 25, from the 7.5 branch? I'm getting builds that complete without error, but the application crashes as soon as it is launched. This is with sdk31 on a Samsung Android 13 device, and the application is fine when built with ndk 24. I see the same issue building with sdk 32, and I get a build failure with sdk 33.
If ndk 25 just isn't supported yet, I have a follow up question about a build error I am getting with ndk 24 on a Windows Server 2022 machine (builds on Windows 10 and Windows Server 2016 are ok).
Thanks
Chris.
|
|
|
Post by Alex Epifanov on Mar 20, 2023 10:44:26 GMT
We currently use NDK 23.1.7779620 for our prod build pipelines. Newer NDKs/SDKs will be supported in upcoming versions.
|
|
chrisb
Junior Member
Posts: 10
|
Post by chrisb on Mar 20, 2023 15:37:22 GMT
Thank you for that quick reply.
|
|
chrisb
Junior Member
Posts: 10
|
Post by chrisb on Mar 21, 2023 11:17:08 GMT
Just for reference - I am still unable to get a successful build on Windows Server 2022 / rhodes 7.5 / ndk 23 / sdk 31. But I am not blocked by this issue as I can use Windows Server 2019 instead.
The error I get is:
C:\Mobile\android-ndk-r23c\toolchains\llvm\prebuilt\windows-x86_64\bin\llvm-ar.exe: error: C:/Mobile/MobileApp/bin/target/android/release/extensions/coreapi/armeabi/libcoreapi.a: Function not implemented
(I'm using ndk r23c as I couldn't find a download for r23b as recommended by Alex)
|
|
|
Post by Alex Epifanov on Mar 29, 2023 23:01:35 GMT
can you share full build log with --trace flag ?
|
|
chrisb
Junior Member
Posts: 10
|
Post by chrisb on Apr 18, 2023 18:35:45 GMT
Sorry for the delay in replying - I don't currently have a Windows Server 2022 machine to get the trace build log. I will post another reply once I get a chance to set up a new server.
|
|
chrisb
Junior Member
Posts: 10
|
Post by chrisb on May 18, 2023 7:00:51 GMT
I've had another look at this and it seems the build problem is actually due to the use of a imdisk ramdisk. I will do a bit more investigation and then post the trace build log file on a new thread.
|
|