Closed pavankuppa closed 3 years ago
Pi4J version 2.0 includes a Java system property you can include to override this default extraction behavior. Perhaps we should add that support to v1.3 which would at least allow you to bypass the SO extract from JAR logic and just let you tell the library where to find the SO file.
@pavankuppa see https://v2.pi4j.com/library-path for more info
Related to #454
Closing with workaround in Pi4J v1.3.
Added support for system property ("pi4j.library.path") to override default embedded library resolution and allow for user explicitly defined resolution path for libpi4j.so
native library.
If there is no /tmp
available, then the Pi4J JAR does not have a location to extract the embedded ("libpi4j.so") native library. The library will need to be extracted and place on the system and a path provided using this system property. Note: you can also use "system" or "local" to have the JAR look for the "libpi4j.so" native library in the system path or in the local runtime directory alongside the JAR file.
It seems the path is not loading which is present inside the jar file
Installed wiringpi too -
sudo apt-get install wiringpi
Even I extract the jar and keep libpi4j.so in lib folder as(raspberrypi/dynamic) where jar are placed