It seems like GraalVM works on compose desktop, bu...

# compose-desktop

[Caleb Kiage]

It seems like GraalVM works on compose desktop, but the gradle plugin doesn't work with the multiplatform plugin so all the configuration has to be done manually 🥲

[Caleb Kiage]

It also runs faster on the computer I used to test. I hadn't even turned on optimizations

[rob42]

@אליהו הדס depends on the scenario I think. For something that's always running, it can be nontrivial. Customers will complain about high background memory usage for sure

[אליהו הדס]

I understand, and why wouldn't it be possible to use kotlin native instead of graalvm? I guess it requires a lot more work

[Caleb Kiage]

Desktop compose uses swing which is Java

[Caleb Kiage]

I figured out how to use the graalvm gradle build tools. Separated out the desktop entry point into its own gradle submodule and used kotlin jvm plugin. Everything works now...I just need to troubleshoot the weirdness with a missing swing class and segfaults on exit. Other than that, the app runs great.

[rob42]

Oh very interesting. I was under the impression that Swing couldn't be built with GraalVM.

[Caleb Kiage]

It can. You just need to run the app with the native image agent attached and collect reflection metadata first. Then use that to build the image

[אליהו הדס]

I found this on github : https://github.com/esp-er/compose-graal-hello

[Caleb Kiage]

The segfaults on exit went away btw, but the missing swing class error is still there. It doesn't seem to affect anything though

[Caleb Kiage]

I looked at the compose-graal-hello while doing this exercise. It uses a different window manager though.

[suresh]

GraalVM support for AWT is limited to linux and windows. No mac mac support - https://github.com/oracle/graal/issues/4124