-
Notifications
You must be signed in to change notification settings - Fork 76
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
The JLI_Launch funtion has not been found in the provided DLL #642
Comments
Needs to compare dlls by working and not working system. (Are Invalid unzipping?) |
(I forgot to update this ticket ...) @praj-foss tracked this error down to originate from https://github.com/MovingBlocks/TerasologyJavaLauncher/blob/385dc34b93179f1658faf6aff0d97fd8cb62c299/jli_library_win.cpp#L52. As that C++ code to write our own EXE hasn't been maintained for years I'm in favor of just removing them and fully rely on the BAT file for Windows. @praj-foss suggested on Discord to use https://github.com/libgdx/packr to create a replacement for the EXE.
The JSON file contains the full class path, so even though this might work for testing the approach right now we'd need a way to generate the config file with each build. There is no PR for this yet. |
Using the BAT startup script (Gradle default) is probably the most error-free approach because Gradle is maintaining it. However, I'm not sure how user-friendly it will be for normal Windows users. I haven't been on Windows for quite a while, but here are some things we should keep in mind when shipping BAT launchers:
If we take the other route (using libgdx's generic EXE), simply copying over those two static files (exe + json) into the final launcher zip should work fine most of the time. But yeah, we'll need to modify the JSON whenever our project dependencies change. And since exe uses native C interfaces to jvm, we also need to ensure that it works fine anytime we bundle a different jvm with the zip. |
Until we get clearer on the above-mentioned questions, @skaldarnar proposed the following intermediate actions:
|
On some systems the launcher does not start with the following error message:
From the reports we have received so far there is nothing to be clearly identified as root cause.
So far, all reports were from systems running Windows 10.
Launcher Versions
Reported Systems
The issue was reported for systems with the following specs:
(reported by Mister)
CPU Intel Celeron N3050 (1.6 Gigglehertz)
Ram: 4 GB (Shared with the GPU)
Windows 10 Home (64 bit) V: 20H2 (19042.928)
(aka: HP 260 G4)
(reported by GEISTBREAKER and fatmaf)
Windows 10 x64
Working System
The issue cannot be reproduced on the following systems:
RAM 16 GB
Win 10 Home (20H2) (same as above)
GPU ASUS 705 Ti STRIX
The text was updated successfully, but these errors were encountered: