Manifest variables description

modules

This is probably the most import of all variables. It should be Python's dictionary containg at most three keywords: local, svn and git. Values connected with these keywords can be either strings or lists containing strings. Each string indicates particular location that correct in terms of its keyword. For example, a project conisting of 4 modules: one stored locally, one in git and two in SVN can have a manifest like 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. This is what \verbfiles is used for.

fetchto

Specifies location for fetching modules from repositories.

root_manifest

Specifies 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 there applied.

name

This is the name of the project that will be used for storage on synthesis server. If you want to makes synthesis faster (and avoid transfering all the time the same files) you should specify any meaningul 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. Used in makefile generation.

library

Target library for simulation for all files from the current module. All files from a module must stay in the same library.