1
0
mirror of https://github.com/hrfee/jfa-go.git synced 2024-11-22 10:20:11 +00:00

Updated Build (markdown)

Harvey Tindall 2020-08-18 15:28:59 +01:00
parent 928560ed03
commit 447c77c86c

@ -4,11 +4,11 @@ python >= 3.6
pip (to install libsass) pip (to install libsass)
node.js and npm (for bootstrap4/5, autoprefixer, cleancss, mjml, and postcss) node.js and npm (for bootstrap4/5, autoprefixer, cleancss, mjml, and postcss)
``` ```
### Makefile
A Makefile is provided, which requires the `make` command. Simply clone the repository and run `make all` (or `make headless` for a non-interactive mode) to grab all necessary dependencies for go/python/node, compile everything and place the executable and app data inside `build/`.
If you aren't using [goreleaser](https://goreleaser.com), you can instead run `make all` to build, which will place it's output in `build/`. If you don't want to use that either, run each command listed under `before: hooks:` in `.goreleaser.yml`, then `go build`. ### Goreleaser
[goreleaser](https://github.com/goreleaser/goreleaser) is used to publish the packages seen in the release section.
* To generate executables for multiple platforms, run `goreleaser build --snapshot --rm-dist`. They will be stored in `dist/`. The `data` directory must be copied into the same directory as the executable for it to run.
If you are: * To generate package archives that include `data`, run `goreleaser --snapshot --skip-publish --rm-dist`.
* To generate executables, run `goreleaser build --snapshot --rm-dist`. This will place executables in `dist/`. The `data` directory must be copied into the same directory as the executable for it to run.
* To generate package archives, run `goreleaser --snapshot --skip-publish --rm-dist`.