[GR-40305] Provide shared libraries required by image as part of produced artifacts

[java71]

Hi,
I have just generated an 'exe' file using GraalVM native-image.
Program works well when 'jsound.dll' is located in same execution directory.

Is it possible to enforce native-image to generate an executable that encapsulate the dll ?
Any option ?
Thanks for your advice.

[olpaw]

What we are currently missing in native-image is a step where we copy the dynamic libraries the built image depends on, to the directory where the image got built into. Also the list of Produced artifacts: that we output at the end of an image-build should list them. Something like:

Produced artifacts:
 /home/user/my_sound_using_image.exe (executable)
 /home/user/jsound.dll (shared library required by image)

This way the user sees that the resulting image requires an additional shared library to function correctly. This is will also be useful for applications that use UI frameworks that we can only support properly via loading their shared libraries components at image-runtime (e.g. AWT/Swing applications). cc @pejovica

[java71]

Hi,
thanks for your answer.
I hope that this new feature will become available soon.
It is much much easier to deliver a product as one single file!

[olpaw]

It is much much easier to deliver a product as one single file!

Unfortunately that's not always feasible. While we do support single file awt images in Linux at the moment it causes many problems and limitations. At some point in the future awt images on Linux will also require awt as shared library instead of linking it in statically.