shard-ameba/shard.yml

name: ameba
version: 1.5.0

authors:
  - Vitalii Elenhaupt <velenhaupt@gmail.com>

targets:
  ameba:
    main: src/cli.cr

scripts:
  # TODO: remove pre-compiled executable in future releases
  postinstall: shards build -Dpreview_mt

executables:
  - ameba
  - ameba.cr

crystal: "~> 1.9.0"

license: MIT
Hello, Ameba 2017-10-26 16:46:58 +00:00			`name: ameba`
Bump v1.5.0 2023-07-28 19:40:22 +00:00			`version: 1.5.0`
Hello, Ameba 2017-10-26 16:46:58 +00:00
			`authors:`
			`- Vitalii Elenhaupt <velenhaupt@gmail.com>`

Use shards build command 2018-04-11 10:44:02 +00:00			`targets:`
			`ameba:`
			`main: src/cli.cr`

Ameba cli & binary (#7) * Ameba cli & binary * -1 when ameba found issues * Add postscript to shard.yml * Correct postinstall * Remove targets * Try executables 2017-11-01 15:21:41 +00:00			`scripts:`
Let it be extensible (#112) 2019-07-18 10:53:04 +00:00			`# TODO: remove pre-compiled executable in future releases`
Make `postinstall` portable Using `shards build` directly instead of `make build` improves portability a lot. This should basically "just work" almost anywhere (including Windows). No need for `make` to be available and makefile compatibility doesn't matter either. 2023-07-15 08:10:42 +00:00			`postinstall: shards build -Dpreview_mt`
Add executables back 2019-05-19 17:46:40 +00:00
			`executables:`
			`- ameba`
Utilize shards' `executables` There's no need for copying the executables manually (which happens in both makefile targets `bin` and `run_file`). Shards' `executables` takes care of that. The makefile targets could potentially be dropped as well, I don't think there would be other uses case for those. 2023-07-15 08:07:15 +00:00			`- ameba.cr`
Change supported crystal version to >= 0.35.0 2020-12-01 12:13:30 +00:00
Bump v1.5.0 2023-07-28 19:40:22 +00:00			`crystal: "~> 1.9.0"`
Change supported crystal version to >= 0.35.0 2020-12-01 12:13:30 +00:00
			`license: MIT`