OK, absolute amazement.
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).
Ran the run_maven.sh program, it took almost 2 hours, and now I have Phoebus on this machine.
Now for the question…
What files do I need to copy to the target machine in order to install the thing? Do I need both the product-*-SNAPSHOT.jar file as well as the product-*-SHAPSHOT.tar.gz files, or the entire contents of the directory?
David
From: Kay Kasemir <kasemirk at ornl.gov>
Sent: Tuesday, August 25, 2026 11:41 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
The JavaFX graphics lib doesn’t always include binaries for linux-aarch64.
For example, version 21.0.7 only has ..-linux.jar
https://repo1.maven.org/maven2/org/openjfx/javafx-base/21.0.7/
Version 23 does include ..-linux-aarch64.jar,
https://repo1.maven.org/maven2/org/openjfx/javafx-base/23/
Fundamentally you pick the version in the phoebus/pom.xml file by changing this line:
<openjfx.version>21.0.7</openjfx.version>
.. but changing the JFX version might have other side effects.
In general, it’s probably not the best idea to include the display (and alarm server, archive, …) in the IOC.
EPICS is a distributed system where the IOCs perform the sampling and certain control aspects, displays then run on client machines and so on.
----
Has there been any thought of porting the Phoebus CSS software to ARM64?
I have a little BeagleBoard AI-64 system running Linux and XFCE that I’d like to get into a stand-alone test system. I’ve got the IOC handled, all the drivers managed, and I’m down to display software.
Building Phoebus fails miserably.
Later-
David