9.6 Generated Type Locations

Go To Top

Return to DDS / IDL / Type Generation

The Repository should place generated type Artifacts under the approved generated directory, not beside handwritten source files unless the selected toolchain requires it and the handbook documents the exception.

The recommended location is:

generated/dds/

If the project generates bindings for multiple languages or DDS products, the generated directory should make those distinctions clear. A representative structure is:

generated/
    dds/
        rti-connext/
            java/
            cpp/
        cyclone-dds/
            c/
            cpp/
        opendds/
            cpp/

The exact structure should follow the approved Phase 0 tool Baseline checklist instance. If Phase 0 supports only one DDS product and one target language, the structure may remain simpler. If later phases support multiple DDS vendors, the generated directory should separate vendor-specific outputs so that generated Artifacts do not overwrite or obscure one another.

Generated type locations should remain stable because Node implementations, build scripts, tests, and review procedures may depend on them. When the team changes generated output locations, it should update the handbook, generation scripts, build scripts, tests, and relevant checklist instances.