CMake failures #1031
Description
Ref. 3168
From ARMAN (@best_seller_for_bot) on Telegram:
https://t.me/CodeOnTheGoDiscussions/2592
"Thanks for looking into it 🙏
Before CMake fails, the project loads normally and I can edit .cpp and CMakeLists.txt files.
When I try to build, CMake starts configuring but then fails during sync/build stage.
After that, sometimes the app restarts automatically and it does not reopen the previous project.
I’m using the experimental NDK template.
Let me know if you need logs — I can share them."
Additional information from user:
https://t.me/CodeOnTheGoDiscussions/2601
"I’m facing a persistent CMake/NDK configuration failure in AndroidIDE (Code on the Go) while building an ARM64 NDK project.
Environment:
- Device: ARM64 Android
- SDK: 35
- NDK: 25.2.9519653
- CMake: 3.22.1
- ABI: arm64-v8a
Current Error:
CMAKE_C_COMPILER clang is not a full path to an existing compiler tool
Compiler identification is unknown during configureCMakeDebug.
Troubleshooting Done:
- Cleared .cxx and build folders
- Reinstalled NDK
- Removed CMake directories manually
- Tested with and without explicit ndkVersion
- Verified ABI filter is arm64-v8a only
It appears the build system may be falling back to x86_64 host binaries instead of ARM-native toolchains, causing compiler detection failure.
Is there a way to force AndroidIDE/AGP to use native ARM CMake + NDK toolchains only?
Is there any hidden cache or configuration that needs to be overridden?
Any guidance would be greatly appreciated. Thanks!"
More info from ARMAN:
https://t.me/CodeOnTheGoDiscussions/2689
"Hey Admin, I'm trying to use the NDK template but it's completely broken. During the build, the IDE throws errors because it cannot locate the CMakeLists.txt file or the path is misconfigured in Gradle.
Is this a known bug in the current version? We need a stable fix for CMake linking so we can build native apps properly without these path errors."