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
I built a program using multik as a dependency and noticed that file size is huge.
Inside of the built shadow jar, the size of the entry containing all of the native libs for multik was 115MB, compressed.
I also noticed that the majority of that is unused if targeting only one OS:
Can Multik be built for each OS in different artifacts, kind of like how JavaFX is? Then the developer can include whichever OSs they need to support, and minimize the size of the library if they only need to target one OS.
The text was updated successfully, but these errors were encountered:
In addition to platform-specific artifacts, it would be helpful if multik continued to distribute a single fat JAR containing all shared libraries for multiplatform builds. As a library author, I find this format more convenient to use, even though it produces a larger overall binary.
Ideally both the multiplatform and the single platform jars can be available so that library users don't have to worry about including the right files and can make their choice easily.
I built a program using multik as a dependency and noticed that file size is huge.
Inside of the built shadow jar, the size of the entry containing all of the native libs for multik was 115MB, compressed.
I also noticed that the majority of that is unused if targeting only one OS:
Can Multik be built for each OS in different artifacts, kind of like how JavaFX is? Then the developer can include whichever OSs they need to support, and minimize the size of the library if they only need to target one OS.
The text was updated successfully, but these errors were encountered: