buildkit/Makefile

DESTDIR=/usr/local

binaries: FORCE
	hack/binaries

images: FORCE
# moby/buildkit:local and moby/buildkit:local-rootless are created on Docker
	hack/images local moby/buildkit

install: FORCE
	mkdir -p $(DESTDIR)/bin
	install bin/* $(DESTDIR)/bin

clean: FORCE
	rm -rf ./bin

test:
	./hack/test integration gateway dockerfile

lint:
	./hack/lint

validate-vendor:
	./hack/validate-vendor

validate-generated-files:
	./hack/validate-generated-files

validate-all: test lint validate-vendor validate-generated-files

vendor:
	./hack/update-vendor

generated-files:
	./hack/update-generated-files

.PHONY: vendor generated-files test binaries images install clean lint validate-all validate-vendor validate-generated-files
FORCE:
Makefile: add `install` and `clean` Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp> 2017-12-13 04:34:55 +00:00			`DESTDIR=/usr/local`
hack: add binary targets Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2017-06-19 23:10:09 +00:00
hack: update test dockerfiles to buildkit Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2018-10-02 17:03:32 +00:00			`binaries: FORCE`
			`hack/binaries`
hack: add binary targets Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2017-06-19 23:10:09 +00:00
Makefile: new target: images Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp> 2019-03-01 08:04:59 +00:00			`images: FORCE`
			`# moby/buildkit:local and moby/buildkit:local-rootless are created on Docker`
			`hack/images local moby/buildkit`

Makefile: add `install` and `clean` Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp> 2017-12-13 04:34:55 +00:00			`install: FORCE`
			`mkdir -p $(DESTDIR)/bin`
hack: update test dockerfiles to buildkit Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2018-10-02 17:03:32 +00:00			`install bin/* $(DESTDIR)/bin`
Makefile: add `install` and `clean` Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp> 2017-12-13 04:34:55 +00:00
			`clean: FORCE`
			`rm -rf ./bin`

cachemanager: add contructor Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2017-05-26 00:16:32 +00:00			`test:`
hack: update test dockerfiles to buildkit Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2018-10-02 17:03:32 +00:00			`./hack/test integration gateway dockerfile`
cachemanager: add contructor Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2017-05-26 00:16:32 +00:00
hack: add binary targets Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2017-06-19 23:10:09 +00:00			`lint:`
			`./hack/lint`
support building on windows (no functional worker yet) Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp> 2017-07-12 05:08:53 +00:00
hack: add binary targets Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2017-06-19 23:10:09 +00:00			`validate-vendor:`
			`./hack/validate-vendor`

Validation and (controlled) generation for go generate'd files. Modelled after the vendor support provide a validator and an updator for files produced by `go generate` (which today just means `.pb.go`). Main difference from the vendor support is that we are no longer simply nuking and replacing a single directory, so I ended up hardcoding `.pb.go` in a bunch of places which I don't like but cannot see a way around which doesn't risk nuking people's other local changes. The generated files are placed in an unpacked form in a `FROM scratch` container for update. Use a subdirectory and `tar --strip-components` (portable to MacOS and Linux according to `tar(1)`) since trying to do a `docker export` of just the root ends up adding `.dockerenv`, `sys`, `proc` and `dev` to the source tree. The validate container is not `FROM scratch` because we want `cat`. The run in `frontend/gateway/pb/generate.go` was missing an include so fix that. The versions of `protoc` and the gogo plugins were chosen to regenerate the existing code as closely as possible. The updates to `.pg.go` here are all the result of regenerating with go1.9 which fixed https://github.com/golang/go/issues/17663 and replaced an invalid timestamp in the gzip header of the data encoded in `fileDescriptor`, and adopted a new standard for marking generated files. Finally, I noticed that my `docker run`s were missing an `--rm` which I inherited from `validate-vendor`, so fix all those. Closes: #322 Signed-off-by: Ian Campbell <ijc@docker.com> 2018-03-26 10:52:36 +00:00			`validate-generated-files:`
			`./hack/validate-generated-files`

			`validate-all: test lint validate-vendor validate-generated-files`
hack: add binary targets Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2017-06-19 23:10:09 +00:00
vendor: add vendoring script Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> 2017-05-25 23:26:11 +00:00			`vendor:`
			`./hack/update-vendor`
support building on windows (no functional worker yet) Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp> 2017-07-12 05:08:53 +00:00
Validation and (controlled) generation for go generate'd files. Modelled after the vendor support provide a validator and an updator for files produced by `go generate` (which today just means `.pb.go`). Main difference from the vendor support is that we are no longer simply nuking and replacing a single directory, so I ended up hardcoding `.pb.go` in a bunch of places which I don't like but cannot see a way around which doesn't risk nuking people's other local changes. The generated files are placed in an unpacked form in a `FROM scratch` container for update. Use a subdirectory and `tar --strip-components` (portable to MacOS and Linux according to `tar(1)`) since trying to do a `docker export` of just the root ends up adding `.dockerenv`, `sys`, `proc` and `dev` to the source tree. The validate container is not `FROM scratch` because we want `cat`. The run in `frontend/gateway/pb/generate.go` was missing an include so fix that. The versions of `protoc` and the gogo plugins were chosen to regenerate the existing code as closely as possible. The updates to `.pg.go` here are all the result of regenerating with go1.9 which fixed https://github.com/golang/go/issues/17663 and replaced an invalid timestamp in the gzip header of the data encoded in `fileDescriptor`, and adopted a new standard for marking generated files. Finally, I noticed that my `docker run`s were missing an `--rm` which I inherited from `validate-vendor`, so fix all those. Closes: #322 Signed-off-by: Ian Campbell <ijc@docker.com> 2018-03-26 10:52:36 +00:00			`generated-files:`
			`./hack/update-generated-files`

Makefile: new target: images Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp> 2019-03-01 08:04:59 +00:00			`.PHONY: vendor generated-files test binaries images install clean lint validate-all validate-vendor validate-generated-files`
support building on windows (no functional worker yet) Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp> 2017-07-12 05:08:53 +00:00			`FORCE:`