separate out REGISTRY_ENVIRONMENT; we want to use that from our valgrind runs,...

separate out REGISTRY_ENVIRONMENT; we want to use that from our valgrind runs, but we also want TESTS_ENVIRONMENT to ...

Original commit message from CVS:
separate out REGISTRY_ENVIRONMENT; we want to use that from
our valgrind runs, but we also want TESTS_ENVIRONMENT to contain
everything that the first test, gst-register, needs
parent c6ca0735
2005-08-21 Thomas Vander Stichele <thomas at apestaart dot org>
* check.mak:
separate out REGISTRY_ENVIRONMENT; we want to use that from
our valgrind runs, but we also want TESTS_ENVIRONMENT to contain
everything that the first test, gst-register, needs
2005-08-21 Thomas Vander Stichele <thomas at apestaart dot org>
* check.mak:
......
......@@ -19,7 +19,7 @@ endif
# valgrind any given test by running make test.valgrind
%.valgrind: % $(CHECK_REGISTRY)
$(TESTS_ENVIRONMENT) \
$(REGISTRY_ENVIRONMENT) \
libtool --mode=execute \
$(VALGRIND_PATH) -q --suppressions=$(SUPPRESSIONS) \
--tool=memcheck --leak-check=yes --trace-children=yes \
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment