<img height="1" width="1" src="https://www.facebook.com/tr?id=1357777224302944&amp;ev=PageView &amp;noscript=1">

Where to Find Things in 5.2.0

August 6, 2015 by
|

In Connext DDS 5.2.0, we've made some changes to simplify our directory structure, make our file size smaller, and make your downloads shorter. In that process we've moved some files around, so here's what you need to know:

Directory Structure Overview

rti_connext_dds-5.2.0/ Top-level RTI directory for all libraries, tools, and services.
  • bin/
Scripts to run tools, services, and utilities. These scripts set up the environment correctly for RTI's applications.
  • doc/
Documentation for all installed products, including manuals and APIs
  • include/
Header files for all installed products
  • lib/
All Connext libraries in the RTI SDK
  • java
Location of jar files. Update your Java classpath to include these libraries.
  • <architecture>
Static SDK libraries you can link into your application and dynamic libraries you can add to your system-specific library path.
  • resource
Location of XML files, IDL files, example templates, and additional installers

Installation

All of our host bundles are now installed with installer executables. These should be pretty self-explanatory. We will always place the installation in an "rti_connext_dds-5.2.0" directory in the path you select.

All targets and add-ons are now being distributed as rtipkg files. You can install rtipkg files using the RTI Package Installer – either through Launcher on the Installation tab, or at the command line using:

bin/rtipkginstall[.bat]

Changes to your Build System

rtiddsgen Location

The rtiddsgen script has moved from the scripts directory to the bin directory. If your build system automatically calls rtiddsgen to generate code from your IDL files, you will need to update your build scripts to call rtiddsgen from:

rti_connext_dds-5.2.0/bin/rtiddsgen

Java Development

If you develop Java applications, download any target bundle for your platform and add the lib/<architecture> directory to your library path. Note that you no longer need to add the jdk suffix to generate example code — instead you specify the target architecture you installed and the language as Java, such as: rtiddsgen -example i86Win32VS2008 -language Java HelloWorld.idl

On Windows, you must either have the version of Visual Studio installed that matches the target architecture — such as Visual Studio 2008 for libraries in target architecture i86Win32VS2008 — or you can download a version of the Microsoft Redistributable Package that matches the target architecture you have chosen. The Microsoft Redistributable Packages can be downloaded here.

.Net Development

If you are developing for .Net, you should download a target that maps to the version of the Visual Studio and .Net framework you are using. All the necessary .Net libraries will be inside the target directory with the core libraries. The targets map to .Net framework versions as shown in the table.

When you generate example code, you can specify the architecture name without specifying a .Net framework version.

i86Win32VS2008/x64Win64VS2008 .Net 2.0
i86Win32VS2010/x64Win64VS2010 .Net 4.0
i86Win32VS2012/x64Win64VS2012 .Net 4.5
i86Win32VS2013/x64Win64VS2013 .Net 4.5.1

Examples

The first time you run any RTI script, RTI's examples will be copied into an rti_workspace directory. This allows you to build and modify examples even if your installation is in a shared or non-writable location. The default location where the workspace is copied is:

  • Mac OS X systems: /Users/your user name/rti_workspace/5.2.0/examples
  • Linux and other UNIX-based systems: /home/your user name/rti_workspace/5.2.0/examples
  • Windows systems: your Windows documents folder\rti_workspace\5.2.0\examples

You can choose not to copy the examples or to copy them to another location. There is information on how to do that in the Getting Started Guide.

Let Us Know What You Thought of the Article.

Leave a Comment Below.

Subscribe to Email Updates