RE: API for Custom Drivers

[Arthur Schwarz]

-----Original Message-----
From: Gavin Smith [mailto:address@hidden 
Sent: Saturday, April 25, 2015 5:31 AM
To: Arthur Schwarz
Cc: Automake Mailing List
Subject: Re: API for Custom Drivers

On 25 April 2015 at 13:11, Arthur Schwarz <address@hidden> wrote:
> >> In "15.3.2 Declaring Custom Test Drivers" we have the automake 
> >> variables LOG_DRIVER and ext_LOG_DRIVER. Assuming LOG_DRIVER = 
> >> driver, does the statement mean that to execute "driver" I type:
> >>
> >>    make driver
> >>
> >> Instead of
> >>    make check ?
> >>
> >
> > I don't how the statement could mean that. When it mentions an 
> > arguments passed to the test driver, this is not referring the 
> > arguments passed to "make".
> >
> > Q: From the reading it looks like there are options followed by 
> > non-options on the command line. I guess my confusion is that the 
> > options (--options) seem to be command line options.
> 
> They are command-line options, just not the options passed to the "make"
command line.
> 
> > Q: Are there other ways to pass options to a test driver?
> 
> I've never used the custom driver feature of Automake and all I know comes
from reading the manual. Section 15.3.2 "Declaring Custom Test Drivers"
appears to explain how to specify a custom test driver to use.
> 
> > Q: How can you select one of perhaps many, test drivers?
> > Q: If there are many test drivers how can you select many, but not 
> > all, of them, "make [options] driver1 driver2 check"?
> >
> 
> From what I can see it would be something like "LOG_DRIVER=driver1 make
check" to override the test driver to use. I don't think there's any way of
using more than one at once.

I think you are saying "env LOG_DRIVER=driver1 make [options] check"?

If you are then I suppose that you can input 

"env ext1_LOG_DRIVER=driver1 ext2_LOG_GRIVER=driver2 make [options] check"

But this is not what the text seems to say, and so I'm confused.