Raspberry PI graalvm

[odbuser2]

Is there an equivalent of graalvm-svm-linux-20.1.0-ea+28 for raspberry pi 64-bit (ubuntu)?

[odbuser2]

Related to: https://github.com/gluonhq/client-maven-plugin/issues/157

I think the client-samples readme: https://github.com/gluonhq/client-samples/blob/master/README.md Is having trouble being in sync with: https://github.com/gluonhq/client-maven-plugin/blob/master/README.md

The samples currently use:

openjfx/javafx-maven-plugin 0.0.4
gluonhq/client-maven-plugin 0.1.23

and contain specific instructions beyond the client-maven-plugin instructions (but out of date?)

[abhinayagarwal]

Hi @odbuser2,

Can you clarify which part of the readme in client-samples needs update?

[odbuser2]

I don't think I have a good, short answer for this... the instructions do not mention raspberry pi at all. If it falls under the linux instructions, then they should be clear to reference 32-bit vs 64-bit.

In general, I think all of the following pages need to be improved so that users do not get lost. They all contain some procedural instructions but none of them start with the bigger picture. I don't know how much influence/control you have over the various pages below, but here is my quick take:

https://github.com/openjfx/javafx-maven-plugin A Maven plugin for projects that depend on OpenJFX modules. The plugin helps manage the javafx module dependencies and related settings. In addition, the plugin includes jlink support to build a custom runtime image.

• note, this is partly why that plugin is confusing... jlink isn't specific to javafx so it's as if there should have been a plugin for Java that includes jlink support that this plugin uses/depends on.

https://github.com/gluonhq/client-maven-plugin A Maven plugin for building native code from projects that depend on OpenJFX to deploy to various platforms: -OSX (.app, pkg) -iOS (ipa) -Android (apk) -Windows (exe, msi) -Raspberry PI (arm64 and arm32 binaries) -Linux (x86-64, arm32, arm64 deb and rpm)

• note the above is just an example off the top of my head - it's important to clarify the arm situation... lots of people waste time on trying this on a raspberry pi or other arm based hardware only to find that some or all of openjdk, graal, javafx libraries, plugins don't work.

https://github.com/gluonhq/client-samples/ Samples that use javafx-maven-plugin and client-maven-plugin.

• note the documentation here should only reference (not re-document) the readme's of the plugin versions used and describe each example.

One may argue that https://openjfx.io and https://www.gluonhq.com are the appropriate places for the actual documentation... maybe so but both sites are a mess (sorry to be blunt). Some of the client-maven-plugin is documented there but it's often out of date or really hard to get to. It's https://docs.gluonhq.com/client/ but try getting there from the main site. Both sites suffer from poor web site design (again forgive the bluntness - I'm very aware and appreciative of all of the work that has been put forth to open and improve javafx. I would hate to see that effort hampered unnecessarily with confusing documentation.

[abhinayagarwal]

Hi @odbuser2,

Critical feedback is always a good source of improvement.

We are all aware of the mess openjfx-docs has been. There have been multiple complains on the openjfx-dev mailing list. The most pain point of the website is that its all HTML, CSS, JS, which makes it difficult to maintain and improve. I have therefore, started a migration project to improve it. Once its ready, I will make a pull request to openjfx/openjfx-docs. It is a work in progress but any feedback / help is most welcome.

note, this is partly why that plugin is confusing... jlink isn't specific to javafx so it's as if there should have been a plugin for Java that includes jlink support that this plugin uses/depends on.

I agree but I do not see an easy way out of this. Since the removal of JavaFX from the JDK, there have been so many questions related to "Distribution of JavaFX" or "JavaFX jar doesn't work". The answer to this is not easy and an alternative is to create runtime images using Jlink. This was the only reason Jlink was included in the plugin.

note the above is just an example off the top of my head - it's important to clarify the arm situation... lots of people waste time on trying this on a raspberry pi or other arm based hardware only to find that some or all of openjdk, graal, javafx libraries, plugins don't work.

Can you open an issue in the repository and add your suggestion as a comment? We will try our best to clear things up.

note the documentation here should only reference (not re-document) the readme's of the plugin versions used and describe each example.

This is an excellent advice. It will also save a lot of duplicated effort. We will work on this.

[odbuser2]

Can you open an issue in the repository and add your suggestion as a comment? We will try our best to clear things up.

Which repository?

[abhinayagarwal]

Which repository?

gluonhq/substrate