go/cmd/vet/Makefile

# Copyright 2010 The Go Authors. All rights reserved.
# Use of this source code is governed by a BSD-style
# license that can be found in the LICENSE file.

# Assumes go/types is installed
test testshort:
	go build
	$(GOROOT)/test/errchk ./vet -printfuncs='Warn:1,Warnf:1' test_*.go test_*.s

# Install command where the go tool can find it.
install:
	go build -o _vet
	cp _vet $(GOROOT)/pkg/tool/$(GOOS)_$(GOARCH)/vet
	rm -f _vet
go.tools: add go/types, ssa, and cmd/vet They will be deleted from their current homes once this has landed. Changes made to import paths to make the code compile, and to find errchk in the right place in cmd/vet's Makefile. TODO in a later CL: tidy up vet. R=golang-dev, gri CC=golang-dev https://golang.org/cl/9495043 2013-05-17 14:20:39 -06:00			`# Copyright 2010 The Go Authors. All rights reserved.`
			`# Use of this source code is governed by a BSD-style`
			`# license that can be found in the LICENSE file.`

			`# Assumes go/types is installed`
			`test testshort:`
go.tools/cmd/vet: update to new go/types package Now that it's in the same repository as the go/types package we can delete the mechanism to build it without type checking. Add a make rule to install it where the go tool can find it. Why doesn't "go install" take a -o flag? R=gri CC=gobot, golang-dev https://golang.org/cl/9526043 2013-05-20 13:20:05 -06:00			`go build`
go.tools: add go/types, ssa, and cmd/vet They will be deleted from their current homes once this has landed. Changes made to import paths to make the code compile, and to find errchk in the right place in cmd/vet's Makefile. TODO in a later CL: tidy up vet. R=golang-dev, gri CC=golang-dev https://golang.org/cl/9495043 2013-05-17 14:20:39 -06:00			`$(GOROOT)/test/errchk ./vet -printfuncs='Warn:1,Warnf:1' test_.go test_.s`

go.tools/cmd/vet: update to new go/types package Now that it's in the same repository as the go/types package we can delete the mechanism to build it without type checking. Add a make rule to install it where the go tool can find it. Why doesn't "go install" take a -o flag? R=gri CC=gobot, golang-dev https://golang.org/cl/9526043 2013-05-20 13:20:05 -06:00			`# Install command where the go tool can find it.`
			`install:`
			`go build -o _vet`
			`cp _vet $(GOROOT)/pkg/tool/$(GOOS)_$(GOARCH)/vet`
			`rm -f _vet`