Cannot extract native libraries from jar on Pi 4B

[pi4j]

Cannot extract native libraries from jar on Pi 4B

[savageautomate]

@lukehutch ,

Sorry for the delay ...
Now that I have completed Pi4J v1.3 and Pi4J v1.4 and released them, I'm focusing on v2. now.

Have you tried any recent builds? We now publish the Pi4J-2.0-SNAPSHOT JARs to the OSS Maven Repository as well as here: https://github.com/Pi4J/download via automated CI/CD scripts when anything is committed/merged into the main branch.

Are you running 32-bit Raspberry Pi OS or 64-bit Raspberry Pi OS?

Thanks, Robert

[lukehutch]

I managed to manually extract libpi4j-pigpio.so from the fat jar and store it in /home/pi, then was able to successfully launch with -Dpi4j.library.path=/home/pi. I still don't know why the automatic extraction doesn't work.

[savageautomate]

@lukehutch

How do I enable log4j logging in Pi4j v2? I looked at the code in NativeLibraryLoader, but I can't see the debug messages on the console to determine what is going wrong here. I checked the docs but didn't see a suggestion about how to enable logging.

It uses the SPF4J API. You can include the slf4j-simple JAR file in your project to print the log message to the console.
Next, you will need to enable DEBUG level logging with code like this.

        // configure default lolling level, accept a log level as the fist program argument
        System.setProperty("org.slf4j.simpleLogger.defaultLogLevel", "DEBUG");

In my case, I see log message like these on my RPi4B (32-bit armv7l)

[main] DEBUG com.pi4j.library.pigpio.util.NativeLibraryLoader - Attempting to load library [libpi4j-pigpio.so] using path: [/lib/armhf/libpi4j-pigpio.so]
[main] DEBUG com.pi4j.library.pigpio.util.NativeLibraryLoader - Library [libpi4j-pigpio.so] loaded successfully using embedded resource file: [/lib/armhf/libpi4j-pigpio.so]

[lukehutch]

Have you tried any recent builds? We now publish the Pi4J-2.0-SNAPSHOT JARs to the OSS Maven Repository as well as here: https://github.com/Pi4J/download via automated CI/CD scripts when anything is committed/merged into the main branch.

I was using the most recent SNAPSHOT build at the time I left the last comment, yes.

Are you running 32-bit Raspberry Pi OS or 64-bit Raspberry Pi OS?

64-bit Raspbian on a Raspberry Pi 4B.

If you want to see the problem, mvn install this:

https://github.com/lukehutch/Adafruit-OLED-Bonnet-Toolkit

Then mvn package this:

https://github.com/lukehutch/usb-copier

When the resulting fat jar is run on the Pi, it can't find the Pi4J library inside the fat jar, even though it's at the right location. You can see how I had to manually copy the library file out of the jar here, in order to launch the jar:

lukehutch/usb-copier#1

[SeanCheatham]

I ran into issues loading the native library as well. In my particular case, a different error indicated it was unable to find the libgpio.so library. I followed the installation instructions for that here.

[lukehutch]

I found a library that solves this problem:

https://github.com/ibmsoe/jniloader

The static method in JniLoader enables developers to ship native libraries in jar files which are extracted and loaded at runtime, making native loading transparent for the end-user (as long as they are on a platform supported by you).