RE: API for Custom Drivers

2015-04-25 Thread Arthur Schwarz
-Original Message- From: Gavin Smith [mailto:gavinsmith0...@gmail.com] 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 wrote: > >> In "15.3.2 Declaring Custo

Re: API for Custom Drivers

2015-04-25 Thread Gavin Smith
On 25 April 2015 at 13:11, Arthur Schwarz 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

RE: API for Custom Drivers

2015-04-25 Thread Arthur Schwarz
-Original Message- From: Gavin Smith [mailto:gavinsmith0...@gmail.com] Sent: Saturday, April 25, 2015 1:26 AM To: Arthur Schwarz Cc: Automake Mailing List Subject: Re: API for Custom Drivers On 25 April 2015 at 00:27, Arthur Schwarz wrote: > > In "15.3.3.1 Command-line ar

Re: API for Custom Drivers

2015-04-25 Thread Gavin Smith
On 25 April 2015 at 00:27, Arthur Schwarz wrote: > > In "15.3.3.1 Command-line arguments for test drivers" there is the > statement: > > "The first non-option argument passed to the test driver is the program to > be run, and all the following ones are command-line options and arguments > for this

API for Custom Drivers

2015-04-24 Thread Arthur Schwarz
In "15.3.3.1 Command-line arguments for test drivers" there is the statement: "The first non-option argument passed to the test driver is the program to be run, and all the following ones are command-line options and arguments for this program." In "15.3.2 Declaring Custom Test Drivers" we have