... | ... | @@ -67,11 +67,13 @@ 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
|
|
|
manifests. All supported actions are listed in an appropriate section
|
|
|
below
|
|
|
h1. Features
|
|
|
below
|
|
|
|
|
|
Hdlmake consists of two major ingredients which are described below.
|
|
|
h3. File-based project description
|
|
|
# Features
|
|
|
|
|
|
Hdlmake consists of two major ingredients which are described below.
|
|
|
|
|
|
### File-based project description
|
|
|
|
|
|
Hdlmake defines a way to describe projects that consist of smaller
|
|
|
modules. Usually developers kept these modules together, altough each of
|
... | ... | @@ -91,8 +93,9 @@ When your project is properly described with manifest files, then you |
|
|
can take advantage of written scripts. You can write makefiles for
|
|
|
simulation, do synthesis on other machines over a network. You can fetch
|
|
|
needed modules recursively and automatically and get rid of them
|
|
|
whenever you want.
|
|
|
h1. Basic run scenarios
|
|
|
whenever you want.
|
|
|
|
|
|
# Basic run scenarios
|
|
|
|
|
|
In order to Hdlmake developer has to put all python files together in
|
|
|
one directory. \\verbhdlmake.py must have execution rights. Next it is
|
... | ... | @@ -170,13 +173,17 @@ accordingly. |
|
|
## Synthesizing projects locally (option -l)
|
|
|
|
|
|
It is also possible to perform synthesis on the local machine. For this
|
|
|
purpose server and username are not necessary.
|
|
|
h1. Additional features
|
|
|
purpose server and username are not necessary.
|
|
|
|
|
|
## Injecting files list into an ISE project file
|
|
|
# Additional features
|
|
|
|
|
|
## Verbose mode (option -v)
|
|
|
|
|
|
Verbose mode (option -v)
|
|
|
For debugging purpose and having more control over what is happening you
|
|
|
can run Hdlmake in verbose mode. In this mode most of the intermediate
|
|
|
data structures are printed
|
|
|
|
|
|
# Manifest variables description
|
|
|
|
|
|
The description can be found on manifest description subpage.
|
|
|
|