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
Currently if you add every platform into same runnable jar file, it gives this error (running from windows):
Platform available on classpath: linux/x64. IE it tries to load all of the platform natives not only the useful ones.
Of course one solution is to make a runnable jar for every platform separately. but it would be much better if it was just one fat jar.
Yes I mean for both the user application and the import native library, which would load all suitable native libraries by the platform.
this would also minimize all library setup if all the libraries are in one fat library-native jar module. yeah it would make some applications larger, but you can also provide the individual parts of the libraries separately, per platform, like its done now. or at least make each fat native jar contain all libraries for each platform in one package. to minimize library hassle.
The text was updated successfully, but these errors were encountered:
Description
Currently if you add every platform into same runnable jar file, it gives this error (running from windows):
Platform available on classpath: linux/x64. IE it tries to load all of the platform natives not only the useful ones.
Of course one solution is to make a runnable jar for every platform separately. but it would be much better if it was just one fat jar.
Yes I mean for both the user application and the import native library, which would load all suitable native libraries by the platform.
this would also minimize all library setup if all the libraries are in one fat library-native jar module. yeah it would make some applications larger, but you can also provide the individual parts of the libraries separately, per platform, like its done now. or at least make each fat native jar contain all libraries for each platform in one package. to minimize library hassle.
The text was updated successfully, but these errors were encountered: