Skip to content
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

Use launch4j Gradle plugin for Windows builds #48

Merged
merged 3 commits into from Jan 3, 2023

Conversation

weyfonk
Copy link
Contributor

@weyfonk weyfonk commented Nov 26, 2022

This is a step towards easier, automated builds:

  • vifeco uses a Gradle plugin named gradle-launch4j 1 to prevent launch4j
    from requiring a separate installation.
  • That plugin uses relative paths in its config for the build .jar and the favicon, as well as a variable for the build version number

Corentin Néau and others added 3 commits November 26, 2022 23:06
A Gradle plugin named gradle-launch4j [1] is used to prevent launch4j
from requiring a separate installation.

[1]: https://github.com/TheBoegl/gradle-launch4j
This fixes the file name from `lauch4j_config.xml` to
`launch4j_config.xml`.
Launch4j config directives using absolute paths, dependent on the build
machine, are replaced with launch4j plugin configuration using relative
paths.
By the same token, a version number variable is used to reduce the
number of manual operations needed to prepare new releases.

`vifeco.exe` can be compiled via `.\gradlew createExe` on Windows and
`gradle createExe` on other systems (tested building on Mac OS then
running on Windows, with encouraging results).
@davidmaignan davidmaignan merged commit 77214b0 into LAEQ:master Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants