kevinschoon-pomo/Makefile

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

.PHONY: \
	all \
	test \
	docs \
	readme \
	release

all: bin/pomo

clean: 
	-rm -fv bin/* docs/*

bindata.go:
	go-bindata -pkg main -o $@ tomato-icon.png

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

release: bin bindata.go
	go build -ldflags "-X main.Version=$(VERSION)" -o bin/pomo-$(VERSION)-linux

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

readme: www/data/readme.json

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/readme.json
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
			`.PHONY: \`
fix version 2018-01-21 16:38:17 +01:00			`all \`
add docs 2018-01-22 16:07:58 +01:00			`test \`
			`docs \`
update Makefile 2018-01-22 17:27:35 +01:00			`readme \`
			`release`
refactor run loop, add simple libnotify support, improve notifications, binpack tomato image 2018-01-21 11:35:03 +01:00
			`all: bin/pomo`

			`clean:`
Makefile: simplify `clean' rule There is a special rule in make(1) to denote that we don't care about the result of a command. Additionally, we can also instruct rm(1) not to complain when it didn't find a file/directory to remove. As a final touch, there is no point of having 2 shell executions to remove 2 or more files. We can compress these 2 recipes into a single one. Reference: https://www.gnu.org/software/make/manual/html_node/Errors.html 2018-02-01 09:53:16 +01:00			`-rm -fv bin/* docs/*`
refactor run loop, add simple libnotify support, improve notifications, binpack tomato image 2018-01-21 11:35:03 +01:00
			`bindata.go:`
			`go-bindata -pkg main -o $@ tomato-icon.png`

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
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			`release: bin bindata.go`
update Makefile 2018-01-22 17:27:35 +01:00			`go build -ldflags "-X main.Version=$(VERSION)" -o bin/pomo-$(VERSION)-linux`
add hugo sources 2018-01-22 15:59:03 +01:00
update Makefile 2018-01-22 17:27:35 +01:00			`docs: readme`
add docs 2018-01-22 16:07:58 +01:00			`cd www && hugo -d ../docs`

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