As mentioned, it is recommended to create a unique directory for each build configuration. A build configuration can be created to address specific architectures, compiler settings, or different RTI Connext DDS Micro build options.

RTI recommends to assign a descriptive name to each build configuration, using a common format. While there are no requirements to the format for functional correctness, the tool-chain files in Cross Compiling RTI Connext DDS Micro uses the RTIME_TARGET_NAME variable to determine various compiler options and selections.

RTI uses the following name format:

{cpu}{OS}{compiler}_{config}

In order to avoid a naming conflict with RTI, the following name format is recommended:

{prefix}_{cpu}{OS}{compiler}_{config}

Some examples:

acme_ppc604FreeRTOSgcc4.6.1 - RTI Connext DDS Micro for a PPC 604 running FreeRTOS compiled with gcc 4.6.1, compiled by acme.
acme_i86Win32VS2015 - RTI Connext DDS Micro for a i386 running Windows XP or higher compiled with Visual Studio 2015, compiled by acme.
acme_i86Linux4gcc4.4.5_test - a test configuration build of RTI Connext DDS Micro for a i386 running Linux 3 or higher compiled with gcc 4.4.5, compiled by acme.

Files built by each build configuration will be stored under RTIMEHOME/build/[Debug | Release]/<name>. These directories are referred to as build directories or RTIMEBUILD. The structure of the RTIMEBUILD depends on the generated build files and should be regarded as an intermediate directory.