Integration boundary

Generated HDL

Build a validated Livt project, inspect its generated HDL, and hand that output to simulation, synthesis, packaging, or an existing HDL project.

Prerequisite: synchronize and validate the selected project before interpreting generated output.

Build and inspect output

  1. Choose Build Livt Project.
  2. Follow compilation and generation progress in the Livt output.
  3. Expand Outputs in the Livt Project view.
  4. Inspect the active profile's lib, main, tests, and optional HxS artifacts.
text 
out/
└── debug/
    ├── lib/
    ├── main/
    ├── tests/
    └── hxs/

Keep Livt source authoritative

Generated HDL is reviewable evidence and an integration artifact, not another authored source tree. Correct the Livt source, manifest, wrapper, or generator setting responsible for an HDL diagnostic and rebuild.

Local and remote generation

The managed installation generates HDL locally by default. A project can select a remote generator endpoint when remote compilation is part of its intended architecture:

toml 
[vhdl.api]
url = "https://compiler.example.com"
ca = "certificates/company-ca.pem"

The manifest stores endpoint and trust configuration, not credentials. Local and remote generation use the same project intent and produce the same class of project artifacts.

Downstream handoff

Commit hand-written wrappers, constraints, and configuration. Archive generated HDL in CI only when another job consumes it or the output is required for review. Keep artifact retention bounded.

Continue with HxS register interfaces or vendor integration.