Package identity, portable paths, compile order, and dependency constraints.
The dvlib.toml manifest
A complete manifest
[package]
name = "axi_agent"
version = "1.4.0"
description = "Reusable AXI4 UVM agent"
authors = ["DV Team"]
license = "MIT"
[compile]
files = [
"src/axi_pkg.sv",
"src/axi_if.sv",
"src/axi_agent.sv",
]
include_dirs = ["src"]
defines = ["AXI_DATA_WIDTH=64"]
[dependencies]
common_utils = "^2.1"
[dev-dependencies]
test_utils = "~0.3"
Field behavior
| Field | Rules and meaning |
|---|---|
| package.name | Lowercase identifier up to 64 characters; letters, digits, underscore, and hyphen. |
| package.version | Semantic version without build metadata; prereleases are allowed. |
| compile.files | Required, unique relative paths in exact source compile order. |
| compile.include_dirs | Relative directories emitted as +incdir+ entries. |
| compile.defines | NAME or NAME=value entries emitted as +define+. |
| dependencies | Runtime package ranges resolved transitively. |
| dev-dependencies | Root-project-only ranges; dependencies of dependencies do not inherit them. |
Portable path rules
Source and include paths must be relative, non-empty, and free of whitespace, backslashes, dot segments, and parent traversal. The same package archive must unpack safely and mean the same thing on different hosts.