IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2024-12-30 10:47:14 -06:00
Code Issues Packages Projects Releases Wiki Activity
090a30e988
opentofu/Makefile

51 lines
1.3 KiB
Makefile
Raw Normal View History

Initial work on config
2014-05-22 18:56:28 -05:00
TEST?=./...
Makefile: add vet target Add a vet target in order to catch suspicious constructs reported by go vet. Vet has successfully detected problems in the past, for example, see 482460c4c8a663ec2882bbddbb32da8e990de080 fc36b1cd9490233a3d220365fac3bc65679fe6de 68a41035a92606b6943c517fd874b54e8237485f 7b704fb77d6430cde07703f7cc8574484630d85c 4f3f85b1651d0c34c27c79cdbb772ecc07d6665a 95fa353ee928a42de1923d0f961e40d4ce201443 4bfe18b40d0749c073b3c4ba23f5c908436815d0 Some vet flags are noisy. In particular, the following flags reports a large amount of generally unharmful constructs: -assign: check for useless assignments -composites: check that composite literals used field-keyed elements -shadow: check for shadowed variables -shadowstrict: whether to be strict about shadowing -unreachable: check for unreachable code In order to skip running the flags mentioned above, vet is invoked on a directory basis with 'go tool vet .' since package- level type-checking with 'go vet' doesn't accept flags. Hence, each file is vetted in isolation, which is weaker than package-level type-checking. But nevertheless, it might catch suspicious constructs that pose a real problem. The vet target runs the following flags on the entire repo: -asmdecl: check assembly against Go declarations -atomic: check for common mistaken usages of the sync/atomic package -bool: check for mistakes involving boolean operators -buildtags: check that +build tags are valid -copylocks: check that locks are not passed by value -methods: check that canonically named methods are canonically defined -nilfunc: check for comparisons between functions and nil -printf: check printf-like invocations -rangeloops: check that range loop variables are used correctly -shift: check for useless shifts -structtags: check that struct field tags have canonical format and apply to exported fields as needed -unsafeptr: check for misuse of unsafe.Pointer Now and then, it might make sense to check the output of VETARGS=-unreachable make vet manually, just in case it detects several lines of dead code etc.
2015-01-16 15:20:32 -06:00
VETARGS?=-asmdecl -atomic -bool -buildtags -copylocks -methods -nilfunc -printf -rangeloops -shift -structtags -unsafeptr
Initial work on config
2014-05-22 18:56:28 -05:00
Default Makefile task should be to test
2014-05-23 19:00:51 -05:00
default: test
config: remove unused files
2015-01-13 12:32:03 -06:00
bin: generate
quote $(CURDIR) to support $GOPATH with spaces
2014-11-25 17:29:15 -06:00
@sh -c "'$(CURDIR)/scripts/build.sh'"
Add `make dev` to make terraform dev bins
2014-06-06 22:25:17 -05:00
config: remove unused files
2015-01-13 12:32:03 -06:00
dev: generate
quote $(CURDIR) to support $GOPATH with spaces
2014-11-25 17:29:15 -06:00
@TF_DEV=1 sh -c "'$(CURDIR)/scripts/build.sh'"
scripts: build script
2014-07-28 12:53:36 -05:00
config: remove unused files
2015-01-13 12:32:03 -06:00
test: generate
config/module: parallelize some things
2014-09-16 14:02:35 -05:00
TF_ACC= go test $(TEST) $(TESTARGS) -timeout=10s -parallel=4
Makefile: add vet target Add a vet target in order to catch suspicious constructs reported by go vet. Vet has successfully detected problems in the past, for example, see 482460c4c8a663ec2882bbddbb32da8e990de080 fc36b1cd9490233a3d220365fac3bc65679fe6de 68a41035a92606b6943c517fd874b54e8237485f 7b704fb77d6430cde07703f7cc8574484630d85c 4f3f85b1651d0c34c27c79cdbb772ecc07d6665a 95fa353ee928a42de1923d0f961e40d4ce201443 4bfe18b40d0749c073b3c4ba23f5c908436815d0 Some vet flags are noisy. In particular, the following flags reports a large amount of generally unharmful constructs: -assign: check for useless assignments -composites: check that composite literals used field-keyed elements -shadow: check for shadowed variables -shadowstrict: whether to be strict about shadowing -unreachable: check for unreachable code In order to skip running the flags mentioned above, vet is invoked on a directory basis with 'go tool vet .' since package- level type-checking with 'go vet' doesn't accept flags. Hence, each file is vetted in isolation, which is weaker than package-level type-checking. But nevertheless, it might catch suspicious constructs that pose a real problem. The vet target runs the following flags on the entire repo: -asmdecl: check assembly against Go declarations -atomic: check for common mistaken usages of the sync/atomic package -bool: check for mistakes involving boolean operators -buildtags: check that +build tags are valid -copylocks: check that locks are not passed by value -methods: check that canonically named methods are canonically defined -nilfunc: check for comparisons between functions and nil -printf: check printf-like invocations -rangeloops: check that range loop variables are used correctly -shift: check for useless shifts -structtags: check that struct field tags have canonical format and apply to exported fields as needed -unsafeptr: check for misuse of unsafe.Pointer Now and then, it might make sense to check the output of VETARGS=-unreachable make vet manually, just in case it detects several lines of dead code etc.
2015-01-16 15:20:32 -06:00
@$(MAKE) vet
Initial work on config
2014-05-22 18:56:28 -05:00
config: remove unused files
2015-01-13 12:32:03 -06:00
testacc: generate
Add "testacc" target for easy acceptance testing
2014-07-10 13:41:18 -05:00
@if [ "$(TEST)" = "./..." ]; then \
echo "ERROR: Set TEST to a specific package"; \
exit 1; \
fi
core: refactoring the way sets work internally v2 This is a refactored solution for PR #616. Functionally this is still the same change, but it’s implemented a lot cleaner with less code and less changes to existing parts of TF.
2014-12-12 16:21:20 -06:00
TF_ACC=1 go test $(TEST) -v $(TESTARGS) -timeout 45m
Add "testacc" target for easy acceptance testing
2014-07-10 13:41:18 -05:00
config: remove unused files
2015-01-13 12:32:03 -06:00
testrace: generate
testrace won't run acceptance tests
2014-07-10 15:33:57 -05:00
TF_ACC= go test -race $(TEST) $(TESTARGS)
Add testrace
2014-07-01 12:04:23 -05:00
config: remove unused files
2015-01-13 12:32:03 -06:00
updatedeps:
update Makefile to better switch to correct branch on updatedeps
2015-01-16 11:37:16 -06:00
$(eval REF := $(shell sh -c "\
git symbolic-ref --short HEAD 2>/dev/null \
|| git rev-parse HEAD"))
Makefile: roll gox into updatedeps No need to have an extra dev bootstrapping step when we can automate it!
2015-01-20 19:36:47 -06:00
go get -u github.com/mitchellh/gox
helper/schema: generate strings for ValueType
2015-01-10 17:51:53 -06:00
go get -u golang.org/x/tools/cmd/stringer
Makefile: add vet target Add a vet target in order to catch suspicious constructs reported by go vet. Vet has successfully detected problems in the past, for example, see 482460c4c8a663ec2882bbddbb32da8e990de080 fc36b1cd9490233a3d220365fac3bc65679fe6de 68a41035a92606b6943c517fd874b54e8237485f 7b704fb77d6430cde07703f7cc8574484630d85c 4f3f85b1651d0c34c27c79cdbb772ecc07d6665a 95fa353ee928a42de1923d0f961e40d4ce201443 4bfe18b40d0749c073b3c4ba23f5c908436815d0 Some vet flags are noisy. In particular, the following flags reports a large amount of generally unharmful constructs: -assign: check for useless assignments -composites: check that composite literals used field-keyed elements -shadow: check for shadowed variables -shadowstrict: whether to be strict about shadowing -unreachable: check for unreachable code In order to skip running the flags mentioned above, vet is invoked on a directory basis with 'go tool vet .' since package- level type-checking with 'go vet' doesn't accept flags. Hence, each file is vetted in isolation, which is weaker than package-level type-checking. But nevertheless, it might catch suspicious constructs that pose a real problem. The vet target runs the following flags on the entire repo: -asmdecl: check assembly against Go declarations -atomic: check for common mistaken usages of the sync/atomic package -bool: check for mistakes involving boolean operators -buildtags: check that +build tags are valid -copylocks: check that locks are not passed by value -methods: check that canonically named methods are canonically defined -nilfunc: check for comparisons between functions and nil -printf: check printf-like invocations -rangeloops: check that range loop variables are used correctly -shift: check for useless shifts -structtags: check that struct field tags have canonical format and apply to exported fields as needed -unsafeptr: check for misuse of unsafe.Pointer Now and then, it might make sense to check the output of VETARGS=-unreachable make vet manually, just in case it detects several lines of dead code etc.
2015-01-16 15:20:32 -06:00
go get -u golang.org/x/tools/cmd/vet
Removed obsolete chars
2015-01-15 15:03:43 -06:00
go get -f -u -v ./...
update Makefile to better switch to correct branch on updatedeps
2015-01-16 11:37:16 -06:00
git checkout $(REF)
update README
2014-06-26 12:33:39 -05:00
Makefile: add vet target Add a vet target in order to catch suspicious constructs reported by go vet. Vet has successfully detected problems in the past, for example, see 482460c4c8a663ec2882bbddbb32da8e990de080 fc36b1cd9490233a3d220365fac3bc65679fe6de 68a41035a92606b6943c517fd874b54e8237485f 7b704fb77d6430cde07703f7cc8574484630d85c 4f3f85b1651d0c34c27c79cdbb772ecc07d6665a 95fa353ee928a42de1923d0f961e40d4ce201443 4bfe18b40d0749c073b3c4ba23f5c908436815d0 Some vet flags are noisy. In particular, the following flags reports a large amount of generally unharmful constructs: -assign: check for useless assignments -composites: check that composite literals used field-keyed elements -shadow: check for shadowed variables -shadowstrict: whether to be strict about shadowing -unreachable: check for unreachable code In order to skip running the flags mentioned above, vet is invoked on a directory basis with 'go tool vet .' since package- level type-checking with 'go vet' doesn't accept flags. Hence, each file is vetted in isolation, which is weaker than package-level type-checking. But nevertheless, it might catch suspicious constructs that pose a real problem. The vet target runs the following flags on the entire repo: -asmdecl: check assembly against Go declarations -atomic: check for common mistaken usages of the sync/atomic package -bool: check for mistakes involving boolean operators -buildtags: check that +build tags are valid -copylocks: check that locks are not passed by value -methods: check that canonically named methods are canonically defined -nilfunc: check for comparisons between functions and nil -printf: check printf-like invocations -rangeloops: check that range loop variables are used correctly -shift: check for useless shifts -structtags: check that struct field tags have canonical format and apply to exported fields as needed -unsafeptr: check for misuse of unsafe.Pointer Now and then, it might make sense to check the output of VETARGS=-unreachable make vet manually, just in case it detects several lines of dead code etc.
2015-01-16 15:20:32 -06:00
vet:
@go tool vet 2>/dev/null ; if [ $$? -eq 3 ]; then \
go get golang.org/x/tools/cmd/vet; \
fi
@echo "go tool vet $(VETARGS) ."
@go tool vet $(VETARGS) . ; if [ $$? -eq 1 ]; then \
echo ""; \
echo "Vet found suspicious constructs. Please check the reported constructs"; \
echo "and fix them if necessary before submitting the code for reviewal."; \
fi
helper/schema: generate strings for ValueType
2015-01-10 17:51:53 -06:00
generate:
go generate ./...
Makefile: add vet target Add a vet target in order to catch suspicious constructs reported by go vet. Vet has successfully detected problems in the past, for example, see 482460c4c8a663ec2882bbddbb32da8e990de080 fc36b1cd9490233a3d220365fac3bc65679fe6de 68a41035a92606b6943c517fd874b54e8237485f 7b704fb77d6430cde07703f7cc8574484630d85c 4f3f85b1651d0c34c27c79cdbb772ecc07d6665a 95fa353ee928a42de1923d0f961e40d4ce201443 4bfe18b40d0749c073b3c4ba23f5c908436815d0 Some vet flags are noisy. In particular, the following flags reports a large amount of generally unharmful constructs: -assign: check for useless assignments -composites: check that composite literals used field-keyed elements -shadow: check for shadowed variables -shadowstrict: whether to be strict about shadowing -unreachable: check for unreachable code In order to skip running the flags mentioned above, vet is invoked on a directory basis with 'go tool vet .' since package- level type-checking with 'go vet' doesn't accept flags. Hence, each file is vetted in isolation, which is weaker than package-level type-checking. But nevertheless, it might catch suspicious constructs that pose a real problem. The vet target runs the following flags on the entire repo: -asmdecl: check assembly against Go declarations -atomic: check for common mistaken usages of the sync/atomic package -bool: check for mistakes involving boolean operators -buildtags: check that +build tags are valid -copylocks: check that locks are not passed by value -methods: check that canonically named methods are canonically defined -nilfunc: check for comparisons between functions and nil -printf: check printf-like invocations -rangeloops: check that range loop variables are used correctly -shift: check for useless shifts -structtags: check that struct field tags have canonical format and apply to exported fields as needed -unsafeptr: check for misuse of unsafe.Pointer Now and then, it might make sense to check the output of VETARGS=-unreachable make vet manually, just in case it detects several lines of dead code etc.
2015-01-16 15:20:32 -06:00
.PHONY: bin default generate test updatedeps vet
Reference in New Issue Copy Permalink