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
$ sdk install java 17.0.8-graal
Stop! java 17.0.8-graal is not available. Possible causes:
* 17.0.8-graal is an invalid version
* java binaries are incompatible with your platform
* java has not been released yet
Tip: see all available versions for your platform:
$ sdk list java
I did that and got:
================================================================================
Available Java Versions for Exotic
================================================================================
Vendor | Use | Version | Dist | Status | Identifier
--------------------------------------------------------------------------------
No versions available for your platform at this time.
================================================================================
$ ./gradlew
./gradlew: line 2: $'\r': command not found
./gradlew: line 18: $'\r': command not found
./gradlew: line 64: $'\r': command not found
./gradlew: line 66: $'\r': command not found
./gradlew: line 69: $'\r': command not found
./gradlew: line 71: $'while\r': command not found
./gradlew: line 73: [: missing `]'
./gradlew: line 74: $'do\r': command not found
ls: cannot access './gradlew'$'\r': No such file or directory
./gradlew: line 79: syntax error near unexpected token `newline'
'/gradlew: line 79: ` *) app_path=$APP_HOME$link ;;
This is an EOL (line endings) compatibility issue.
git converts the files to \r\n on checkout.
I often use d2u to fix such issues.
The suggested fix is:
$ git config --global -e
# edit [core] section and set autocrlf=input
# then verify with:
$ git config --get core.autocrlf
input
gradlew.bat
I decided to try the build from cmd rather than bash:
Hi @VladimirAlexiev, thanks for the effort & the infos. I've never tried the build with Cygwin, I just now that some people use SDKMAN! with WSL. You are correct, a GraalVM JDK is only required for the build if a native executable (.exe) should be built, which, for regular builds is the default - the native executable should ease use after all.
I tried the instructions https://atextor.de/owl-cli/main/snapshot/index.html#building-from-source and have these troubles:
SDKMAN
I did that and got:
Line endings
This is an EOL (line endings) compatibility issue.
git converts the files to
\r\n
on checkout.I often use
d2u
to fix such issues.The suggested fix is:
gradlew.bat
I decided to try the build from
cmd
rather thanbash
:It gave some warnings about deprecated features, but was successful.
The complete build scan is at https://scans.gradle.com/s/nmmtoraixpzcu
running owl-cli
I currently use Temurin 22 (installed with
scoop
), but owl-cli seems to run ok.I think it needs
graalvm-17
only for the build process, because it fails to run with it:The text was updated successfully, but these errors were encountered: