The recommended directory structure is described below and should be used (1) because:

the source bundle includes a helper script to run CMake that expects this directory structure.
this directory structure supports multiple architectures.
this directory structure mirrors the structure shipped by RTI. To link against built libraries instead of those shipped by RTI, set RTIMEHOME to RTIMEROOT (2).

NOTE 1: This applies to builds using CMake. To build in a custom environment, please refer to Custom Build Environments.

NOTE 2: The path to an installation of rtiddsgen, likely from a bundle shipped by RTI, will also have to be specified separately.

CMakeLists.txt.txt is the main input file to CMake and is used to generate build files.

The RTIMEROOT/include directory contains the public header files. By default it is identical to RTIMEHOME/include. However, custom ports will typically add files to this directory.

The RTIMEROOT/src directory contains the RTI Connext DDS Micro source files. RTI does not support modifications to these files unless explicitly stated in the porting guide. A custom port will typically add specific files to this directory.

The RTIMEROOT/build directory is empty by default. CMake generates one set of build-files for each configuration. A build configuration can be an architecture, RTI Connext DDS Micro options, language selection etc. This directory will contain CMake generated build-files per architecture per configuration. By convention the Debug directory is used to generate build-files for debug libraries and the Release directory is used for release libraries.

The RTIMEROOT/lib directory is empty by default. All libraries successfully built with the CMake generated build-files, independent of which generator was used, will be copied to the RTIMEROOT/lib directory.

The following naming conventions are used regardless of the build-tool:

Static libraries have a z suffix.
Shared libraries do not have an additional suffix.
Debug libraries have a d suffix.
Release libraries do not have an additional suffix.

The following libraries are built:

rti_me - the core library, including the DDS C API.
rti_me_discdpde - the Dynamic Participant Dynamic Endpoint plugin.
rti_me_discdpse - the Dynamic Participant Static Endpoint plugin.
rti_me_rhsm - the Reader History plugin.
rti_me_whsm - the Writer History plugin.
rti_me_cpp - the C++ API.

Note: the names above are the RTI library names. Depending on the target architecture the library name is prefixed with lib prefix and the library suffix also varies between target architectures, such as .so, .dylib etc.

For example:

rti_mezd indicates a static debug library
rti_me indicates a dynamically liked release library