Versions Compared

Old Version 1

changes.mady.by.user Steve Northover

Saved on

compared with

New Version 2

changes.mady.by.user David Hill

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Cross building for ARM hard float

In order to cross-compile for Linux/ARM you first need to obtain the ARM based libraries to compile against. You'll need several of the same tools as for a Linux desktop build, so you should start by making sure you can build for the desktop, following the instructions above.

For the cross-compilation step you should start with a Raspberry Pi with the Raspbian operating system installed on it, as described at OpenJFX on the Raspberry Pi. Then you need to install some additional libraries:

Code Block
themeMidnight
languagebash
sudo apt-get install \
  libatk1.0-dev \
  libdirectfb-dev \
  libgtk2.0-dev \
  libgstreamer0.10-dev \
  libgstreamer-plugins-base0.10-dev \
  libudev-dev \
  libxml2-dev \
  libxslt1-dev \
  libxtst-dev

This will pull over the libraries from the Raspbian repository.

There are three general parts to a cross compile tool chain, and there is a script in OpenJFX that will gather these items, an put them in the appropriate place to match the build configuration. These parts include:

  • A cross compiler
  • Include files
  • target libraries to link against

Note that the target libraries often do not have to match exactly the system they will run on, as long as the version number matches what is available on the target system. This means we can use a 'generic' version of most shared libraries, and still be able to work on the target system. There are certain libraries that are not generic - libEGL often will have vendor specific dependencies for example, making the library non-portable to link against.

A Linux command  'ldd -r a_shared_library.so' can be used to check a shared library on the target system, and validate that any dependencies are met. In particular this command can be used to test the OpenJFX native libraries to verify they are compatible.

Fetching a cross compile toolchain

Tip

These instructions assume that you don't need to set an HTTP or HTTPS proxy to access the internet, either because you don't need one or because your system is already configured to use one. If you need to define proxy settings then you should define the environment variables http_proxy and https_proxy. Both are needed. In the case of the command with sudo above, you need to define the proxy after sudo, like this:
sudo http_proxy="http://<proxy-host>:<proxy-port" apt-get...

Now you need to shut down the Pi (run sudo halt and wait half a minute or so) and remove the SD card from it. Connect the card to a Linux x86 machine that has a working copy of OpenJFX on it. Then, from To obtain the toolchain, in the OpenJFX directory run:

Code Block
themeMidnight
languagebash
 buildSrc/crosslibs/crosslibs-armv6hf.sh

This will copy files from your Pi's file system to download Debian packages and unpack them into a directory crosslibs at the same level as your OpenJFX working copy. It will then download a cross-compiler for ARM and install it in the same place. When the script has completed you should see:

Code Block
themeMidnight
Done.
You can now replace your SD card in you Raspberry Pi; you won't need to run crosslibs-armv6hf.sh again unless OpenJFX is modified to require additional or updated libraries
.

You are now ready to run a full cross-compile for ARM hard float. The compile command is run on the Linux x86 machine:

Code Block
themeMidnight
languagebash
gradle -PBUILD_NATIVES=true -PCOMPILE_PANGO=true -PCOMPILE_TARGETS=armv6hf
The parameter -PCOMPILE_PANGO=true in the above command tells Gradle to build using the open-source Pango and Freetype font libraries instead of the closed-source font library. This enables you to build a complete JavaFX stack for ARM from the open source repository.

Testing a resulting build

 

When you run with this build you will need to tell Java to use your JavaFX instead of its built-in JavaFX. For example,

 

Code Block
themeMidnight
languagebash
/opt/jdk1.8.0/bin/java \
    -Djava.ext.dirs=build/armv6hf-sdk/rt/lib/ext \
    -jar BrickBreaker.jar

Note that setting java.ext.dirs overrides the location of the JRE extension directory, and so any other jars present in the extension directory of your JRE will not be seen.

As an alternative to java.ext.dirs, you can copy the build result on top of a copy of your JRE installation

Code Block
themeMidnight
languagebash
cp -r build/armv6hf-sdk/rt/lib _path_to_your_JRE