Manifest variables description
Manifests are python scripts with some variables of special meaning. They are used to describe your project. Below there is a list of each variable that can be used and that is interpreted by Hdlmake. If a variable is not described here, then you can use it, but its value will not influence the program's behavior.
modules
This is probably the most important of all variables. It should be Python's dictionary containing at most three keywords: \verblocal, \verbsvn and \verbgit. Values connected with these keywords can be either strings or lists containing strings. Each string indicates a particular location that is correct in terms of its keyword. For example, a project consisting of 4 modules: one stored locally, one in git and two in SVN can have a manifest like the following:
@
module =
{
local,
git,
svn,
"http://svn.cern.ch/trunk/oasis/client@25"\]
}
@
files
For each module you can specify what files (or directories) should be taken into account for synthesis or simulation. The files
is used to do this.
fetchto
This specifies the location of repositories for fetching modules from repositories.
root_manifest
Specifies the root manifest for the current module. The option is especially useful for testbenches. When having multiple testbenches you may want to specify modules needed for all of them in one place. Root manifest can be used in such cases.
name
This is the name of the project that will be used for storage on the synthesis server. If you want to makes synthesis faster (and avoid transferring the same files all the time) you should specify some meaningful name here.
tcl
Path to a .tcl file used for synthesis for Xilinx.
ise
Version of ISE that should be used in a synthesis
vsim_opt, vcom_opt, vlog_opt, vmap_opt
These 4 variables contain run parameters for vsim, vcom, vlog and vmap respectively. They are used in makefile generation.
library
These 4 variables contain run parameters for vsim, vcom, vlog and vmap respectively. They are used in makefile generation.