Thanks to Sravan Lakkimsetti for the awesomely proactive help,
thanks to Gordon Hollingworth of Raspberry Pi for providing access
to aarch64 hardware, and thanks to Mikaël Barbero for hooking it
up to the JustJ CI instance, we now have JustJ JREs for
Linux aarch64 available.
The p2 update site for these Java 15.0.1 JREs are
available here:
https://download.eclipse.org/justj/jres/15/updates/milestone/latest
The non-debug-stripped variants of these JREs
include a src.zip so JDT supports source debugging using
these JREs, thanks to the contributions of Alex Boyko.
I've
built sample products, effectively the Eclipse SDK,
version 4.18, with JustJ 15.0.1 and Oomph included:
https://download.eclipse.org/justj/www/download.eclipse.org.php?file=sample-products/202010270600
So I've been able to test that the Eclipse SDK
works properly on Windows, i.e., that JDT can debug step
into JustJ JRE libraries and see the sources automatically.
Also note that the generation of the JREs actually launches
Eclipse with that JRE, so each JRE has minimally been tested
to confirm that Eclipse does launch using that JRE on each
operating system and hardware combination.
I would suggest using https://download.eclipse.org/justj/jres/15/updates/milestone/latest
for the next EPP milestone. I'll produce a released
version of these after the next EPP milestone has
tested them on all platforms.
Regards,
Ed
On 26.10.2020 05:50, Ed Merks wrote:
I see
that the EPP packages now include aarch64 variants:
https://www.eclipse.org/downloads/packages/release/2020-12/m1
The Java 15 JDK also supports aarch64:
https://download.java.net/java/GA/jdk15.0.1/51f4f36ad4ef43e39d0dfdbaf6549e32/9/GPL/openjdk-15.0.1_linux-aarch64_bin.tar.gz
This Bugzilla asks JustJ to provide support for aarch64:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=566640
Without that support, the aarch64 EPP packages that include a
JustJ JRE will not actually contain a fragment with an actual JRE.
Making this work primarily involves making this script work
natively on aarch64:
https://git.eclipse.org/c/justj/justj.git/tree/releng/org.eclipse.justj.releng/build-jre.sh
But I cannot test how to implement that locally.
Ultimately the JustJ ci instance will need yet another dedicated
agent/executor:
https://ci.eclipse.org/justj/
I don't see any mention of aarch64 here:
https://wiki.eclipse.org/CBI#What.27s_provided.3F
An additional dedicated agent costs one "resource pack", so I will
need to hunt down someone to donate yet another resource pack.
https://docs.google.com/spreadsheets/d/e/2PACX-1vQGhAH2b-BdoW5MAgmCG8NLfAjZMe7fIgsYNtUMREmIeAXmAPjDkZOx1OHaz0-INS51TGN41C3zcbI8/pubhtml?gid=746314272&single=true
The two current dedicated agents (for MacOS and Windows) are
sponsored by Deutsches Zentrum fuer Luft- und Raumfahrt:
https://docs.google.com/spreadsheets/d/e/2PACX-1vQGhAH2b-BdoW5MAgmCG8NLfAjZMe7fIgsYNtUMREmIeAXmAPjDkZOx1OHaz0-INS51TGN41C3zcbI8/pubhtml?gid=832654757&single=true
Assuming such an agent type exists, I've asked for one:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=568233
But the more fundamental question is, does anyone care? And even
more fundamentally, does any one care enough to contribute? I
don't actually personally care about aarch64.
Regards,
Ed
_______________________________________________