Introduction to RTI Connext Micro support for iOS

This user-manual describes how to build RTI Connext Micro for iOS. RTI does not ship prebuilt libraries for RTI Connext Micro on iOS. However, the RTI Connext Micro source-code has been built and tested on iOS 4.2 and iOS 7.1.

Requirements

Connext Micro Source Code

The RTI Connext Micro source code is available from RTI's support portal: support.rti.com

Xcode

In order to build RTI Connext Micro for iOS it is required to install Xcode. RTI has tested with Xcode 4 and 5. In order to deploy and test to an actual iOS device it is necessary to obtain a developer certificate from Apple. Please see http://developer.apple.com for more information.

RTI Connext Micro works with both the iOS simulator and iOS devices.

CMake

RTI provides build-files based on CMake. CMake can be downloaded from http://www.cmake.org, and version 2.8 or higher is required. It is recommended to install the CMake GUI.

In order to create a project file for building RTI Connext Micro using Xcode, cmake tool-chain file is required. A tool-chain file can be downloaded from here:

https://code.google.com/p/ios-cmake

Building the Source

The following is step by step instructions on how to built the RTI Connext Micro source:

Extract the source-code. Please note that the remaining instructions assume that only a single platform is build from the source.

In the top-level source directory enter the following:

shell> cmake-gui .

This will start up the CMake GUI where all build configuration takes place.

Click the "Add Entry" button and enter the following values. Press "Done" when complete.

    Name: CMAKE_IOS_SDK_ROOT
    Value: <path to iOS SDK>
    Type: FILEPATH

The <path to iOS SDK> depends on version of iOS and version of Xcode. 
For iOS 7.1 and Xcode 5 the path to the SDK is:

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS7.1.sdk

Click the "Configure" button.
Select Xcode from the drop-down list.
Select "Specify tool-chain for cross-compiling" and enter the path to iOS.cmake. Press done.
Click "Configure" again. There should not be any red lines. If there are, click configure again.

Expand the CMAKE and RTIMICRO options and configure how to build RTI Connext Micro:

CMAKE_BUILD_TYPE: Debug or blank. If Debug is used the RTI Connext Micro debug 
                  libraries are built.

RTIMICRO_BUILD_API: C or C++
   C   - Include the C API.
   C++ - Include the C++ API.

RTIMICRO_BUILD_DISCOVERY_MODULE: Dynamic | Static | Both
   Dynamic - Include the dynamic discovery module.
   Static  - Include the static discovery module.
   Both    - Include both discovery modules.

RTIMICRO_BUILD_LIBRARY_BUILD: 
   Single    - Build a single library.
   RTI style - Build the same libraries RTI normally ships. This is useful
               if RTI libraries are already being used and you want to use
               the librarires build from source.

RTIMICRO_BUILD_LIBRARY_TYPE: 
    Static -  Build static libraries.
    Shared -  Build shared libraries.

RTIMICRO_BUILD_LIBRARY_PLATFORM_MODULE: Select POSIX for iOS

RTIMICRO_BUILD_LIBRARY_TARGET_NAME: <target name>
   Enter a string as the name of the target. This is also used as the
   name of the directory where the built libraries are placed. 
   If you are building libraries to replace the libraries shipped by RTI 
   you can use the RTI target name here. It is then possible to set 
   RTIMEHOME to the source tree (if RTI style is selected for 
   RTIMICRO_BUILD_LIBRARY_BUILD).

Click "Configure".

Click "Generate".

Open the Xcode project and build.

Libraries are placed in lib/<RTIMICRO_BUILD_LIBRARY_TARGET_NAME>

How to Modify Existing Examples

There are no iOS specific RTI Connext Micro examples. However, with small modifications it is possible to use any of the existing examples found in the examples directory.

Create an iOS project.
Include the source-code for for example example/CPP/HelloWorld_dpde (only include HelloWorld_publisher.cxx or HelloWorld_subscriber.cxx).
Define RTI_DARWIN as a preprocessor directive.
Call publisher_main_w_args(DDS_Long domain_id, char *udp_intf, char *peer, DDS_Long sleep_time, DDS_Long count), or subscriber_main_w_args, with the correct arguments.