On Tue, Jul 9, 2019 at 12:22 AM Richard W.M. Jones <rjones@redhat.com> wrote:

On Mon, Jul 08, 2019 at 01:54:16PM +0300, Arik Hadas wrote:
> Hi,
>
> When using the libguestfs-java bindings, java.library.path should point to
> the place the JNI stuff resides in. In [1] it was suggested to set it
> to /usr/local/lib
> but apparently, it is deployed elsewhere in other distributions, right? so
> I wonder what is the recommended way of setting it in a Java application
> that could execute on various distributions.
>
> Additionally, the libguestfs-java bindings for Fedora 30 seem to be missing
> - is it a known issue?
>
> [1] https://www.redhat.com/archives/libguestfs/2012-September/msg00057.html

I actually have no idea about any of these issues. However I would
note that the Java bindings do need some attention:

https://bugzilla.redhat.com/show_bug.cgi?id=1536762

Patches welcome!

Ack.

In addition to the things proposed in that bz, I think it would also be great to:

1. Support Java streams in addition to files - talked about it a bit with Pino at FOSDEM

2. Have a configuration file that points to the location of the JNI part at a known place (that the application can use)

The context of this is the integration with muCommander.

There's already an on-going initiative to leverage this functionality (!)

I'll try to address some of those things.

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html