[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "tool-and-target-specific" configuration files
|
From: |
Ben Elliston |
|
Subject: |
Re: "tool-and-target-specific" configuration files |
|
Date: |
Tue, 22 Jan 2019 22:25:09 +1100 |
|
User-agent: |
NeoMutt/20170609 (1.8.3) |
On Mon, Jan 21, 2019 at 09:32:34PM -0600, Jacob Bachmeyer wrote:
> Or should I shelve documenting the expected structure of a testsuite
> and untangle the board/target description rat's nest first,
> documenting the description of a testing lab under "Customizing
> DejaGnu"?
Yes, let's chew that off, first. Thanks.
> Aside from load_lib, are any of the other load_* procedures in
> runtest.exp considered part of any API or can they be refactored at
> will to help untangle this rat's nest?
They are used by baseboard files in the wild (and by the ones shipped
with DejaGnu), so I would say, "no, they cannot be refactored".
Ben
signature.asc
Description: PGP signature