bug-gnulib
[Top][All Lists]
Advanced

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

Re: valgrind-tests.m4


From: Simon Josefsson
Subject: Re: valgrind-tests.m4
Date: Tue, 18 May 2010 09:36:44 +0200
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)

Ralf Wildenhues <address@hidden> writes:

>> > With Automake 1.11's parallel-tests option, you have the possibility
>> > to specify per-extension "compilers" for tests.
>> >
>> > Example:
>> >   # .sh and .pl files are processed to .log files.
>> >   TEST_EXTENSIONS = .sh .pl
>> >   SH_LOG_COMPILER = bash -vx
>> >   PL_LOG_COMPILER = perl -w -m strict
>> >   TESTS = foo.sh bar.pl baz.sh
>> 
>> I don't see how to use this for running valgrind only on compiled .c
>> files though.  Or are you suggesting inventing some "virtual" extension
>> like .valgrind?  I'm not sure how to use that with the intended
>> behaviour.
>
> Well, one could prepend LOG_COMPILER (the default variable that doesn't
> go with any specified extension) or have the developer specify some
> other extension.  Your macro could just set some variable that the
> package author prepends to the needed variables: one of the
> *LOG_COMPILER ones if parallel-tests is used, and TESTS_ENVIRONMENT
> otherwise.  That would leave the most flexibility, but of course require
> a bit more work for the package author.

How would this solve the problem of running valgrind on scripts?  I'm
not familiar with the new parallel-tests stuff, but isn't LOG_COMPILER
applied for all extensions?  I don't think I see what advantage your
model would give compare to my proposal.

/Simon



reply via email to

[Prev in Thread] Current Thread [Next in Thread]