Skip to main content
Version: Current

Generate Target Files

Use a backend to generate files for a selected target. Generation creates files only; it does not execute the target tooling.

Workflow​

  1. Validate the scenario.
  2. Confirm that the backend is discoverable.
  3. Generate target files.
  4. Inspect the generated directory and use it with the target tooling under your own operational process.
cxc validate -i scenarios/Example.cradle
cxc plugin list
cxc build -i scenarios/Example.cradle --target <backend> -o ./output

The backend name is the suffix of its executable name. For example, cxc-backend-example is selected with --target example.

Generated layout and backend options are backend-specific. Use cxc build --help and the backend's own documentation for exact requirements.

Rebuild after a scenario change​

Use rebuild when the output directory already contains a successful build and you want to compare it with an edited scenario:

cxc rebuild -i scenarios/Example.cradle --target <backend> -o ./output

The directory must contain .cxc-build-ir.json. CradleXC classifies each instance change, prints the plan and regenerates the complete output. It does not apply the plan to a live deployment.

If network identity or addressing changed, create a fresh output directory with cxc build instead. See cxc rebuild for the complete behavior.