-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packr cannot recognise jrePath
Temurin JRE and JDK zips for Windows
#220
Comments
I can't tell what you're running. You can check that directory to make sure it has a 'jvm.dll' file in there with the proper directory structure. |
In short it was working fine with some Java 8 oldjdks. However when I tried to use latest Temurin 11 JDK or JRE zips for windows x64 or x86_64, it failed. The only thing the changed for packr was the link in this line: |
I haven’t tried the latest adoptium jdks. You could try forking and updating the test to see what happens.
|
This comment was marked as off-topic.
This comment was marked as off-topic.
Ignore #220 (comment), I forgot this was a Windows specific issue. Also my analysis isn't correct. |
For Temurin: ~$ find . | grep -P 'jvm.dll|libjvm.so|libjvm.dylib'
./bin/client/jvm.dll
./bin/server/jvm.dll for OldJDK $ find . | grep -P 'jvm.dll|libjvm.so|libjvm.dylib'
./jre/bin/server/jvm.dll does it doesn't work because for Temurin it is the folder root? |
ok @karlsabo I have built the packr from libgdx/packr:master@e6a277d which is the current latest on: And tested it with Temurin Releases. The result? Failure. CI Tests |
I updated the test suite to use the latest Temurin JDKs and JREs and they work without issue. Take a look at the list of JDKs and JREs that are used in testing: |
I tried with JRE and JDK Temurin 11 builds for Windows x64 and x86_64 from here:
https://adoptium.net/temurin/releases/
Packr cannot recogise either JDK or JRE and throws the following error:
Example Tests:
https://github.com/touhidurrr/buildUnciv/runs/6430297670?check_suite_focus=true#step:6:170
The text was updated successfully, but these errors were encountered: