Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| config:start [2025/05/27 18:03] – [The configuration files] rajit | config:start [2025/06/05 09:58] (current) – rajit |
|---|
| </code> | </code> |
| Here the variable is an array (a.k.a. table) that corresponds to the space-separated list of values. | Here the variable is an array (a.k.a. table) that corresponds to the space-separated list of values. |
| | |
| | <code> |
| | int_tablex <var> values |
| | real_tablex <var> values |
| | string_tablex <var> values |
| | </code> |
| | Here the variable is an array (a.k.a. table) as before, but the values are appended to the existing table; i.e. the table is extended. |
| |
| <code> | <code> |
| * ''layout.conf'': [[config:layout|layout]] generation from netlist. | * ''layout.conf'': [[config:layout|layout]] generation from netlist. |
| * ''lint.conf'': [[config:lint|linting]] configuration for analyzing SPICE simulation traces. | * ''lint.conf'': [[config:lint|linting]] configuration for analyzing SPICE simulation traces. |
| | * ''expropt.conf'': [[config:expropt|expression optimization]] configuration, used to run external logic synthesis tools for translating Boolean and integer expressions into logic gates. |
| * ''models.sp'': In the standard technology configuration directory, the file ''models.sp'' should exist if mixed-signal and analog modeling is to be used. This particular file should include the SPICE commands necessary to include all the device models needed for simulation. This is typically a single line of the form ''.lib "<path-to-models>" TT'' | * ''models.sp'': In the standard technology configuration directory, the file ''models.sp'' should exist if mixed-signal and analog modeling is to be used. This particular file should include the SPICE commands necessary to include all the device models needed for simulation. This is typically a single line of the form ''.lib "<path-to-models>" TT'' |
| |
| | Any configuration parameter can be over-ridden by using the ''-cnf=<file.conf>'' command-line option that is supposed by any ACT tool. While most technology-specific options are unlikely to need to be overridden, |
| | others (e.g. warnings, definitions of macros) may need [[config:runtime|user customization]]. |
| |