2. Upgrading from 4.1.0 to 4.2.0¶
See Important: How to Use this Guide, if you haven’t already.
The following sections describe how to upgrade from Connext Micro 4.1.0 to Connext Micro 4.2.0. They describe general, wire, and other compatibility issues between Connext Micro 4.2.0 and previous releases.
Attention
For important information on new and removed platforms and features in Connext Micro 4.2.0, see Supported Platforms and Programming Languages and What’s New in 4.2.0 in the Connext Micro documentation.
See RTI Connext Performance Benchmarks for performance details in this release.
2.1. API Deprecation¶
Connext Micro 4.2.0 is the last version to support the ability to specify a locator
address (such as 127.0.0.1
) without a transport name prefix. The next
version of Connext Micro will no longer support this capability. For example, if you
register a transport with the name udp
and for the address 127.0.0.1
,
you must specify the locator as udp://127.0.0.1
.
To maintain compatibility with future Connext Micro versions, we strongly suggest updating your applications to specify the transport name prefix.
2.2. Library Compatibility¶
In Connext Micro 4.2.0, support for Extensible Types (XTypes) has been extracted from
the core library rti_me
into a new, separate library rti_me_ddsxtypes
.
The XTypes module was integrated into rti_me
in Connext Micro 4.1.0. The functionality
remains unchanged.
By default, rtiddsgen will generate code that requires the rti_me_ddsxtypes
library. However, if you pass -interpreted 0
to rtiddsgen when generating
code, this library is not needed.
Note
The CERT profile does not support the rti_me_ddsxtypes
library. You must
pass -interpreted 0
to rtiddsgen when compiling IDL code for the CERT
profile.
Refer to Link applications and libraries in the Connext Micro documentation for information on linking your applications.
2.3. Transport Compatibility¶
Due to a fixed bug in Connext Micro 4.2.0, the Zero Copy v2 transport is not backwards compatible with applications using previous versions of Connext Micro (4.1.0 and below). Refer to What’s Fixed in 4.2.0 for more information. To ensure compatibility, migrate other applications using Zero Copy v2 to Connext Micro 4.2.0.