-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MacOS support #114
Comments
This issue appears to be stale because it has been open 30 days with no activity. This issue will be closed in 7 days unless |
FYI: Via Eclipse Temurin there are (untested) Mac OS X static-libs now. JDK 17: https://github.com/adoptium/temurin17-binaries/releases/tag/jdk-17.0.1%2B12 |
Anything on this getting traction. Definitely a good thing to move forward with this. |
No, not yet. At the moment it looks like we would need to rely on GH actions to provide MacOS releases while Linux and Windows releases are built and tested internally. @Karm WDYT? |
Relying on doing Mac releases on GH actions is not an option, so there are no MacOS releases planned at the time of writing. When (rather than if) that changes, we will update this issue 👍 |
Any updates? |
I don't think our stance has changed on this one, sorry. |
graalvm/mandrel-packaging#339 enables building Mandrel for MacOS x86. Next step is figuring out if it works on M1 as well. Last, we will need some infrastructure as mentioned in #114 (comment). |
@zakkak Thx for the addition to the mandrel-packaging.
My note is redundant. I am sorry. I managed to miss the end of your previous comment 👍 |
Mandrel team has the M2 Pro systems now, so we will revisit this issue presently. |
We have preview builds, now in testing...
|
MacOS builds should be relatively easy to produce and test, however, there are still some roadblocks in our way.
To my knowledge these are:
mandrel-packaging
is known to have some issues on MacOS (See Packaging output not working on macOS mandrel-packaging#42)Please comment bellow if you are aware of any additional issues.
The text was updated successfully, but these errors were encountered: