add a .gdb target always rebuild registry

Original commit message from CVS:
add a .gdb target
always rebuild registry

diff --git a/ChangeLog b/ChangeLog
index 467592a..506e9cf 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2005-08-26  Thomas Vander Stichele  <thomas at apestaart dot org>
+
+       * check.mak:
+         add a .gdb target; rebuild registry for each target, otherwise
+         a code rebuild always triggers a reg rebuild, and it's just too
+         annoying
+       * gstdoc-scangobj:
+
 2005-08-21  Thomas Vander Stichele  <thomas at apestaart dot org>
 
        * check.mak:

diff --git a/check.mak b/check.mak
index e6fd6d0..6070886 100644 (file)
--- a/check.mak
+++ b/check.mak
@@ -12,13 +12,17 @@ check-local-disabled:
        @true
 endif
 
+$(CHECK_REGISTRY).rebuild:
+       -rm $(CHECK_REGISTRY)
+       make $(CHECK_REGISTRY)
+
 # run any given test by running make test.check
-%.check: % $(CHECK_REGISTRY)
+%.check: % $(CHECK_REGISTRY).rebuild
        @$(TESTS_ENVIRONMENT)                                   \
        $*
 
 # valgrind any given test by running make test.valgrind
-%.valgrind: % $(CHECK_REGISTRY)
+%.valgrind: % $(CHECK_REGISTRY).rebuild
        $(REGISTRY_ENVIRONMENT)                                 \
        CK_DEFAULT_TIMEOUT=20                                   \
        libtool --mode=execute                                  \
@@ -31,8 +35,16 @@ endif
        fi
        @rm valgrind.log
 
+# gdb any given test by running make test.gdb
+%.gdb: % $(CHECK_REGISTRY).rebuild
+       $(REGISTRY_ENVIRONMENT)                                 \
+       CK_FORK=no                                              \
+       libtool --mode=execute                                  \
+       gdb $*
+
+
 # valgrind all tests
-valgrind: $(TESTS) $(CHECK_REGISTRY)
+valgrind: $(TESTS)
        @echo "Valgrinding tests ..."
        @failed=0;                                                      \
        for t in $(filter-out $(VALGRIND_TESTS_DISABLE),$(TESTS)); do   \