... | ... | @@ -51,7 +51,7 @@ supports synthesis and simulation, they are used for both testbenches |
|
|
and top modules. The major goal of the manifests is to describe the
|
|
|
structure of the project:
|
|
|
|
|
|
- what is the module's ancestor (if any),
|
|
|
- what is the module's ancestor (if needed),
|
|
|
- for parent modules, what modules it is made of, where to take them
|
|
|
from, where to store them locally,
|
|
|
- what are the local files, that should be used in synthesis or
|
... | ... | @@ -63,8 +63,8 @@ structure of the project: |
|
|
|
|
|
Whenever you want to run Hdlmake for any reason, you should have
|
|
|
prepared manifest.py file containing all needed variables. Description
|
|
|
of available variables you can find in a section below. You can also use
|
|
|
built-in user help.
|
|
|
of available variables you can find in a section below. For a quick help
|
|
|
you can also use built-in user help.
|
|
|
Hdlmake makes use also of run arguments. In general, their purpose is to
|
|
|
indicate the action that should be taken by the script. Some of them are
|
|
|
also used for specifing additional parameteter that are not enclosed in
|
... | ... | |