4 ms·

Massive thanks for this. I've opened an issue to ensure I improve this: https://github.com/timeseries/qstudio/issues/54 https://github.com/timeseries/qstudio/is

Massive thanks for this. I've opened an issue to ensure I improve this: https://github.com/timeseries/qstudio/issues/54 https://github.com/timeseries/qstudio/issues/54 To be honest I've delayed improving Mac as I don't use the platform myself so I don't know how people usually install java apps on mac. I guess it's time I dove in and properly solved this. With the upcoming windows spyware I may have to move platform anyway.

whartung 2y ago
This could well be a good opportunity to dig into jlink and jpackage and use that to build native installs for the different platforms, bundling the JDK. In my experiments, I was able to pull it off for Mac and Windows, but Linux was still a bit wild west as to how to properly package it (for me), so they just get a fat jar. It's doable, I just didn't do it. It helps if you use the Java modularity to trim down the runtime. I was able to distribute my FX app (which requires platform specific binaries) that way.
brsiegel 2y ago
JavaPackager as you're already using should work, you would just need to build the Mac packages on a Mac build agent. For something more future-proof and performant, GraalVM native images (https://www.graalvm.org/latest/reference-manual/native-image/ https://www.graalvm.org/latest/reference-manual/native-image...) seem to be the future of native packaging for JVM applications.