love2d
project installs the wrong ndk version and then crashs
basically because i have this version of android studio (which i got a few days ago) idk what happens but it insists on retrying with this specific ndk verrsion
now this might be intentional since looking at the code there was recently a change for using this version. if thats the case the readme needs an update.
also the project still crashes on build on my end... and since there is no seprate stable version anywhere thats really anoying as I dont really have any knowledge on what version i can go back to in order to get things working
the crash on a defualt clean build is a bunch of warnings like
C/C++: | ^
C/C++: /home/user/Desktop/lua_stuff/love-android/app/src/main/cpp/love/src/libraries/vma/vk_mem_alloc.h:16380:5: note: insert '_Nullable' if the pointer may be null
C/C++: 16380 | VmaAllocation* pAllocation,
C/C++: | ^
C/C++: | _Nullable
C/C++: /home/user/Desktop/lua_stuff/love-android/app/src/main/cpp/love/src/libraries/vma/vk_mem_alloc.h:16380:5: note: insert '_Nonnull' if the pointer should never be null
C/C++: 16380 | VmaAllocation* pAllocation,
C/C++: | ^
C/C++: | _Nonnull
C/C++: /home/user/Desktop/lua_stuff/love-android/app/src/main/cpp/love/src/libraries/vma/vk_mem_alloc.h:16380:18: warning: pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified) [-Wnullability-completeness]
C/C++: 16380 | VmaAllocation* pAllocation,
C/C++: | ^
C/C++: /home/user/Desktop/lua_stuff/love-android/app/src/main/cpp/love/src/libraries/vma/vk_mem_alloc.h:16380:18: note: insert '_Nullable' if the pointer may be null
C/C++: 16380 | VmaAllocation* pAllocation,
C/C++: | ^
C/C++: | _Nullable
C/C++: /home/user/Desktop/lua_stuff/love-android/app/src/main/cpp/love/src/libraries/vma/vk_mem_alloc.h:16380:18: note: insert '_Nonnull' if the pointer should never be null
C/C++: 16380 | VmaAllocation* pAllocation,
C/C++: | ^
C/C++: | _Nonnull
C/C++: /home/user/Desktop/lua_stuff/love-android/app/src/main/cpp/love/src/libraries/vma/vk_mem_alloc.h:16381:22: warning: pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified) [-Wnullability-completeness]
C/C++: 16381 | VmaAllocationInfo* pAllocationInfo)
C/C++: | ^
C/C++: /home/user/Desktop/lua_stuff/love-android/app/src/main/cpp/love/src/libraries/vma/vk_mem_alloc.h:16381:22: note: insert '_Nullable' if the pointer may be null
C/C++: 16381 | VmaAllocationInfo* pAllocationInfo)
followed by
> Task :app:mergeNormalRecordReleaseNativeDebugMetadata FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:mergeNormalRecordReleaseNativeDebugMetadata'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.MergeNativeDebugMetadataTask$MergeNativeDebugMetadataWorkAction
> Java heap space
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.9/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 5m 14s
94 actionable tasks: 94 executed
(base) user@user-System-Product-Name:~/Desktop/lua_stuff/love-android$
also more context i have 128gb of ram so the heap space is most likely not a phisical ram issue
For the NDK issue, r27b is indeed correct NDK version LOVE 12 needs (main branch). Do note that this may be upgraded later as LOVE 12 is not yet fully stable.
As for the "Java heap space" error, unfortunately Gradle runs their build instance with low max RAM. You either need to run with GRADLE_OPTS environment variable (see our GitHub Actions CI steps) or by adding this into your ~/.gradle/gradle.properties:
org.gradle.jvmargs=-Xmx8G
