On Sat, Apr 11, 2009 at 1:21 PM, Eric Blake <ebb9@xxxxxxx> wrote: > This is very doable. In fact, it is how the m4 testsuite allows the user > to specify an alternate $SED program [1]. You can use atlocal.in to > perform initialization of your $TESTSUITE_PREFIX before any tests run, > then rely on that variable throughout your tests. > > [1] http://git.savannah.gnu.org/cgit/m4.git/commit/?id=e21aa9fb Thanks, it is working. I just had to use "which" to force an absolute path as Valgrind does not search in the PATH for the binary it has to run: AT_CHECK([$CHECK_PREFIX `which simple-test`], [0], [expout], [ignore]) However, I still have an issue with the other scenario (MinGW cross-compiling): in that case, my binaries are suffixed with '.exe'. Is is easy to make Autotest aware of EXEEXT, however AT_TESTED does not do what I want: atlocal.in: EXEEXT="@EXEEXT"; export EXEEXT; simple-test.at: # [...] AT_TESTED([simple-test$EXEEXT]) # AT_CHECK, etc. In that case, AT_TESTED search a binary called "simple-test$EXEEXT" without evaluating shell arguments. Is there any way to work around this issue? (I am using Autoconf 2.63) Thanks, -- Thomas Moulard http://www.linkedin.com/in/moulard _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
