====== 5.5 DDS Tooling ====== [[fxdemo:05-part:start | Go To Top ]] [[fxdemo:05-part:05-development-environment:start | Return to Development Environment ]] The Phase 0 development environment must define the [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] tooling required to generate [[dido:99_annexes:annex-b-terms-and-definitions:t:type|Types]], configure participants, build runtime [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], and run the [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] network. DDS tooling may include a DDS vendor installation, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] compiler, language binding generator, runtime libraries, [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|QoS]] configuration support, diagnostic tools, and environment setup commands. The team should document the DDS vendor or vendors selected for Phase 0. If the team supports more than one DDS implementation, the handbook should identify which behaviours are part of the DDS standard and which depend on a vendor-specific tool, command, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] file, or runtime library. The DDS setup should be [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducible]]. Developers should know which tools they need, how to verify installation, how to generate Types from IDL, how to configure QoS, how to run local participants, and how to diagnose basic discovery or communication problems. The Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] should not depend on the undocumented DDS environment state. If DDS tools require environment variables, license files, setup scripts, path updates, or runtime library paths, the handbook or prerequisite script should identify and validate them. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.