diff options
| author | Philip Chimento <philip@endlessm.com> | 2015-08-27 13:27:24 -0700 |
|---|---|---|
| committer | Philip Chimento <philip@endlessm.com> | 2015-08-27 13:27:24 -0700 |
| commit | a2e4acd229ff4c23adc522e9dff3b7a807ba080a (patch) | |
| tree | ca57b123d3ec1ef97125752ccaaa1b220b81c6f1 /m4 | |
| parent | a74e2f421bb2c44f3bf5755dcb82b09164da7a56 (diff) | |
Revert "eos-coverage.m4: Forward coverage flags to distcheck"
This reverts commit 87bf507ea1527804fb9f1d5dbb299e0604e3b55f.
On further discussion with Dan, we decided that projects should just opt
in to coverage-on-distcheck by setting DISTCHECK_CONFIGURE_FLAGS
themselves, instead of enforcing it from eos-coverage.m4.
[endlessm/eos-sdk#3303]
Diffstat (limited to 'm4')
| -rw-r--r-- | m4/eos-coverage.m4 | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/m4/eos-coverage.m4 b/m4/eos-coverage.m4 index 31b18e8..cf92afc 100644 --- a/m4/eos-coverage.m4 +++ b/m4/eos-coverage.m4 @@ -416,10 +416,6 @@ run_coverage.coverage: clean-local: clean-coverage ' - EOS_DISTCHECK_CONFIGURE_FLAGS_RULES=" -DISTCHECK_CONFIGURE_FLAGS += --enable-coverage --with-coverage-dir=$EOS_COVERAGE_DIR - " - EOS_COVERAGE_RULES_FOOTER=' run_coverage.log: $(filter-out run_coverage.log,$(TEST_LOGS)) @@ -428,7 +424,7 @@ CLEANFILES += run_coverage.coverage .PHONY: eos-clean-c-coverage eos-c-coverage clean-coverage eos-collect-coverage coverage-cobertura coverage-genhtml ' - EOS_COVERAGE_RULES="$EOS_COVERAGE_RULES_HEADER $EOS_GENHTML_COVERAGE_RULES $EOS_COBERTURA_COVERAGE_RULES $EOS_C_COVERAGE_RULES $EOS_JS_COVERAGE_RULES $EOS_COVERAGE_RULES_TARGETS $EOS_COVERAGE_AUTORUN_GENERATED_TARGET $EOS_DISTCHECK_CONFIGURE_FLAGS_RULES $EOS_COVERAGE_RULES_FOOTER" + EOS_COVERAGE_RULES="$EOS_COVERAGE_RULES_HEADER $EOS_GENHTML_COVERAGE_RULES $EOS_COBERTURA_COVERAGE_RULES $EOS_C_COVERAGE_RULES $EOS_JS_COVERAGE_RULES $EOS_COVERAGE_RULES_TARGETS $EOS_COVERAGE_AUTORUN_GENERATED_TARGET $EOS_COVERAGE_RULES_FOOTER" # Substitute at the top first AC_SUBST([EOS_COVERAGE_DIR]) |