The current JVM version(s) don't allow to detect if an ARM CPU is "armel" or "armhf", where the latter is used for Raspberry Pi. Therefore it is not possible to ship the TR executable JAR with "armhf" support. Therefore we must choose a different implementation. The JVM environment variable -DdisableEmbeddedRXTX will, if set, disable the usage of the packed RXTX JNI files. In order to have the gateway work one would therefore have to provide this flag at TR gateway startup AND install librxtx-java using e.g., aptitude on the host OS.
The current JVM version(s) don't allow to detect if an ARM CPU is "armel" or "armhf", where the latter is used for Raspberry Pi. Therefore it is not possible to ship the TR executable JAR with "armhf" support. Therefore we must choose a different implementation. The JVM environment variable
-DdisableEmbeddedRXTXwill, if set, disable the usage of the packed RXTX JNI files. In order to have the gateway work one would therefore have to provide this flag at TR gateway startup AND installlibrxtx-javausing e.g., aptitude on the host OS.