packr VS bach

LibGDX has their own way of doing this: https://github.com/libgdx/packr

Go to https://github.com/libgdx/packr, download a release on the releases page.

> they quickly realize they need Windows, and a Mac, and maybe Linux just to make packages that their friends can run

And when they test it on Windows they'll realize that the launcher that jpackage creates does something weird on startup (involving relaunching itself it seems?) that makes Windows display a busy cursor for a while after the program has launched, so they have to forget about jpackage and redo it all with something like Packr [1] and Wix# [2]...

[1] https://github.com/libgdx/packr

[2] https://github.com/oleg-shilo/wixsharp

You may also want to bundle a JVM with your game install so you don't have to rely on the user having Java installed. You can use libGDX-packr or jpackage for this. If you have any trouble, feel free to hit me up.

Try packr: https://github.com/libgdx/packr

Then see if this could work for you: https://github.com/libgdx/packr

https://stackoverflow.com/questions/2258932/embed-a-jre-in-a-windows-executable has some suggestions, one of which is https://github.com/libgdx/packr if you embed your Rust library within a JAR

If you are on a lower version I have made good experiences with the packr tool.

Projects like bach do serve to make the case that, if the resolution/build library piece were filled in, building and maintaining a multi module or multi-whatever project using just javac/jar/etc with Java build programs would be practical.

Have you heard about/looked into bach? It's a build-tool based mostly around pumping the output of one jdk tool into another.

Not quite that, but bach is a build tool trying to simplify that java build process.