PyInfra: Incremental Modular Configuration

[preusser]

Enable the prompt use of PoC by an incremental configuration process that asks for configuration info only when a certain flow or tool is to be used for the first time. A modular organization of the configuration data appears to be the natural choice for such an approach. This would additionally enable a targeted reconfiguration, e.g., after the update of a specific vendor tool. An explicitly triggered complete configuration should still be possible.

Measures:

• Tools maintain a configuration state including the states unconfigured and configured (with the corresponding info).
• Each invocation of a tool would start with calling its ensureConfiguration method and trigger the tool configuration when the tool is in unconfigured state. The actual invocation will proceed when the tool already was or has been properly configured.
• The optional invocation of ./poc.sh configure walks the user through a possibly complete configuration. Each configuration step may be skipped by the choice of the user.
• The invocation ./poc.sh configure <tool> allows a targeted (re-)configuration of the named tool.

[Paebbels]

Hello,

Tools maintain a configuration state including the states unconfigured and configured (with the corresponding info).

This is already implemented.

Each invocation of a tool would start with calling its ensureConfiguration method and trigger the tool configuration when the tool is in unconfigured state. The actual invocation will proceed when the tool already was or has been properly configured.

The unconfigured state is already detected by each command. An error message is reported to the user. The messages includes a note to invoke .\PoC.ps1 configure and to configure the needed tool(s).

Invoking a configuration routine from within a tool flow routine is not possible and not intended.

The optional invocation of ./poc.sh configure walks the user through a possibly complete configuration. Each configuration step may be skipped by the choice of the user.

This is already implemented. See the configuration tools hints or the detailed configuration documentation for choice P (skip/pass a configuration step).

The invocation ./poc.sh configure <tool> allows a targeted (re-)configuration of the named tool.

Implemented in commit 864528c38c680733eedf5fb5907fdaf0e3640f6a. Moreover, the configuration can be launched in verbose (-v) or debug (-d) mode.

Example:

cd PoCRoot
.\poc.ps1 configure Xilinx.Vivado

Regards Patrick