@smith.adriane If you're interested, I got a conversation here with someone who made this work: https://graalvm.slack.com/archives/CN9KSFB40/p1653139823437649

So I guess we could re-use grease to compile m1 binaries via the ios target

But probably not worth the hassle

I was curious, so I looked to see if the gluon project had config for m1 macs. It looks like it does: • https://github.com/gluonhq/substrate/blob/6c847a37dc6c682d9ee274f114305afac6dfc292/src/main/java/com/gluonhq/substrate/target/AbstractTargetConfiguration.java#L395 • https://github.com/gluonhq/substrate/blob/acb987c67a635081dceee7c5707c8a8cb3f67154/src/main/java/com/gluonhq/substrate/Constants.java#L70 So using the same approach might work.

@borkdude, I did check out the graalvm thread you linked. It was quite a trip.

It does seem like the thread came to a similar conclusion. It's possible to cross-compile, but it's probably just easier to wait until github actions support m1.

I do think it would be interesting to better understand the cross-compilation pipeline. llvm has a bunch of targets (like wasm) that could be interesting.