Re: Testing external files w/ Autotest

[Ralf Wildenhues]

Hi Nathaniel,

* Nathaniel D. Sizemore wrote on Tue, Dec 13, 2005 at 11:17:09PM CET:
> 
> m4_define([AT_CHECK_EXTERNAL_FILE], [
> AT_SETUP()
> AT_KEYWORDS(add)
> AT_CHECK([add -4 -5], [], [stdout])
> AT_CHECK([fgrep -x --file=../../test3/expected_output.txt stdout],  
> [], [ignore])
> AT_CLEANUP
> ])
> 
> Here, 'add' is just a simple test program that returns the sum of any  
> arguments given to it.  The file expected_output.txt contains '9'.
> 
> I've two problems with the above code: first, the relative pathname  
> ("../../test3/...") just feels clunky and fragile to me.

The `atconfig' file should provide you with abs_top_builddir and some
others, I think.

> Secondly,  
> the above code does cannot find the required file  
> (expected_output.txt) when doing an out-of-place build, i.e. 'make  
> distcheck'.

Similarly, abs_top_srcdir.

> Could someone point me in the right direction as to how to make this  
> better?  I've been over the Goat Book, the info files, mailing list  
> archives, all to no avail.  (I'd be happy to add to the Autotest  
> documentation clarifying the above issue, by the way . . .)

Oh yes, please do!  :)

Wrt autotest, CVS Autoconf has a number of bugs fixed over 2.59, by the
way.

Cheers,
Ralf