Reference

Project File Reference

Look up supported project, test, dependency, build, simulator, generator, and vendor settings.

Unsupported fields in recognized tables are reported as configuration errors. Keep credentials, downloaded dependency state, and generated paths out of the manifest.

Project and tests

TableKeys
[project]name, component, version, path, outdir, profile, indexUrl
[tests]path, components
[build.<profile>]warnings
[simulator]tool, path

Dependencies

toml
[dependencies]
"Package.Name" = "<selected-version>"
"Local.Package" = { path = "../local-package" }
"Identified.Local.Package" = { version = "<selected-version>", path = "../local-package" }

Inline dependency tables accept version and path.

VHDL generation

TableKeys
[vhdl]file_header, company
[vhdl.api]url, ca

Vivado

TableKeys
[vendor.vivado]path, part
[vendor.vivado.project]component, wrapper, top, include_tests
[vendor.vivado.ip]component, wrapper, top, vendor, library, name, version, display_name, description, taxonomy, include_tests

GOWIN

TableKeys
[vendor.gowin]path, part, device_version
[vendor.gowin.project]component, wrapper, top, constraints, timing_constraints, output_base_name, run, include_tests
[vendor.gowin.ip]component, wrapper, top, name, version, library, include_tests

Lattice Radiant

TableKeys
[vendor.radiant]path, ip_packager_path, device, performance
[vendor.radiant.project]component, wrapper, top, implementation, strategy, synthesis, constraints, run_to, include_tests
[vendor.radiant.ip]component, wrapper, top, vendor, library, name, version, display_name, description, supported_devices, documentation, encrypt, include_tests

Use Configure a Livt Project for workflow guidance and Vendor Integration for template-specific behavior.