jMonkeyEngine / jMonkeyEngine/jmonkeyengine
Prepare a Graal-based iOS AOT Compilation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
Due to the sunset of bintray, the SDK cannot easily access the avian build anymore, that I manually did painfully on a Mac OS X machine and stored it on bintray.
Now while I could try to get this running on Github Actions, it's still discontinued and based on java 7.
Instead Graal provides an industry grade support for general AOT compilation and should be supported for a much longer time.
The scope of this issue is to determine the steps required to get a working iOS Build and potentially yield further issues to implement engine-side improvements for that.
I guess @Ali-RS already had Graal Native image running?
Edit: Potentially even running some example in Github Actions to verify all the issues from https://hub.jmonkeyengine.org/t/native-compilation-graalvm-native-image/43820/ don't arise
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing Avian-based iOS build process, the Graal Native Image discussion, and the referenced GitHub Actions approach. Determine whether a working Graal-based iOS build can be produced and verified in GitHub Actions; document the required steps and any engine-side follow-up issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, ios, java
- Domain
- build-system, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100