kevinschoon-pomo/Makefile

VERSION ?= $(shell git describe --tags 2>/dev/null)
ifeq "$(VERSION)" ""
	VERSION := UNKNOWN
endif

LDFLAGS=\
	-X github.com/kevinschoon/pomo/pkg/internal.Version=$(VERSION)

.PHONY: \
	test \
	docs \
	pomo-build \
	readme \
	bin/pomo

default: bin/pomo test

clean:
	[[ -f bin/pomo ]] && rm bin/pomo || true

bin/pomo:
	cd cmd/pomo && \
	go build -ldflags '${LDFLAGS}' -o ../../$@

test:
	go test ./...
	go vet ./...

install:
	go install ./cmd/...

docs: www/data/readme.json
	cd www && hugo -d ../docs

www/data/readme.json: www/data README.md
	cat README.md | python -c 'import json,sys; print(json.dumps({"content": sys.stdin.read()}))' > $@

www/data bin:
	mkdir -p $@
fix version 2018-01-21 16:38:17 +01:00			`VERSION ?= $(shell git describe --tags 2>/dev/null)`
			`ifeq "$(VERSION)" ""`
			`VERSION := UNKNOWN`
			`endif`
refactor run loop, add simple libnotify support, improve notifications, binpack tomato image 2018-01-21 11:35:03 +01:00
restructure project into modules 2020-09-08 18:35:47 +02:00			`LDFLAGS=\`
update Makefile 2021-07-29 03:36:33 +02:00			`-X github.com/kevinschoon/pomo/pkg/internal.Version=$(VERSION)`
restructure project into modules 2020-09-08 18:35:47 +02:00
refactor run loop, add simple libnotify support, improve notifications, binpack tomato image 2018-01-21 11:35:03 +01:00			`.PHONY: \`
add docs 2018-01-22 16:07:58 +01:00			`test \`
			`docs \`
add new build environment for cross compile 2019-03-17 20:10:28 +01:00			`pomo-build \`
fix issue where interface can block Fixed an issue where the UI can block when certain key combinations are pressed in different states. An alternative and more robust approach would likely be to re-write the runner code as a finite state machine, however these quick fixes work okay. Additionally cleaned up some spacing in console messages and added a CREATED state which is the default state of a pomodoro. 2022-05-30 21:59:03 +02:00			`readme \`
			`bin/pomo`
refactor run loop, add simple libnotify support, improve notifications, binpack tomato image 2018-01-21 11:35:03 +01:00
build before running tests 2022-05-29 03:24:10 +02:00			`default: bin/pomo test`
build bin/pomo by default 2021-10-10 17:32:10 +02:00
			`clean:`
			`[[ -f bin/pomo ]] && rm bin/pomo \|\| true`
restructure project into modules 2020-09-08 18:35:47 +02:00
build before running tests 2022-05-29 03:24:10 +02:00			`bin/pomo:`
restructure project into modules 2020-09-08 18:35:47 +02:00			`cd cmd/pomo && \`
			`go build -ldflags '${LDFLAGS}' -o ../../$@`
update Makefile 2018-07-12 21:04:02 +02:00
fix version 2018-01-21 16:38:17 +01:00			`test:`
			`go test ./...`
add vet to test 2018-01-26 16:34:21 +01:00			`go vet ./...`
fix version 2018-01-21 16:38:17 +01:00
adding install target to Makefile 2022-05-29 03:31:46 +02:00			`install:`
			`go install ./cmd/...`

add installer script 2019-02-10 21:39:45 +01:00			`docs: www/data/readme.json`
rm release helpers Binary releases suck to maintain and upstream package maintainers, e.g. Debian, Brew, etc. should be preferred. 2021-07-29 02:00:16 +02:00			`cd www && hugo -d ../docs`
Makefile: add missing dependency for `www/data' 2018-02-01 10:00:51 +01:00
Makefile: split the target from the PHONY rule A PHONY rule is executed always. The target of the `readme' rule is to create the `www/data/readme.json', which depends only on `README.md'. If we specify these dependencies separately, make(1) won't build the `readme.json', if it's not necessary. And yet, we can refer to this creation by typing `make readme'. 2018-02-01 10:10:24 +01:00			`www/data/readme.json: www/data README.md`
Makefile: shorten recipe using default target var 2018-02-01 10:13:39 +01:00			`cat README.md \| python -c 'import json,sys; print(json.dumps({"content": sys.stdin.read()}))' > $@`
add installer script 2019-02-10 21:39:45 +01:00
Makefile: explicitly create bin/, if necessary Most of the go(1) tools will create the missing directory. Yet, it is better to define this dependency explicitly to make(1), to avoid unnecessary surprises. Another useful feature of make(1) is the multiple targets per rule. This way, we can have the same action and it is the target the variable of the rule, anymore. 2018-02-01 10:06:05 +01:00			`www/data bin:`
Makefile: add missing dependency for `www/data' 2018-02-01 10:00:51 +01:00			`mkdir -p $@`