On 3/30/23 10:44 AM, Kevin Rushforth wrote:
No, I didn't see this. Yes, this seems a reasonable request.
Actually, I was going to submit a pull request to get my patch for this
change integrated (after the reproducible builds PR is merged). I've
tested JavaFX on all six architectures for Linux: amd64, arm64, armhf,
i386, ppc64el, and even s390x! It works on all platforms except for the
software rendering on an IBM mainframe (s390x), but even that could be
fixed someday. The bug is due to the mainframe being big-endian instead
of little-endian.
My tests of Java and JavaFX on all Linux architectures are posted here:
Status
https://github.com/jgneff/openjdk/discussions/11
The Java bug on an s390x virtual machine should be fixed by now, too,
but I haven't yet had a chance to test the QEMU fix.
John
On 3/30/2023 10:34 AM, Glavo wrote:
Did I successfully send this email to the mailing list?
On Wed, Mar 29, 2023 at 10:18 PM Glavo <zjx001...@gmail.com> wrote:
Hi everyone,
Currently OpenJFX's build script asserts the CPU architecture and
does not allow building on unknown architectures.
But in fact OpenJFX is cross-platform, it can actually be built
and run on almost all architectures.
The only hurdle was the asserts in the build scripts, and John
made it compile on the s390x and ppc64el platforms with a simple
patch[1].
I'm working on some niche architectures (such as MIPS64el and
RISC-V) and I need to compile OpenJFX for them.
I understand the need to warn users that there may be unknown
issues building on these architectures,
and I don't have time to do regular testing to ensure that OpenJFX
works on these architectures.
But I wish it was simpler to build OpenJFX on these architectures.
So can we add a gradle property to have the build script skip the
assertion on the architecture,
thus allowing us to build OpenJFX on unknown architectures without
modifying any files?
Glavo
[1]:
https://github.com/jgneff/openjfx/blob/candidate/snap/local/allow-armhf-i386-ppc64el-s390x.patch
