Create Windows MSI installer #108
Assignees
Milestone
Comments
This was referenced Oct 3, 2014
cbeams
added a commit
that referenced
this issue
Oct 3, 2014
The plugin's jfx* tasks tie into the normal Gradle build lifecycle, such that `gradle build` will now generate executables and installers according to the OS on which the build is being run. These files are output to the `build/distributions` directory. Installers work as expected OS X and Linux at this point. Windows installers do build, but a very particular configuration is necessary on the Windows machine doing the building (this configuration is to be documented in #109). However, even when the configuration is in place and the MSI installer is successfully built, there is still a fatal error at installer execution time relating to a missing msvp100.dll file. See details at https://bitbucket.org/shemnon/javafx-gradle/issue/43. An issue has been created to track this from the Bitsquare side as well--see #108. The changes made in this commit are based on on the samples at http://bitbucket.org/shemnon/javafx-gradle and the article at http://jaxenter.com/tutorial-a-guide-to-the-gradle-javafx-plugin-46270.html The gradle/javafx.gradle file is copied directly from the sources in the bitbucket repository above, as is apparently the convention (not sure why this isn't part of the plugin itself, but that's a question to be addressed later). Resolves #66, #100 See #108, #109
3 tasks
|
Superseded by #243. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When integrating the JavaFX Gradle plugin to build native installers for Bitsquare (#66), an issue was encountered on Windows where, upon attempting to execute the MSI created by the plugin, a fatal error is raised regarding a "missing msvp100.dll" file.
This has been documented in detail at https://bitbucket.org/shemnon/javafx-gradle/issue/43. This issue is here to track progress there from our side.
Note that this DLL problem is fixed in JDK 8u40, but that's not due out until March 2015. We'll need to find a way to work around this earlier than that.
The text was updated successfully, but these errors were encountered: