-
Notifications
You must be signed in to change notification settings - Fork 103
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
Offer mechanism to build a distributable with bundled JRE when using Gradle #543
Comments
I've written this for my own project. Maybe it could be leveraged. |
Here's what I could find. It's been a while, so I'm not sure if everything is is used. It doesn't download jre's by itself. Those I downloaded manually. There are also some hardcoded paths in there:
|
I guess we need to start by finding a concept, because just out of my head I can remember a few different solutions:
And they also vastly differ by the environment required (standalone, steam, ...), configuring jvm properties, keeping them updated, download bundle size (e.g. if it's always included in every patch versus a slim executable searching system jvms or downloading on demand) |
Its actually using launch4j. I believe I opted for not bundling the jre in the exe though |
Offer mechanism to build a distributable with bundled JRE when using Gradle. Ant has this, in the SDK. But not with Gradle. I always kinda figured that Gradle users can figure this one out themselves as one is supposed to anyway tweak around with
gradle.build
manually. This could be a good feature offered by the SDK.If there is a good single solution to rule them all, that would be super. The jME initialization wizard currently does includes one solution in its generated script. That would be the easiest solution to just copy that. If there is no single solution, I guess we would need to ask this in the Gradle wizard that what kind of release one is trying to do and figure out which one to use.
One challenge after that is to have the user understand how to trigger this release build. I'm sure it shouldn't happen on every
run
.Reference (and options):
https://hub.jmonkeyengine.org/t/how-to-deploy-a-jme-project-as-executable-with-the-integrated-jvm-using-jme-3-6-and-above/47182/
The text was updated successfully, but these errors were encountered: