You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for some reason lime 8.1.0 messes up the ndk path in bin/app/build.gradle
FAILURE: Build failed with an exception.
* Where:
Build file 'C:\Users\User\Project\export\release\android\bin\app\build.gradle' line: 18
* What went wrong:
Could not compile build file 'C:\Users\User\Project\export\release\android\bin\app\build.gradle'.
> startup failed:
build file 'C:\Users\User\Project\export\release\android\bin\app\build.gradle': 18: Unexpected character: '\'' @ line 18, column 10.
ndkPath 'c \ : \ \android-ndk-r11c'
1 error
* 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 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.4.2/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 2s
bin\app\build.gradle has the NDK path as c\ : \ \android-ndk-r11c(with no spaces ofc) whenever i run lime build android
if i change the path to c:\android-ndk-r11c in build.gradle while it's compiling it goes just fine with no errors
I'm compiling on windows 11 so idk if other platforms have this issue
The text was updated successfully, but these errors were encountered:
for some reason lime 8.1.0 messes up the ndk path in bin/app/build.gradle
bin\app\build.gradle has the NDK path as c\ : \ \android-ndk-r11c(with no spaces ofc) whenever i run lime build android
if i change the path to c:\android-ndk-r11c in build.gradle while it's compiling it goes just fine with no errors
I'm compiling on windows 11 so idk if other platforms have this issue
The text was updated successfully, but these errors were encountered: