From a266fe8d306d3fb6512cd2328db4594e807b5140 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tim-Philipp=20M=C3=BCller?= Date: Fri, 7 Jan 2011 00:43:07 +0000 Subject: [PATCH] tests: never disable g_assert() and cast checks for the unit tests The unit tests are riddled with g_assert() and friends, sometimes containing functional code like set_state() calls in them even (looking at you, pipeline/capsfilter-renegotiation). Make sure we don't disable assert and cast checks for the unit tests even if this has been specified for the rest of the code base, e.g. via --disable-glib-asserts. --- tests/check/Makefile.am | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tests/check/Makefile.am b/tests/check/Makefile.am index 31c9be1b4d..0cc03a4c37 100644 --- a/tests/check/Makefile.am +++ b/tests/check/Makefile.am @@ -151,7 +151,8 @@ VALGRIND_TO_FIX = \ noinst_PROGRAMS = $(check_libvisual) AM_CFLAGS = $(GST_CFLAGS) $(GST_CHECK_CFLAGS) \ - -DGST_TEST_FILES_PATH="\"$(TEST_FILES_DIRECTORY)\"" + -DGST_TEST_FILES_PATH="\"$(TEST_FILES_DIRECTORY)\"" \ + -UG_DISABLE_ASSERT -UG_DISABLE_CAST_CHECKS LDADD = $(GST_LIBS) $(GST_CHECK_LIBS) # valgrind testing