A release build includes all neccessary artifacts to run rxtx on all officially supported platforms (see the build matrix).
This is a three step process:
First, run the platform independend build phase:
mvn -Dmake.release=prepare install
This will build the
artifacts and the [lib]rxtxSerial-os-arch binary matching your build platform. If your build host supports additional target platforms via cross compilers, you can include them in the build by enabling their respective maven profile. e.g. on a prepared Ubuntu Linux you can include all artifacts by running:
mvn -Dmake.release=prepare -Pwith-linux-x86,with-linux-x86_64,with-windows-x86,with-windows-x86_64,with-osx-x86_64 install
If your build host does not support the build of all targets, you have to continue the process on one or more other systems, until all native targets are built. To do that, you have to run above command (with respective profiles) on the machines. Then collect the binaries from the target directories and copy them to one machine. Deploy the binaries to the local maven repository on one machine. Then continue on this particular machine.
Finally the previously build artifacts are packed to a release by running
mvn -Dmake.release=bundle install
When the build finishes, the rxtx api JAR and rxtxSerial driver JAR are installed in your local maven repository. To use the JARs with ant or other build systems, you might copy them from the following directories:
/somewhere/rxtx/rxtx-api/target
/somewhere/rxtx/rxtxSerial/target