[Bashdb-devel] bashdb: make check vs. VPATH build

[Eric B. <eb...@by...>]

I'm having trouble getting 'make check' to work when doing a VPATH build. 
To reproduce:

$ tar xzvf bashdb-3.00-0.02.tar.gz
$ cd bashdb-3.00-0.02
$ mkdir build
$ cd build
$ ../configure
$ make
$ make check

The problem is that the 3.00-0.02 distribution includes generated files, 
which is a no-no from autoconf's perspective.  If dbg-main.inc is generated 
at configure time (which it is), then you should only distribute 
dbg-main.inc.in.  Otherwise, bashdb-3.00-0.02/dbg-main.inc is what you 
distributed (and remembers your value of PKGDATADIR, among others), even 
though I want 'make check' to test using my 
bashdb-3.00-0.02/build/dgb-main.inc (with my PKGDATADIR).  Likewise with 
test/check_common, and so forth.

I tried editing the distribution, to make sure the tests are run on the 
built copies, but it leads to another problem.  Now, since some of the .inc 
files are in $(srcdir), while others are in $(builddir), the uninstalled 
bashdb will not work with its -L argument, because there is no one single 
directory to include.  Maybe the solution to use from here is to generate 
all of the .inc files, even though most of them have no autoconf @patterns@ 
to be replaced.  So, this patch is a good start, but needs more work before 
'make check' will work on a VPATH build.

2005-07-30  Eric Blake  <eb...@by...>

	* test/Makefile.am (check_DATA): Don't distribute generated files.
	* Makefile.am (pkgdata_DATA): Ditto.
	(pkgdatadir): Fix definition.
	(install-data-hook): Create dirname BASHDB_MAIN, if needed.
	* configure.ac (BASHDB_MAIN): Allow --with-bashdb-main to work.
	* test/run-*: Use built check_common.


-- 
Someday, I might put a cute statement here.

Eric Blake             eb...@by...