[PATCH] Clean up test targets in gtk/Makefile.am



Hi,

The following patch allows testgtk to be debugged with `gdb', without
resorting to using the .libs/ subdir.

  Index: gtk/Makefile.am
  ===================================================================
  RCS file: /debian/home/gnomecvs/gtk+/gtk/Makefile.am,v
  retrieving revision 1.23
  diff -u -p -r1.23 Makefile.am
  --- Makefile.am 1998/03/14 23:14:58     1.23
  +++ Makefile.am 1998/03/16 00:37:00
  @@ -263,7 +263,7 @@ testinput_DEPENDENCIES = $(DEPS)
   testselection_DEPENDENCIES = $(DEPS)
   simple_DEPENDENCIES = $(DEPS)

  -.PHONY: files
  +.PHONY: files test test-debug

   files:
	  @files=`ls $(DISTFILES) 2> /dev/null `; for p in $$files; do \
  @@ -271,7 +271,11 @@ files:
	  done

   test: testgtk
  -       ( CWD=`pwd` ; cd $(srcdir) ; $$CWD/testgtk )
  +       builddir=`pwd`; cd $(top_builddir); top_builddir=`pwd`; \
  +       cd $$builddir; cd $(srcdir); \
  +       $(SHELL) $$top_builddir/libtool --mode=execute $$builddir/testgtk

   test-debug: testgtk
  -       ( CWD=`pwd` ; cd $(srcdir) ; gdb $$CWD/testgtk )
  +       builddir=`pwd`; cd $(top_builddir); top_builddir=`pwd`; \
  +       cd $$builddir; cd $(srcdir); \
  +       $(SHELL) $$top_builddir/libtool --mode=execute gdb $$builddir/testgtk

The old `test-debug' rule doesn't work.  I can commit it if it is
ok. (And yes, all those `cd's need to be there).

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]