RE: Phoebus on ARM64

["Dudley, David via Tech-talk" <tech-talk at aps.anl.gov>]

 

 

From: Kay Kasemir <kasemirk at ornl.gov>
Sent: Wednesday, August 26, 2026 11:17 AM
To: Dudley, David <dudleyd at frib.msu.edu>; tech-talk at aps.anl.gov
Subject: Re: Phoebus on ARM64

 

[EXTERNAL] This email originated from outside of FRIB

> I re-cloned the archive, went into the pom.xml file, and change the version from 21.0.7, to 21.0.12 (the exact revision installed on my AI-64).

 

We’re talking about the version of two different things.

 

1) The JavaFX graphics lib.

You need a version that happens to be published with linux-aarch64 binaries.

One inconvenient way to check is on https://repo1.maven.org/maven2/org/openjfx/javafx-base/

where 21.0.7 does not but 21.0.12 does include linux-aarch64 binaries.

 

2) The JDK (compiler and runtime).

You need a version that’s compatible with all the sources and the JavaFX lib.

The release notes for JFX21 on https://github.com/openjdk/jfx/tree/master/doc-files say:

JavaFX 21 requires JDK 17 or later.

The remaining phoebus sources are right now in the process of requiring JDK25

(https://github.com/ControlSystemStudio/phoebus/issues/3904), but as we speak (type), JDK21 is good enough.

 

==> Congratulations that JDX21.0.12 contains linux-aarch64 binaries and is compatible with the JDK21.0.12 (same version number but a different thing) that you happen to have.

 

> Ran the run_maven.sh program, it took almost 2 hours, and now I have Phoebus on this machine.

 

Didn’t you just email about the "more than capable” setup? The issue here might be the disk more than the CPU. On my 10 year old Linux host, building it for 4 different architectures takes 40 minutes, so 10 min per arch, not 2 hours.

 

This machine is behind a local firewall,  and the storage used for the build is on an NFS mount.

A fair portion of the time in compilation was taken in downloading all the dependencies and compiling them.  Yes, the process took some time, but I’m not concerned about that.

The completed files run fine, and it executes reasonably well.  Perfect for what I’m working toward.

I just needed something to display status information and allow me to start/stop the operations.  I’m more than happy with the result, just surprised.

 

> What files do I need to copy to the target machine in order to install the thing?

 

Easiest way is to take the whole “phoebus-product” folder.

Or narrow it down:

phoebes.sh

settings_template.ini   (to have an idea what you can put into a settings.ini)

target/lib

target/product*.jar

Or read the phoebus-product/README.md about ‘jpackage'

Or, as is EPICS tradition, start developing a new display tool.

 

 

Why would I want to do that?  You’ve done a really good job on this, and I’m more than happy with the phoebus product, just had problems getting it configured to compile.  Far as I’m concerned… done!

 

-Kay