-
-
Notifications
You must be signed in to change notification settings - Fork 652
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
LWJGL_BUILD_OFFLINE=true results in releases being build with incorrect native binaries #740
Comments
actually here is the issue: lwjgl3/config/build-definitions.xml Line 135 in ad60275
however, the copy command uses this static definition and copies the ARM64 file over to the changing Lines 1043 to 1045 in ad60275
hence why arm64 binaries end up in x86_64 and arm32 jars |
moving the definition should solve the issue
note there may be better ways to solve this and there may be other places where lib.native is used incorrectly such as here |
theofficialgman@e04a910 |
@theofficialgman Thanks, offline mode should produce correct artifacts now! |
- A platform/architecture that is missing locally does not generate an artifact anymore. - When multiple architectures are present locally, native libraries are now bundled in the correct artifacts.
Version
3.3.0 (nightly), 3.2.3
Platform
Linux x64, Linux arm64, Linux arm32
JDK
OpenJDK 11
Module
All
Bug description
following these buildsteps:
the
bin/RELEASE/modulename
folders containlwjgl-modulename-natives-linux.jar
,lwjgl-modulename-natives-linux-arm32.jar
,lwjgl-modulename-natives-linux-arm64.jar
files. NOTE, this was on offline release, no binaries were downloaded (verified that), and all of those jars contain the ARM64 binaries. I believe this must be a problem with the generateNativeModuleInfoClasses that is causing the creation of all three architectures and the copying of the available arm64 binaries to all 3 folders which get packed into jars.lwjgl3/modules/generator/src/main/java/org/lwjgl/generator/util/ModuleInfoGen.java
Lines 164 to 224 in 18ef45b
bin/linux/arm64
andbin/libs/native/linux/arm64
are the only folders made from theant compile-native
command so that is working correctly, it is just an issue with theant release
this issue probably also happens on windows/macos but is untested
Stacktrace or crash log output
No response
The text was updated successfully, but these errors were encountered: