Home

My Document - Community RTI Connext Users

1. 11 11 Thread Configuration Thread Settings for Windows Platforms Section Table 11 6 on the facing page lists the thread settings for Windows platforms 142 11 11 Thread Configuration Thread Priority Definitions for Windows Platforms Section Table 11 7 on the next page and Thread Kinds for Windows Platforms Section Table 11 8 on the next page list the thread priority definitions and thread kinds respectively Table 11 6 Thread Settings for Windows Platforms DDS Applicable Thread ThreadSe dines d Platform Specific Setting mask OS default thread type priority Asynchronous Publisher Asynchronous flushing stack size thread OS default thread stack size cpu list CPU core affinity not supported cpu rotation mask priority Database thread stack size cpu list cpu rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO OS default thread stack size CPU core affinity not supported CPU core affinity not supported N DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT priority Eye died stack_size OS default thread stack size cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS _ FLOATING POINT mask priority ReceiverPool threads stack size OS default thread stack size cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported 143 11 11 1 Sup
2. All other supported architectures Dynamic ASee Notes for Using Shared Memory Section 2 3 1 on page 11 b NDDSHOME represents the root directory of your Connext DDS installation LIBPATH represents the value of the LIBPATH variable prior to changing it to support Connext DDS When using nddsjava jar the Java virtual machine JVM will attempt to load release versions of the native libraries nddsjava so nddscore so nddsc so When using nddsjavad jar the JVM will attempt to load debug versions of the native libraries nddsjavad so nddscored so nddscd so Chapter 2 AIX Platforms Table 2 4 Library Creation Details for AIX Architectures Library arnt Libraries Compiler Flags Used by RTI Used by RTI RTI Architecture Static amp Dynamic q32 qlongdouble qalias noansi qpic large qthreaded D POSIX C Release SOURCE 199506L D__ EXTENSIONS O qflag i i DPtrIntType long DCSREAL IS FLOAT DCPU Power5 DNDEBUG p5AIX5 3xlc9 0 q32 qlongdouble qalias noansi qpic large qthreaded D POSIX C SOURCE 199506L D__ EXTENSIONS O qflag i i DPtrIntType long DCSREAL IS FLOAT DCPU Power5 g q32 qwarn64 qlongdouble qalias noansi qpic large qthreaded D POSIX C Release SOURCE 199506L D EXTENSIONS O qflag i i DPtrIntType long DCSREAL _ IS FLOAT DCPU Power7 DNDEBUG p7AIX7 1xlc12 1 q32 qwarn64 qlongdouble qalias noansi qpic large qthreaded D POSIX C SOURCE 199506L D EXTENSIONS O qflag ii
3. Debug None required All other supported Linux SUSE architectures i when not using Java Dynamic Release LD LIBRARY PATH NDDSHOME llibK lt architecture gt amp Debug LD_LIBRARY_PATH Table 5 6 Library Creation Details for Linux Architectures provides details on how the Linux libraries were built This table is provided strictly for informational purposes you do not need to use these para meters to compile your application You may find this information useful if you are involved in any in depth debugging Table 5 6 Library Creation Details for Linux Architectures Library Format RTI Architecture Compiler Flags Used by RTI Static amp Dynamic fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS _ Release FLOAT DCPU I80586 DTARGET i86Linux2 6gcc3 4 3 fmessage length 0 DNDEBUG c Wp MD 186Linux2 6gcc3 4 3 fPIC DLINi86Linux2 6gcc3 4 3UX g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Linux2 6gcc3 4 3 fmessage length 0 c Wp MD fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS _ Release FLOAT DCPU I80586 DTARGET i86Linux2 6gcc4 1 1 fmessage length 0 DNDEBUG c Wp MD 186Linux2 6gcc4 1 1 fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS _ FLOAT DCPU I80586 DTARGET 186Linux2 6gcc4 1 1 fmessage length 0 c Wp MD fPIC DLINUX O Wall Wno unknown pragmas
4. Known Defects e If you have a Wind River account you can find more information about defect WIND00418701 here https sup port windriver com olsPortal faces maintenance defectD etails jspx defectId WIND00418701 This issue has been fixed in VxWorks 6 9 3 2 If you need a patch for your version of VxWorks or for more information about this issue please contact Wind River e There is a known defect when using VxWorks 6 9 3 2 in a multicast scenario If you have a Wind River account you can find more information about defect VX W6 8077 here https sup port windriver com olsPortal faces maintenance defectD etails jspx defectlId V X W6 80771 amp adf c trl state crbf uqpa 4 If you are using VxWorks 6 9 3 2 and want to use multicast please contact Wind River to get an official patch to fix this issue 10 8 Supported Transports Shared memory Shared memory is supported and enabled by default on all VxWorks 6 x and higher architectures It is not supported on VxWorks 5 x and VxWorks 653 platforms See also e Shared Memory Communication between Applications Running in Kernel Mode and RTP Requires Explicitly Set Participant ID Section 10 8 1 on the next page 114 10 8 1 Shared Memory Communication between Applications Running in Kernel Mode and RTP e How To Run Connext DDS Libraries in Kernels Built without Shared Memory Section 10 8 2 below UDPv4 Supported and enabled by default UDP v6 Supported on VxWorks 6 7 an
5. DLINUX O Wall Wno unknown pragmas Release DPtrIntType long DCSREAL IS FLOAT DCPU PPC32 DTARGET ppc85xxWRLinux2 6gcc4 3 2 DNDEBUG Wp MD ppc85xxWRLinux2 6gcc4 3 2 powerpc wrs linux gnu gcc mcpu powerpc msoft float fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU PPC32 DTARGET ppc85xxWRLinux2 6gcc4 3 2 Wp MD m64 fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL _ Release IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 1 1 DNDEBUG c Wp MD x64Linux2 6g0cc4 1 1 m64 fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL _ IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 1 1 fmessage length 0 c Wp MD m64 fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL _ Release IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 1 21 DNDEBUG c Wp MD x64Linux2 6gcc4 1 2 m64 fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL _ IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 1 2 fmessage length 0 c Wp MD Release m64 fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL_ IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gce c Wp MD x64Linux2 6gcc4 3 4 Debug m64 fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL_ IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 3 4 c Wp MD gcc m64 fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long Release DCSREAL IS FLOA
6. DPtrIntType long DCSREAL IS FLOAT DCPU i686 DRTI ENDIAN _ LITTLE DRTI THREADS DRTI MULTICAST DRTI SHARED MEMORY DRTI IPV6 DTARGET i86Linux3gcc4 8 2 DNDEBUG c Wp MD g m32 fPIC DLINUX DRTI LINUX26 DRTI LINUX DRTI POSIX THREADS DRTI POSIX SEMAPHORES DRTI CPU AFFINITY O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU i686 DRTI ENDIAN _ LITTLE DRTI THREADS DRTI MULTICAST DRTI SHARED MEMORY DRTI IPV6 DTARGET i86Linux3 gcc4 8 2 DDEBUG c Wp MD fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS _ FLOAT DCPU PPC7400 DTARGET ppc7400Linux2 6gcc3 3 3 DNDEBUG c Wp MD fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS _ FLOAT DCPU PPC7400 DTARGET ppc7400Linux2 6gcc3 3 3 c Wp MD fPIC DLINUX g Wall Wno unknown pragmas DPtrIntyType long DCREAL IS_ FLOAT DCPU e500 DTARGET ppc85xxLinux2 6gec4 3 2V DNDEBUG c Wp MD fPIC DLINUX g Wall Wno unknown pragmas DPtrIntyType long DCREAL IS _ FLOAT DCPU e500 DTARGET ppc85xxLinux2 6gcec4 3 2 c Wp MD The C libnddscpp dynamic libraries were linked using g the C dynamic libraries i e libnddscore and libnddsc were linked using gcc 45 Chapter 5 Linux Platforms Table 5 6 Library Creation Details for Linux Architectures Library Format RTI Architecture Compiler Flags Used by RTI Static amp Dynamic mcpu powerpc msoft float fPIC
7. DPtrIntType long DCSREAL IS _ Release FLOAT DCPU I80586 DTARGET i86Linux2 6gcc4 1 2V fmessage length 0 DNDEBUG c Wp MD 186Linux2 6gcc4 1 2 fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS _ FLOAT DCPU I80586 DTARGET 186Linux2 6gcc4 1 2 fmessage length 0 c Wp MD 44 Chapter 5 Linux Platforms Table 5 6 Library Creation Details for Linux Architectures RTI Architecture 186Linux2 6gcc4 4 5 186Linux3gcc4 3 4 186Linux3gcc4 8 2 ppc7400Linux2 6gcc3 3 3 ppc85xxLinux2 6gcc4 3 2 Library Format Static amp Dynamic Release Debug Release Release Release Debug Release Compiler Flags Used by RTI gcc m32 fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET 186Linux2 6gcc4 4 5 DNDEBUG Wp MD gcc m32 fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET 186Linux2 6gcc4 4 5 Wp MD fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS _ FLOAT DCPU I80586 DTARGET 186Linux3 gcc4 3 4 fmessage length 0 DNDEBUG c Wp MD fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS _ FLOAT DCPU I80586 DTARGET 186Linux3 gcc4 3 4 fmessage length 0 c Wp MD m32 fPIC DLINUX DRTI LINUX26 DRTI LINUX DRTI POSIX THREADS DRTI POSIX SEMAPHORES DRTI CPU AFFINITY O Wall Wno unknown pragmas
8. DPtrIntType long DCSREAL _ IS FLOAT DCPU Power7 g q64 qwarn64 qlongdouble qalias noansi qpic large qthreaded D POSIX C Release SOURCE 199506L D__ EXTENSIONS O qflag i 1 DPtrIntType long DCSREAL IS FLOAT DCPU Power5 DNDEBUG 64p5AIX5 3xlc9 0 q64 qwarn64 qlongdouble qalias noansi qpic large qthreaded D POSIX C SOURCE 199506L D__ EXTENSIONS O qflag i i DPtrIntType long DCSREAL IS FLOAT DCPU Power5 g q64 qwarn64 qlongdouble qalias noansi qpic large qthreaded D POSIX C Release SOURCE 199506L D EXTENSIONS O qflag ii DPtrIntType long DCSREAL _ IS FLOAT DCPU Power7 DNDEBUG 64p7AIX7 1xlc12 1 q64 qwarn64 qlongdouble qalias noansi qpic large qthreaded D POSIX C SOURCE 199506L D EXTENSIONS O qflag ii DPtrIntType long DCSREAL _ IS FLOAT DCPU Power7 g 4Connext DDS was built using the xIC_r compiler See IBM s XLC reference manual for a description of the different compilers For a list of the additional settings defined by default for the xIC r compiler see the file etc vac cfg 53 bL inking without the 128 bit versions of the C Runtime Library when your program uses 128 bit long doubles for example if you specify qldbl128 or qlongdouble alone may produce unpredictable results Therefore RTI libraries compiled with qlongdouble are linked using 1C128 For more information please consult the IBM compiler reference website http pic dhe ibm com infocenter comphelp v121v141
9. DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM DNDEBUG c Wp MD march i486 ansi DTOOL gnu mrtp D PROTOTYPE 5 0 fPIC g DVXWORKS _ MAJOR VERSION 6 DVXWORKS MINOR VERSION 7 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM c Wp MD ccpentium m32 march pentium fno builtin ansi DCPU PENTIUM DTOOL _ Staticor FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 0 Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 8 Wall Wno Release unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD pentiumVx6 8gcc4 1 2 ccpentium m32 march pentium fno builtin ansi DCPU PENTIUM DTOOL _ Static or FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 g Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 8 Wall Wno Debug unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT Wp MD ccpentium m32 march pentium ansi DCPU PENTIUM DTOOL FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 O Wall Wno unknown pragmas DRTS _ VXWORKS DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 8 DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD Static or Dynamic Release pentiumVx6 8gcc4 1 2 rtp ccpentium m32 march pentium ansi DCPU PENTIUM DTOOL FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 g Wall Wno unknown pragmas DRTS _ VXWORKS DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 8 DPtrIntType long DCSREAL IS FLOAT
10. SOLARIS2 O Wall Wno unknown pragmas fPIC DPtrIntType long DCSREAL IS FLOAT Release DCPU 1386 DTARGET 1868012 9gcc3 3 21 DNDEBUG c Wp MD Wp 186S0D 9gcc3 3 2 Static and D POSIX C SOURCE 199506L D__ EXTENSIONS DSolaris2 DSVR5 DSUNA Dynamic SOLARIS2 g O Wall Wno unknown pragmas fPIC DPtrIntType long DCSREAL IS _ Debug FLOAT DCPU 1386 DTARGET 186Sol2 9gcc3 3 2 c Wp MD Wp NDDSHOMB is where Connext DDS is installed LD_ LIBRARY PATH represents the value of the LD LIBRARY PATH variable prior to changing it to support Connext DDS When using nddsjava jar the Java virtual machine JVM will attempt to load release versions of the native libraries When using nddsjavad jar the JVM will attempt to load debug versions of the native libraries b NDDSHOME is where Connext DDS is installed LD_ LIBRARY PATH represents the value ofthe LD LIBRARY PATH variable prior to changing it to support Connext DDS When using nddsjava jar the Java virtual machine JVM will attempt to load release versions of the native libraries When using nddsjavad jar the JVM will attempt to load debug versions of the native libraries The C libnddscpp dynamic libraries were linked using g the C dynamic libraries i e libnddscore and libnddsc were linked using gcc 88 9 1 Request Reply Communication Pattern Table 9 4 Library Creation Details for Solaris Architectures RTI Architecture Library Format S
11. Wp MD Static or Dynamic Debug 105 Chapter 10 VxWorks Platforms Table 10 4 Library Creation Details for All VxWorks Architectures Library Format RTI Architecture Compiler Flags Used by RTI ccpentium m32 march pentium fno builtin ansi DCPU PENTIUM DTOOL _ Staticor FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 0 Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 9 Wall Wno Release unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD pentiumVx6 9gcc4 3 3 ccpentium m32 march pentium fno builtin ansi DCPU PENTIUM DTOOL _ Static or FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 g Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 9 Wall Wno Debug unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU PENTIUM Wp MD ccpentium m32 march pentium ansi DCPU PENTIUM DTOOL FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 O Wall Wno unknown pragmas DRTS _ VXWORKS DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 9 DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD Static or Dynamic Release tiumVx6 9gcc4 3 3 o UM cepentium m32 march pentium ansi DCPU PENTIUM DTOOL FAMILY gnu Staticor DTOOL gnu mrtp D_ PROTOTYPE 5 0 g Wall Wno unknown pragmas DRTS Dynamic VXWORKS DVXWORKS MAJOR VERSION 6 Debug DVXWORKS MINOR VERSION 9 DPtrIntType long DCSREAL IS FLOAT Wp MD ccpentium mtune p
12. libnddscorezd a libnddsczd dba libnddscorezd dba librticonnextmsgezd dba librticonnextms gezd a 2Choose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API gt The dba files contain the debugging information You can link without these as long as they are located in the same directory as the matching d a file so that the MULTI IDE can find the debug information The RTI C C libraries are in S NDDSHOME Ylib lt architecture gt dThe rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type Transports other than the default IP transport such as StarFabric may require linking in additional libraries For further details see the API Reference HTML documentation or contact support rti com 26 4 1 Required Patches for INTEGRITY 10 0 2 and 11 0 4 Table 4 3 Running Instructions for INTEGRITY Architectures RTI Architecture Required Environment Variables Table 4 4 Library Creation Details for INTEGRITY Architectures RTI Architecture Compiler Flags Used by RTI Format bsp devtree fsl e500mc prototype warnings unknown_pragma silent link_once_templates p4080Inty1 1 devtree fsl e500mc comp2012 1 Static bsp devtree fsl e500mc prototype warnings unknown pragma silent link once templates Debug G Static bsp devtree fsl e500mc prototy
13. lt openssl install dir gt lt architecture gt lib These libraries are in lt NDDSHOME gt 7lib lt architecture gt 73 7 10 Libraries Required for Using RTI TCP Transport APIs Table 7 11 Additional Libraries for using RTI TCP Transport APIs on OS X Systems with TLS Enabled Library Format RTI TLS Libraries Dynamic Release libnddstls so Dynamic Debug libnddstlsd so Static Debug libnddstlszd a libssl so OpenSSL Libraries libcrypto so AThese libraries are in lt NDDSHOME gt libKarchitecture gt 74 Chapter 8 QNX Platforms Table 8 1 Supported QNX Platforms lists the architectures supported on QNX operating systems Table 8 1 Supported QNX Platforms QNX Neutrino 6 4 1 qec 4 3 3 with GNU C libraries 186QNX6 4 1qcc_gpp QNX Neutrino 6 5 qec 4 4 2 with GNU C libraries 1860NX6 5qcc gpp4 4 2 QNX Neutrino 6 5 0 SP1 ARM v7a Cortex qcc 4 4 2 with Dinkum libraries armv7aQN X6 5 0SP 1qcec_cpp4 4 2 Table 8 2 Building Instructions for QNX Architectures lists the libraries you will need to link into your application See also e Libraries Required for Using Distributed Logger Section 8 8 on page 82 e Libraries Required for Using RTI Secure WAN Transport APIs Section 8 10 on page 83 e Libraries Required for Using RTI TCP Transport APIs Section 8 11 on page 83 Make sure you are consistent in your use of static dynamic debug and release versions of the lib raries Do not link both static and dynamic libr
14. 7 or 1 8 IBM xIC r for AIX v12 1 POWER 64 bit mode 64p7A1X7 1xlc12 1 IBM Java 1 7 or 1 8 Table 2 2 Building Instructions for AIX Architectures lists the compiler flags and the libraries you will need to link into your application See also Libraries Required for Using Monitoring Section 2 8 on page 14 Make sure you are consistent in your use of static dynamic debug and release versions of the lib raries Do not link both static and dynamic libraries Similarly do not mix release and debug lib raries Table 2 3 Running Instructions for AIX Architectures provides details on the environment vari ables that must be set at run time for an AIX architecture Table 2 4 Library Creation Details for AIX Architectures provides details on how the libraries were built This table is provided strictly for informational purposes you do not need to use these Chapter 2 AIX Platforms parameters to compile your application You may find this information useful if you are involved in any in depth debugging Table 2 2 Building Instructions for AIX Architectures Library Required RTI Required System Required Compiler Format Libraries c Libraries4 Flags libnddscppz a or libnddscpp2z a Static Release libnddscz a libnddscorez a librticonnextms gcppz a 141 Insl Im pthread libnddscppzd a ids or libnddscpp2zd a Static Debug libnddsczd a libnddscorezd a Ge librticonnextms gcppzd a DRTI_AIX DRTI UNIX Trad
15. 9 4 Supported Transports Shared memory Supported and enabled by default UDPv4 Supported and enabled by default UDP v6 Supported for all Solaris 2 9 and 2 10 platforms The transport is not enabled by default and the peers list must be modified to support IPv6 Traffic Class support is only provided for Solaris 2 10 plat forms TCP IPv4 Not supported 9 4 1 Shared Memory Support To see a list of shared memory resources in use use the ipes command To clean up shared memory and shared semaphore resources use the iperm command The shared memory keys used by Connext DDS are in the range of 0x400000 For example ipcs m grep 0x4 The shared semaphore keys used by Connext DDS are in the range of 0x800000 the shared mutex keys are in the range of 0xb00000 For example joss cuajo 0 igoes S gras Odo 90 9 4 2 Increasing Available Shared Resources Please refer to the shared memory transport online documentation for details on the shared memory and semaphore keys used by Connext DDS 9 4 2 Increasing Available Shared Resources Connext DDS uses System V semaphores to manage shared memory communication If you plan to run multiple Connext DDS applications on the same node at the same time you may need to increase the num ber of available semaphores Each Connext DDS application that has shared memory enabled allocates 4 individual semaphores The Solaris system defaults allow only 10 per host which may
16. AND MEAN O2 Zi MT EHsc D_ CRT SECURE NO DEPRECATE DNDEBUG c DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Win32VS2010 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN 02 Zi MD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Win32VS2010 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MTd EHsc RTC1 D CRT SECURE NO DEPRECATE c DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGE T i86Win32VS2010 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c 135 Chapter 11 Windows Platforms Table 11 5 Library Creation Details for Windows Architectures RTI Library Te Compiler Flags Used by RTI DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET 186Win32VS2012 Static DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN 02 Zi Release MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET 186Win32V8S2012 Dynamic DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN 02 Z Release MD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c i86Win32V S2012 DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Win32VS2012 Static DWIN32 D_ WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI Debug MTd EHsc RTC1 D CRT SECURE NO DEPRE
17. C Libraries for QNX Platforms For QNX architectures in Connext DDS 5 0 and higher The C libraries are now built without the fno rtti flag and with the fexceptions flag To build QNX architectures with Connext DDS 5 0 and higher you must build your C applications without fno exceptions in order to link with the RTI libraries In summary e Do not use fno exceptions when building a C application or the build will fail It is not neces sary to use fexceptions but doing so will not cause a problem e Itis no longer necessary to use fno rtti but doing so will not cause a problem 78 8 2 Support for Modern C API 8 2 Support for Modern C API Connext DDS provides two different C APIs which we refer to as the Traditional C and Modern C APIs The Modern C API is available for all QNX platforms For more information on Modern C see Traditional vs Modern C in the User s Manual 8 3 Multicast Support Multicast is supported on QNX platforms and is configured out of the box That is the default value for the initial peers list NDDS_DISCOVERY_ PEERS includes a multicast address See the online doc umentation for more information 8 4 Supported Transports Shared Memory Supported and enabled by default To see a list of the shared memory resources enter ls dev shmem RTIOsapiSharedMemorySegment To clean up the shared memory resources remove the files listed in dev shmem The shared
18. CPU core affinity not supported cpu rotation k DDS THREAD SETTINGS STDIO DDS THREAD uu SETTINGS FLOATING POINT priority OS default thread priority oa stack_size OS default stack size cpu_list CPU core affinity not supported cpu_rotation DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT priority OS default thread priority Hermon treads stack size OS default stack size cpu list CPU core affinity not supported imm Table 3 6 Thread Priority Definitions for Android Platforms Thread Priority Definition Operating System Priority 2 THREAD PRIORITY HIGH 9999999 THREAD PRIORITY ABOVE NORMAL 9999999 THREAD PRIORITY NORMAL 9999999 21 3 5 1 Support for Controlling CPU Core Affinity for RTI Threads Table 3 6 Thread Priority Definitions for Android Platforms Thread Priority Definition Operating System Priority THREAD PRIORITY LOW 9999999 THREAD PRIORITY BELOW NORMAL 9999999 3 5 1 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Controlling CPU Core Affinity in the User s Manual is not available for Android platforms 3 6 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on Android platforms 3 7 Distributed Logger Support RTI Distributed Logger is not supported on Android platforms 3 8 Libraries Required for Using Monitoring M
19. CPU for dynamic release and dynamic debug libraries 1dl Insl Im also use the following libnddscd so Ipthread Irt Wl no as needed libnddscored so librticonnextmsgcd so Dynamic Debug Release nddsj a rticonnextmsg jar None required nddsjavad jar rticonnextmsgd jar Table 5 5 Running Instructions for Linux Architectures provides details on the environment variables that must be set at run time for a Linux architecture When running on 64 bit Java architectures x64Linux2 6 use the d64 flag on the command line Table 5 5 Running Instructions for Linux Architectures Library RTI Architecture Format Environment Variables LD_LIBRARY_PATH NDDSHOME libKarchitecture gt All supported Linux SUSE architectures when LD_LIBRARY_PATH using Java Note For all 64 bit Java architectures 64Linux use d64 in the command line 2Choose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API PRTI C C Java libraries are in lt NDDSHOME gt 1ib lt architecture gt The jar files are in lt NDDSHOME gt 71lib ava The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 43 Chapter 5 Linux Platforms Table 5 5 Running Instructions for Linux Architectures Library RTI Architecture Format Environment Variables Static Release amp
20. D RTI WIN32 MTd D RTI WIN32 D NDDS DLL _ VARIABLE MD D RTI WIN32 D NDDS DLL _ VARIABLE MDd 2Choose nddscpp for the Traditional C API or nddscpp2 for the Modern C API bThe RTI C C Java libraries are in lt NDDSHOME gt lib lt architecture gt Jar files are in lt NDDSHOME gt lib java 128 Chapter 11 Windows Platforms Table 11 2 Building Instructions for Windows Host Architectures Library Required System Required Compiler RTI Libraries or Jar Files Format Libraries Flags Static Release Static Debug C Traditional and Modern APIs Dynamic Release Dynamic Debug nddscppz lib or nddscpp2z lib nddscz lib nddscorez lib rticonnextmsgcppz lib nddscppzd lib or nddscpp2zd lib nddsczd lib nddscorezd lib rticonnextmsgcppzd lib nddscpp lib or nddscpp2 lib nddsc lib nddscore lib rticonnextmsgcpp lib nddscppd lib or nddscpp2d lib nddscd lib nddscored lib rticonnextmsgcppd lib netapi32 lib advapi32 lib user32 lib ws2 32 lib D RTI WIN32 MT D RTI WIN32 MTd D RTI WIN32 D NDDS DLL _ VARIABLE MD D RTI WIN32 D NDDS DLL _ VARIABLE MDd AChoose nddscpp for the Traditional C API or nddscpp2 for the Modern C API bThe RTI C C Java libraries are in lt NDDSHOME gt lib lt architecture gt Jar files are in lt NDDSHOME gt lib java 129 Chapter 11 Windows Platforms Table 11 2 Building Ins
21. DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V 2010 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c 137 11 1 Requirements when Using Microsoft Visual Studio Table 11 5 Library Creation Details for Windows Architectures RTI Library Architecture Format Static Release Dynamic Release Note linker requires MACHINE X64 option Static Debug Dynamic Debug x64Win64VS2012 Static Release Dynamic x64Win64VS2013 Release Note linker requires MACHINE X64 option Dynamic Debug Compiler Flags Used by RTI W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V 2012 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V 2012 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V 2012 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MTd EHsc RTC1 D CRT SECURE NO DEPRECATE c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V S2012 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c W3 DPtrIntType long DCSRE
22. DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DNDEBUG Dynamic Release target 1 4 source 1 4 All supported Linux architectures for Java target 1 4 source 1 4 g 5 1 Support for Modern C API Connext DDS provides two different C APIs which we refer to as the Traditional C and Modern C APIs The Modern C API is available for all the platforms in Table 5 1 Linux Platforms on ARM CPUs through Table 5 3 Linux Platforms on PowerPC CPUs except Yellow Dog Linux 4 0 ppc7400Linux2 6gcc3 3 3 For more information on Modern C see Traditional vs Modern C in the User s Manual 5 2 Multicast Support Multicast is supported on all Linux platforms and is configured out of the box That is the default value for the initial peers list NDDS_DISCOVERY_PEERS includes a multicast address See the API Reference HTML documentation for more information 47 5 3 Supported Transports 5 3 Supported Transports Shared memory Supported and enabled by default To clean up shared memory resources reboot the ker nel UDPv4 Supported and enabled by default UDPv6 Supported for all platforms except Raspbian Wheezy 7 0 armv6vfphLinux3 xgcc4 7 2 The UDPv6 transport is not enabled by default and the peers list must be modified to support IPv6 Note Traffic Class support is only provided on architectures with gcc 4 1 0 or later that support the UDPv6 transport TCP IPv4 Su
23. Hat Enterprise Linux 4 0 iS6Linux2 6gcc3 4 3 e Yellow Dog Linux 4 0 ppc7400Linux2 6gcc3 3 3 To use the above platforms you must have the development version of Native POSIX Thread Library NPTL installed on your host system and the NPTL libraries on your target system e When you build the application you must have the development NPTL library installed in us r lib nptl This library is not installed by default e To see if your system has NPTL installed look for this directory usr lib nptl It should contain these files libpthread so and libpthread a e If NPTL is not installed you will need to install a package that includes it such as nptl devel This package is not typically part of a default installation You can find it either in your original Linux installation media CD DV D or if you have upgraded your system through the distribution s update site e When you run the application it will automatically use the default NPTL library in lib nptl You do not need the development library installed on the target system 5 5 2 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Controlling CPU Core Affinity in the User s Manual is available on all supported Linux SUSE platforms The dynamic loader Id is configured by default to load the NPTL library as long as LD ASSUME _ KERNEL is NOT defined 49 5 5 2 Support for Controlling CPU Core Affinity
24. INTEGRITY 10 0 2 and 11 0 4 platforms you must install these patches from Green Hills Software 27 4 2 Support for Modern C API e INTEGRITY 10 0 2 Platforms e pentiumInty10 0 2 pcx86 patch_6901 iff e INTEGRITY 11 0 4 Platforms e p4080Intyl1 devtree fsl e500mc comp2012 1 patch_7584 iff and patch_7585 iff e p4080Inty 1 1 devtree fsl e500mc comp2013 5 4 patch_8154 iff patch_8155 iff patch_ 8246 iff For more information on these patches please contact your Green Hills Software representative 4 2 Support for Modern C API Connext DDS provides two different C APIs which we refer to as the Traditional C and Modern C APIs The Modern C API is available for these INTEGRITY platforms e INTEGRITY 10 0 2 on an x86 CPU e INTEGRITY 11 0 4 For more information on Modern C see Traditional vs Modern C in the User s Manual 4 3 Multicast Support Multicast is supported on all INTEGRITY platforms 4 4 Supported Transports Shared memory Supported enabled by default To clean up shared memory resources reboot the kernel UDPv4 Supported enabled by default UDPv6 Not supported TCP IPv4 Not supported 4 5 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is not supported on INTEGRITY platforms 4 6 Thread Configuration Table 4 5 Thread Settings for INTEGRITY Platforms lists the thread settings for INTEGRITY platforms 28 4 6 Thread Configurat
25. Instructions for VxWorks 653 Architectures Library Required RTI Required Format Libraries Kernel Components libnddscppz a libnddscz a Static Release libnddscorez a librticonnextmsgcppz a libnddscppzd a libnddsczd a See either libndds corezd a Table 10 11 Required Kernel Components for C librticonnextmsgcppzd a sbc8641Vx653 2 3gcc3 3 2 Traditional API libnddscpp so OF libnddsc so Table 10 12 Required Kernel Components for libnddscore so simpcVx653 2 3gcc3 3 2 librticonnextmsgcpp so Static Debug libnddscppd so libnddscd so libnddscored so librticonnextmsgcppd so libnddscz a Static Release libnddscorez a librticonnextmsgcz a libnddsczd a See either Static Debug libnddscorezd a Table 10 11 Required Kernel Components for librticonnextmsgezd a 558641 Vx653 2 3gcc3 3 2 libnddsc so OF libnddscore so Table 10 12 Required Kernel Components for librticonnextmsgc so simpcVx653 2 3gcc3 3 2 libnddscd so libnddscored so librticonnextms gced so 4The Connext DDS C C libraries are in lt NDDSHOME gt lib lt architecture gt Required Compiler Flags DRTL VXWORKS DRTI_VX653 DRTL VXWORKS DRTI_VX653 102 Chapter 10 VxWorks Platforms Table 10 4 Library Creation Details for All VxWorks Architectures Library Format RTI Architecture Compiler Flags Used by RTI ccpentium march x86 64 m64 mcmodel small mno red zone fno builtin ansi TOOL _ Staticor FAMILY gnu DTOOL gnu D_W
26. LD LIBRARY PATH LD LIBRARY PATH lt path to ndds libs gt CLASSPATH lt path to dex gt classes dex Table 3 4 Library Creation Details for Android Architectures RTI Architecture Compiler Flags Used by RTI PEL fpic DLINUX O Wall Wno unknown pragmas Wno address Wno unused but set variable Release DPtrIntType long DCSREAL IS FLOAT DCPU cortex a9 DTARGET armv7aAndroid2 3gcc4 81 DNDEBUG c Wp MD armv7aAndroid2 3gcc4 8 fpic DLINUX O Wall Wno unknown pragmas Wno address Wno unused but set variable Debug DPtrIntType long DCSREAL IS FLOAT DCPU cortex a9 DTARGET armv7aAndroid2 3gcc4 8V c Wp MD Rel target 1 4 1 4 armv7aAndroid2 3gcc4 8 EN dpud for Java Debug target 1 4 source 1 4 g 3 1 Support for Modern C API Connext DDS provides two different C APIs which we refer to as the Traditional C and Modem C APIs The Modern C API is available for all Android platforms For more information on Modern C see Traditional vs Modern C in the User s Manual 3 2 Multicast Support Multicast is available on supported Android platforms and is configured out of the box That is the default value for the initial peers list NDDS_DISCOVERY_ PEERS includes a multicast address See the API Reference HTML documentation for more information Multicast has not been tested for this release and so though available is not officially supported This should be addressed in a future rele
27. On VxWorks systems an application s process ID will often be the same across reboots This may cause logged errors during the discovery process or discovery may not complete successfully for the restarted application The workaround is to manually provide a unique appld each time the application starts The appld is stored in the DomainParticipant s WireProtocol QosPolicy There are two general approaches to provid ing a unique appld The first approach is to save the appId in NVRAM or the file system and then incre ment the appld across reboots The second approach is to base the appId on something that is likely to be different across reboots such as a time based register 113 10 6 Support for Modern C API 10 6 Support for Modern C API Connext DDS provides two different C APIs which we refer to as the Traditional C and Modern C APIs The Modern C API is available for all VxWorks platforms except VxWorks 5 5 and VxWorks 653 For more information on Modern C see Traditional vs Modern C in the User s Manual 10 7 Multicast Support Multicast is supported on VxWorks 5 x 7 x and VxWorks 653 on sbc8641d CPU platforms It is con figured out of the box That is the default value for the initial peers list NDDS_ DISCOVERY PEERS includes a multicast address See the API Reference HTML documentation for more information Multicast is not supported on the following platforms e VxWorks 653 on the SIMPC CPU
28. PEERS includes a multicast address See the online doc umentation for more information 7 3 Supported Transports Shared memory Supported and enabled by default UDPv4 Supported and enabled by default UDPv6 Not supported TCP IPv4 Supported 69 7 4 Monotonic Clock Support 7 4 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is not supported on OS X platforms 7 5 Thread Configuration Table 7 5 Thread Settings for OS X Platforms lists the thread settings for OS X platforms Table 7 6 Thread Priority Definitions for OS X Platforms lists the thread priority definitions 7 5 1 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Controlling CPU Core Affinity in the User s Manual is not available for OS X platforms Table 7 5 Thread Settings for OS X Platforms DDS_ Applicable Thread ThreadSettings_ Platform Specific Setting t cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO priority OS default thread priority Database thread stack_size OS default thread stack size cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported 70 7 6 Durable Writer History and Durable Reader State Features Table 7 5 Thread Settings for OS X Platforms DDS_ Applicable Thread ThreadSettings_ Platform Specific Setting DDS
29. a libssl so libcrypto so OpenSSL Libraries 8 12 Restarting Applications on QNX Systems Due to a limitation in the POSIX API ifa process is unexpectedly interrupted in the middle of a critical section of code that is protected by a shared mutex semaphore the OS is unable to automatically release the semaphore making it impossible to reuse it by another application The Connext DDS shared memory transport uses a shared mutex to protect access to the shared memory area across multiple processes It is possible under some extreme circumstances that if one application crashes or terminates ungracefully while executing code inside a critical section the other applications sharing the same resource will not be able to continue their execution If this situation occurs you must manually delete the shared memory mutex before re launching any application in the same DDS domain These libraries are in lt NDDSHOME gt lib lt architecture gt PThese libraries are in lt NDDSHOME gt lib lt architecture gt 84 Chapter 9 Solaris Platforms Table 9 1 Supported Solaris Platforms lists the architectures supported on Solaris operating sys tems Table 9 1 Supported Solaris Platforms Operating Compiler or System EP Software Development Kit GE AUTE gcc 3 3 2 186S0D 9gcc3 3 2 Solaris 2 9 UItraSPARC CC 5 4 Forte Dev 7 Sun One Studio 7 sparcSol2 9cc5 4 gcc3 4 2 UItraSPARC with native 64 bit sparc64Sol2 10g0c3 4 2 suppor
30. a thread with a larger stack or increase the default stack size of the shell task by recompiling the kernel For more information please see the Solutions on the RTI Customer Portal accessible from https support rti com 10 4 Libraries for RTP Mode on VxWorks 6 3 and Higher Systems Dynamic libraries are not available for VxWorks 6 3 and higher systems with Real Time Processes RTP mode on PowerPC PPC CPUs This is due to a platform limitation in VxWorks PPC platforms that puts an upper bound on the size of the Global Offset Table GOT for any single library which limits how many symbols the library can export Some Connext DDS libraries in particular libnddsc export a num ber of symbols that exceed this upper bound Dynamic libraries are available for VxWorks 6 3 and higher systems with RTP mode on Pentimum CPUs 10 5 Requirement for Restarting Applications When restarting a VxWorks application you may need to change the appId value In general this is only required if you still have other Connext DDS applications running on other systems that were talking to the restarted application If all the Connext DDS applications are restarted there should be no problem This section explains why this is necessary and how to change the appld All Connext DDS applications must have a unique GUID globally unique ID This GUID is composed of a hostld and an appld RTI implements unique applds by using the process ID of the application
31. create the shared memory manager for you Please follow these steps 1 Specify the path to your INTEGRITY distribution in the default gpj top level project file by adding the following line modify it according to the path to your INTEGRITY distribution os dir local applications integrity integrity 10 0 2 34 4 14 3 Shared Memory Limitations on INTEGRITY Systems 2 Build the project 3 Before running your Connext DDS application on a target download the posix_shm_manager file generated by the build onto the target The POSIX Shared Memory Manager will start automatically after the download and your applications will be able to use shared memory Notes e Only one posix_shm_manager is needed on a particular target INTEGRITY offers the option of building this posix_shm_manager inside the kernel Please refer to the INTEGRITY doc umentation e If you are already using shared memory through the POSIX library there may be a possible conflict e INTEGRITY 5 has two different types of POSIX library a single address space one or light and another one complete POSIX implementation Connext DDS uses the first one but will work if you are using the complete POSIX implementation 4 14 3 Shared Memory Limitations on INTEGRITY Systems If several applications are running on the same INTEGRITY node and are using shared memory once an application is stopped it cannot be restarted When the application is stopped gracefully
32. dylib libnddscppd dylib or libnddscpp2d dylib Dynamic Debug libnddscd dylib libnddscored dylib librticonnextmsgcppd dylib 2Choose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API BThe Connext DDS C C libraries are in lt NDDSHOME gt 1lib lt architecture lt NDDSHOME gt is where Connext DDS is installed see Paths Mentioned in Documentation Section 1 1 on page 3 The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 66 Chapter 7 OS X Platforms Table 7 2 Building Instructions for OS X Architectures Required System Libraries Library Format libnddscz a Static Release libnddscorez a librticonnextmsgcz a dynamic Ipthread libnddsczd a Static Debug libnddscorezd a lc single module librticonnextmsgezd a DRTI UNIX ldl Im Ipthread libnddsc dylib DRTI DARWIN API Required RTI Libraries Required Compiler Flags libnddscore dylib DRTI DARWIN10 librticonnextmsgc dylib i libnddscd dylib Dynamic Debug libnddscored dylib librticonnextms gcd dylib nddsjava jar N A DRTI_64BIT None required nddsjavad jar rticonnextms gd jar AChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API gt The Connext DDS C C libraries are in lt NDDSHOME gt 1lib lt architecture lt NDDSHOME gt is where C
33. for RTI Threads Support for controlling CPU core affinity described in Controlling CPU Core Affinity in the User s Manual is not available for QNX platforms Table 8 5 Thread Settings for QNX Platforms DDS T a Applicable Thread ThreadSettings t Platform Specific Setting Asynchronous flushing stack size 32 1024 thread ims 1 rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO a Database thread CPU core affinity not supported CPU core A AAA RRA o not supported 80 8 7 Durable Writer History and Durable Reader State Features Table 8 5 Thread Settings for QNX Platforms DDS ThreadSettings t i DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS Dodd FLOATING POINT A e O Event thread Applicable Thread Platform Specific Setting CPU core affinity not supported CPU core affinity not supported DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT i th CPU core affinity not supported cpu_rotation CPU core affinity not supported Table 8 6 Thread Priority Definitions for QNX Platforms Thread Priority Definition Operating System Priority mask THREAD PRIORITY ABOVE NORMAL THREAD PRIORITY NORMAL THREAD PRIORITY BELOW NORMAL THREAD PRIORITY LOW 8 7 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on QNX platforms 81 8 8 Libraries Required for Using Distributed Logger 8 8 Libr
34. for RTI Threads Table 5 7 Thread Settings for Linux Platforms DDS_ Applicable Thread ThreadSettings_ Platform Specific Setting t OS default thread type OS default thread priority Asynchronous Publisher Asynchronous OS default thread stack size flushing thread Empty CPU list Supported on Linux and SUSE platforms T DDS THREAD SETTINGS CPU NO ROTATION Supported on epu rotanon Linux and SUSE platforms DDS THREAD SETTINGS STDIO OS default thread priority Database thread OS default thread Sere Empty CPU list Supported on Linux and SUSE platforms T DDS THREAD SETTINGS CPU NO ROTATION Supported on cpu_rotahon Linux and SUSE platforms k DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS TE FLOATING POINT OS default thread priority Event thread OS default thread stack size Empty CPU list Supported on Linux and SUSE platforms rain DDS THREAD SETTINGS CPU NO ROTATION Supported on pu Linux and SUSE platforms DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING_POINT DDS THREAD SETTINGS CPU NO ROTATION Supported on cpu romanon Linux and SUSE platforms 50 5 6 Durable Writer History and Durable Reader State Features Table 5 8 Thread Priority Definitions for Linux Platforms Thread Priority Definition Operating System Priority THREAD PRIORITY DEFAULT 9999999 THREAD PRIORITY HIGH 9999999 THREAD PRIORITY ABOVE NORMAL 9999999 THREAD PRIORITY NORMAL 9999999 THREAD PRIORITY BELOW NORMAL 9999999 THREAD PRIOR
35. in Controlling CPU Core Affinity in the User s Manual is not available for LynxOS platforms Table 6 6 Thread Settings for LynxOS Platforms DDS _ ThreadSettings t Asynchronous flushing stack size 16 1024 thread Applicable Thread Platform Specific Setting cpu rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO Database thread 16 1024 CPU core affinity not supported CPU core affinity not supported stack size 4 16 1024 cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported i DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT Event thread DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS BUDE FLOATING POINT priority ReceiverPool threads uiuos 4 16 1024 cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported 62 6 6 Durable Writer History and Durable Reader State Features Table 6 7 Thread Priority Definitions for LynxOS Platforms Thread Jo ei 0000 Definition Ra ood Priority THREAD PRIORITY ABOVE NORMAL THREAD PRIORITY NORMAL THREAD PRIORITY BELOW NORMAL THREAD PRIORITY LOW 6 6 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on LynxOS platforms 6 7 Distributed Logger Support RTI Distributed Logger is not supported on LynxOS platforms 6 8 Libraries Required for Using Monitoring Make sure you are consistent
36. in your use of static dynamic debug and release versions of the libraries For example if your Connext DDS application is linked with the static release version of the Connext DDS libraries you will need to also use the static release version of the monitoring library Do not link both static and dynamic libraries Similarly do not mix release and debug libraries If you are statically linking your application with DDS libraries and you want to add monitoring to your application you will also need to statically link the monitoring library The library cannot be loaded dynam ically strictly through the QoS profile because it also depends on DDS to publish its data Therefore it depends on DDS the DDS functionality would cause duplicate symbols to be found resulting in the ter mination of the process Note If you are plan to use static libraries the RTI library from Table 6 8 Additional Libraries for Using Monitoring must appear first in the list of libraries to be linked 63 6 9 IP Fragmentation Issues Table 6 8 Additional Libraries for Using Monitoring Static Release Static Debug Dynamic Release Dynamic Debug librtimonitoringz a librtimonitoringzd a librtimonitoring so librtimonitoringd so 6 9 IP Fragmentation Issues The LynxOS platforms do not support IP fragmentation over the loopback interface due to a bug in the OS see below The maximum size of a UDP packet that can be sent over the loopback interface is therefore l
37. index jsp topic 2Fcom ibm xlcpp121 aix d oc 2F compiler _ref 2Fopt Idbl128 html 2 1 Support for Modern C API Table 2 4 Library Creation Details for AIX Architectures Library Format ne Compiler Flags Used by RTI Architecture Static amp Dynamic All supported AIX target 1 4 source 1 4 EE architectures for Java Debug target 1 4 source 1 4 g 2 1 Support for Modern C API Connext DDS provides two different C APIs which we refer to as the Traditional C and Modem C APIs The Modern C API is available for all AIX 7 1 platforms For more information on Modern C see Traditional vs Modern C in the User s Manual 2 2 Multicast Support Multicast is supported on all AIX platforms and is configured out of the box That is the default value for the initial peers list NDDS_DISCOVERY_ PEERS includes a multicast address See the API Reference HTML documentation for more information 2 3 Supported Transports e Shared memory Supported and enabled by default e UDPv4 Supported and enabled by default e UDPv6 Not supported TCP IPv4 Not supported 4Connext DDS was built using the xIC_r compiler See IBM s XLC reference manual for a description of the different compilers For a list of the additional settings defined by default for the xIC r compiler see the file etc vac cfg 53 bL inking without the 128 bit versions of the C Runtime Library when your program uses 128 bit lon
38. lib rtidlezd lib rtidlc dll rtidled dll M Ar rtidlcppz lib rtidlcppzd lib rtidlcpp dll rtidlcppd dll 11 14 Libraries Required for Using Monitoring Make sure you are consistent in your use of static dynamic debug and release versions of the libraries For example if your Connext DDS application is linked with the static release version of the Connext DDS libraries you will need to also use the static release version of the monitoring library Do not link both static and dynamic libraries Similarly do not mix release and debug libraries If you are statically linking your application with DDS libraries and you want to add monitoring to your application you will also need to statically link the monitoring library The library cannot be loaded dynam ically strictly through the QoS profile because it also depends on DDS to publish its data Therefore it depends on DDS the DDS functionality would cause duplicate symbols to be found resulting in the ter mination of the process Table 11 10 Additional Libraries for Using Monitoring Static Release Static Debug Dynamic Release Dynamic Debug rtimonitoringz lib rtimonitoringzd lib rtimonitoring lib rtimonitoringd lib Psapi lib Psapi lib rtimonitoring dll rtimonitoringd dll 11 15 Libraries Required for Using RTI Secure WAN Transport APIs To use the Secure WAN Transport APIs add the libraries from Table 11 11 Additional Libraries for Using RTI Secure WAN Transport APIs on Windows System
39. or ungracefully any new application on the same domain index within the same DDS domain will fail to start until the shared memory manager is also restarted Additionally if the application is stopped ungracefully the remaining applications will print several error messages such as the following until Connext DDS purges the stopped application from its database Resource Manager send error 0x9 This error message is logged from INTEGRITY s POSIX shared memory manager not from Connext DDS The error message is benign and will not prevent the remaining applications from communicating with each other or with application on other nodes The workaround is to either restart the stopped application with a different participant index or shut down all the other applications and the shared memory manager then restart everything 4 15 Using rtiddsping and rtiddsspy on PowerPC INTEGRITY Systems While the RTI libraries for INTEGRITY can be used with any BSP providing the PowerPC processor falls under the same category for example the ppc7400 RTI libraries can be used on any target with a PPC74xx processor rtiddsping and rtiddsspy are provided as executables and therefore are BSP depend ent You will not be able to run them successfully on your target if it is not compatible with the BSP listed 35 4 16 Issues with INTEGRITY Systems in the architecture name such as mvme5100 7400 Please refer to your hardware documentation for pe
40. resource names used by Connext DDS begin with RTIOsapiSharedMemorySem To see a list of shared semaphores enter ls dev sem RTIOsapiSharedMemorySemMutex To clean up the shared semaphore resources remove the files listed in dev sem The permissions for the semaphores created by Connext DDS are modified by the process umask value If you want to have shared memory support between different users run the command umask 000 to change the default umask value to 0 before running your Connext DDS application UDPv4 Supported and enabled by default UDPv6 Supported The transport is not enabled by default the peers list must be modified to support IPv6 No Traffic Class support To use the UDPv6 transport the network stack must provide IPv6 capability Enabling UDPv6 may involve switching the network stack server and setting up IPv6 route entries TCP IPv4 Supported on i86QNX6 5qcc_cpp4 4 2 and armv7aQNX6 5 0SPlqcc_cpp4 4 2 TLS Supported on 1860NX6 5qcc cpp4 4 2 and armv7aQNX6 5 0SPlqcc_cpp4 4 2 79 8 5 Monotonic Clock Support 8 5 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is supported on QNX plat forms 8 6 Thread Configuration Table 8 5 Thread Settings for QNX Platforms lists the thread settings for QNX platforms Table 8 6 Thread Priority Definitions for QNX Platforms lists the thread priority definitions 8 6 1 Support for Controlling CPU Core Affinity
41. 0 rticonnextdotnet45 dll for NET 4 5 rticonnextdotnet45 1 dll for NET 4 5 1 One of these depending on your version of NET nddsdotnetd dll for NET 2 0 nddsdotnet40d dll for NET 4 0 nddsdotnet45d dll for NET 4 5 nddsdotnet45 1d dll for NET 4 5 1 And one of these depending on your version of NET rticonnextdotnetd dll for NET 2 0 rticonnextdotnet40d dll for NET 4 0 rticonnextdotnet45d dll for NET 4 5 rticonnextdotnet45 1 d dll for NET 4 5 1 nddsjava jar rticonnextmsg jar nddsjavad jar rticonnextmsgd jar Required System Required Compiler Libraries Flags AChoose nddscpp for the Traditional C API or nddscpp2 for the Modern C API bThe RTI C C Java libraries are in lt NDDSHOME gt lib lt architecture gt Jar files are in lt NDDSHOME gt lib java 131 Chapter 11 Windows Platforms Table 11 3 Building Instructions for Windows Target Architectures Library Format Static Release Static Debug Dynamic Release Dynamic Debug Static Release Static Debug Dynamic Release Dynamic Debug RTI Libraries or Jar Files b nddscz lib nddscorez lib rticonnextmsgcz lib nddsczd lib nddscorezd lib rticonnextms gezd lib nddsc lib nddscore lib rticonnextmsgc lib nddscd lib nddscored lib rticonnextms gcd lib nddscppz lib nddscz lib nddscorez lib rticonnextms gcppz lib nddscppzd lib nddsczd lib nddscorezd lib rticonnextms gcppzd lib n
42. 0 DVXWORKS MAJOR VERSION 5 DVXWORKS MINOR VERSION S O Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU PPC603 DNDEBUG c Wp MD Static or Dynamic Release ppc603Vx5 5gcc mcpu 603 G 0 fno builtin mlongcall D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 5 DVXWORKS MINOR VERSION S O Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU PPC603 c Wp MD Static or Dynamic Debug Static or mcpu 604 G 0 fno builtin mlongcall D PROTOTYPE 5 0 DVXWORKS MAJOR Dynamic VERSION 5 DVXWORKS MINOR VERSION S O Wall Wno unknown pragmas Release DRTS VXWORKS DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD ppc604Vx5 5gcc Static or mcpu 604 G 0 fno builtin mlongcall D PROTOTYPE 5 0 g DVXWORKS MAJOR Dynamic VERSION 5 DVXWORKS MINOR VERSION S O Wall Wno unknown pragmas Debug DRTS VXWORKS DPtrIntType long DCPU PPC604 c Wp MD 107 Chapter 10 VxWorks Platforms Table 10 4 Library Creation Details for All VxWorks Architectures Library Format RTI Architecture Compiler Flags Used by RTI mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align mno implicit fp ansi D_ Staticor WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 3 O Wall Wno unknown pragmas DRTS _ Release VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD ppc604Vx6 3gcc3 4 4 mcpu 604 fno builtin
43. 06 Chapter 10 VxWorks Platforms Table 10 4 Library Creation Details for All VxWorks Architectures Library Format RTI Architecture Compiler Flags Used by RTI mcpu 405 fno builtin mlongcall DTOOL gnu mstrict align msoft float ansi D_WRS _ Staticor KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS _ Dynamic MINOR_VERSION 6 O Wall Wno unknown pragmas DRTS_VX WORKS Release DTOOL gnu DTOOL_FAMILY gnu DPtrIntType long DCPU PPC405 DNDEBUG c Wp MD ppc405Vx6 6gcc4 1 2 mcpu 405 fno builtin mlongcall DTOOL gnu mstrict align msoft float ansi D_WRS_ Staticor KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas DRTS _ Debug VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC405 c Wp MD msoft float mlongcall mregnames mstrict align ansi DTOOL gnu mrtp D_ Static PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR Release VERSION 6 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL sfgnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 DNDEBUG c Wp MD ppc405Vx6 6gcc4 1 2 rtp msoft float mlongcall mregnames mstrict align ansi DTOOL gnu mrtp fPIC shared D_ Static PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR Debug VERSION 6 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL sfgnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 c Wp MD mcpu 603 G 0 fno builtin mlongcall D_ PROTOTYPE 5
44. 2 222 2222 c eee cece eee eee eee 34 4 14 3 Shared Memory Limitations on INTEGRITY Systems 2 00 00 eee cece e cece cece nere 35 4 15 Using rtiddsping and rtiddsspy on PowerPC INTEGRITY Systems 000000 0 22 cece eee eee ee 35 4 16 Issues with INTEGRITY Systems ooo ee eee eee ee 36 4 16 1 Delay When Writing to Unreachable Peers 200 0 00 eeeeee 36 4 16 2 Linking with libivfs a without a File System 02 2 220 loc s se nnns 36 4 16 3 Compiler Warnings Regarding Unrecognized pragma Directives 022202022 2 220 ee 36 4 16 4 Warning when Loading Connext DDS Applications on INTEGRITY Systems 36 Chapter 5 Linux Platforms 5 1 Support for Modern CH API oo eee eee ele e e eren 47 5 2 Mu lticast SUPPO eres ed dao dd rosado Eyed LU So OCD o Lao tr 47 5 Sisupportedy Transports 4 219 2 hoe eh eerte Nod ad O teed Dee eR es 48 5 3 1 Shared Memory Support it a a r O te 48 5 4 Monotonic Clock SUppOTRt Vta Ae dee tk ete Sui ahd seer DULL RE UR A EN Dg 48 5 5 Ihread Gonfig ratlon 4 5 ovs du e us de eat 48 5 5 1 Native POSIX Thread Library NPTL Requirements ooooccccccccccccccccccnccccccccccccnnnncccccccoo 49 5 5 2 Support for Controlling CPU Core Affinity for RTI Threads 2 2 222222 e eee eee 49 5 6 Durable Writer History and Durable Reader State Features oooccccccccccccccccccccccccccccccccccnnncccccccooo 51 5 7 Libraries Required for Using Distributed Logger ooo
45. 2 and 11 0 4 Section 4 1 on page 27 dSee Required Patches for INTEGRITY 10 0 2 and 11 0 4 Section 4 1 on page 27 For use with Windows and Solaris hosts as supported by Green Hills Software 24 Chapter 4 INTEGRITY Platforms Table 4 3 Running Instructions for INTEGRITY Architectures provides details on the environment vari ables that must be set at run time for an INTEGRITY architecture Table 4 4 Library Creation Details for INTEGRITY Architectures provides details on how the libraries were built This table is provided strictly for informational purposes you do not need to use these para meters to compile your application You may find this information useful if you are involved in any in depth debugging 25 Chapter 4 INTEGRITY Platforms Table 4 2 Building Instructions for INTEGRITY Architectures Library Format Static Release C Traditional and Modern APIs Static Debug Static Release Static Debug Required System Libraries Required Compiler Flags Required RTI Libraries2bcd libnddscppz a or libnddscpp2z a libnddscz a libnddscorez a librticonnextmsgcppz a libnddscppzd a or libnddscpp2zd a libnddsczd a libnddscorezd a libnddscppzd dba or libnddscpp2zd dba libsocket a libnet a RTI INTY exceptions libposix a libnddsczd dba libnddscorezd dba librticonnextmsgezd dba librticonnextmsgcppzd a libnddscz a libnddscorez a librticonnextmsgcz a libnddsczd a
46. 3 architectures dl Insl Im L usr lib nptl Ipthread lrt All other Linux architectures ldl Insl Im Ipthread Irt Required Compiler Flags 64 bit architectures DRTI UNIX m64 32 bit architectures DRTI UNIX m32 For 186Linux3gcc4 8 2 and x64Linux3gcc4 8 2 when running on Ubuntu CPU for dynamic release and dynamic debug libraries also use the following WI no as needed 2Choose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API PRTI C C Java libraries are in lt NDDSHOME gt lib lt architecture gt The jar files are in lt NDDSHOME gt lib java The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 42 Chapter 5 Linux Platforms Table 5 4 Building Instructions for Linux Architectures Required RTI Required Libraries System Required Compiler Flags or Jar Files2bc Libraries Library An Format libnddscz a Static libnddscorez a Release All 64 bit architectures librticonnextms gcz a Linux2 6gcc3 DRTI UNIX m64 architectures Static Tree de 1dl Insl Im Debug librticonnextms m L usr lib nptl 32 bit architectures SAO Ipthread Irt DRTI UNIX m32 libnddsc so libnddscore so M All other Linux For iS6Linux3gcc4 8 2 and x64Linux3gcc4 8 2 when running on librticonnextmsgc so architectures Ubuntu
47. 3 sbc8641d gcc 2 3 sbc8641Vx653 2 3gcc3 3 2 SIMPC gcc 3 3 2 simpcVx653 2 3gcc3 3 2 AFor use with Windows and or Solaris Hosts as supported by Wind River Systems 98 Chapter 10 VxWorks Platforms The following tables list the libraries you will need to link into your application and the required compiler flags e Table 10 2 Building Instructions for VxWorks 5 x 7 x Architectures e Table 10 3 Building Instructions for VxWorks 653 Architectures See also e Libraries Required for Using Distributed Logger Section 10 12 on page 118 e Libraries Required for Using Monitoring Section 10 13 on page 119 Make sure you are consistent in your use of static dynamic debug and release versions of the libraries Do not link both static and dynamic libraries Similarly do not mix release and debug libraries Compiling a Connext DDS application for VxWorks depends on the development platform For more information such as specific compiler flags see the VxWorks Programmer s Guide Table 10 4 Library Creation Details for All VxWorks Architectures provides details on how the VxWorks libraries were built We recommend that you use similar settings Cross compiling for any VxWorks platform is similar to building for a UNIX target To build a VxWorks application create a makefile that reflects the compiler and linker for your target with appropriate flags defined There will be several target specific compile flags you must set to build
48. AL IS FLOAT DCPU AMD64 DTARGET x64Win64V 2013 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V S2013 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi IMD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V S2013 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MTd EHsc RTC1 D CRT SECURE NO DEPRECATE c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V 82013 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c 11 1 Requirements when Using Microsoft Visual Studio When Using Visual Studio 2008 Service Pack 1 Requirement You must have Visual Studio 2008 Service Pack 1 or the Microsoft Visual C 2008 SP1 Redistributable Package installed on the machine where you are running an application linked with dynamic libraries 138 11 1 Requirements when Using Microsoft Visual Studio This includes dynamically linked C C and all NET and Java applications The Microsoft Visual C 2008 SP1 Redistributable Package can be downloaded from the following Microsoft websites For x86 architectures http www microsoft com downloads details aspx familyid A5C84275 3B97 4AB7 A40D 3802
49. APIs Table 11 13 Additional Libraries for using RTI TCP Transport APIs on Windows Systems with TLS Enabled Library Format RTI TLS Libraries Static Debug nddstlszd dll ssleay32 lib OpenSSL Libraries libeay32 lib The libraries are in lt NDDSHOME gt lib lt architecture gt 147
50. B2AF5FC2 amp displaylang en For x64 architectures http www microsoft com downloads details aspx FamilyID ba9257ca 337f 4b40 8 14 157cf dffee4e amp displaylang en When Using Visual Studio 2010 Service Pack 1 Requirement You must have Visual Studio 2010 Service Pack 1 or the Microsoft Visual C 2010 SP1 Redistributable Package installed on the machine where you are running an application linked with dynamic libraries This includes dynamically linked C C and all NET and Java applications To run an application built with debug libraries of the above RTI architecture packages you must have Visual Studio 2010 Service Pack 1 installed The Microsoft Visual C 2010 Service Pack 1 Redistributable Package can be obtained from the fol lowing Microsoft websites For x86 architectures http www microsoft com download en details aspx 1d 5555 For x64 architectures http www microsoft com download en details aspx 1d 14632 When Using Visual Studio 2012 Redistributable Package Requirement You must have the Visual C Redistributable for Visual Studio 2012 Update 3 installed on the machine where you are running an application linked with dynamic libraries This includes dynamically linked C C and all NET and Java applications You can download Visual C Redistributable for Visual Studio 2012 Update 3 from this Microsoft web site http www microsoft com en ca download details aspx id 30679 When Using Visual Studio 2013
51. CATE c MDd DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGE T 186Win32VS2012V Dynamic DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI Debug EHsc RTC1 D CRT SECURE NO DEPRECATE c MT DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET 186Win32V82013 Static DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi Release EHsc D_ CRT SECURE NO DEPRECATE DNDEBUG c DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET 186Win32V82013 Dynamic DWIN32 D_ WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Z Release MD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c 186Win32VS2013 DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET 186Win32V82013 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MTd EHsc RTC1 D CRT SECURE NO DEPRECATE c DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGE T i86Win32V 2013 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c 136 Chapter 11 Windows Platforms Table 11 5 Library Creation Details for Windows Architectures RTI Architecture x64Win64V S2008 Note linker requires MACHINE X64 option x64Win64V S2010 Note linker requires MACHINE X 64 option Library Format Static Release Dynamic Release Static Debug Dynamic Debug Static Release Dynamic Release Compiler Fl
52. D POSIX THREADS CALLS D NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU PPC7400 DTARGET ppc7400Lynx4 2 0gcc3 2 2V c Wp MD 59 6 1 Support for Modern C API Table 6 5 Library Creation Details for LynxOS Architectures Library Format RTI Architecture Compiler Flags Used by RTI Static amp Dynamic mcpu 7400 maltivec mabi altivec fno exceptions mthreads mshared fPIC D_POSIX_ THREADS CALLS D NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU PPC7400 DTARGET ppc7400Lynx5 0 0gcc3 4 3 DNDEBUG c Wp MD Release ppc7400Lynx5 0 0gec3 4 3 mcpu 7400 maltivec mabi altivec fno exceptions mthreads mshared fPIC D POSIX THREADS CALLS D NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU PPC7400 DTARGET ppc7400Lynx5 0 0gcc3 4 3 c Wp MD mcpu 750 fno exceptions mthreads mshared fPIC D POSIX THREADS CALLS D Release NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntType long DCPU PPC750 DTARGET ppc750Lynx4 0 0gcec3 2 2 DNDEBUG c Wp MD ppc750Lynx4 0 0gcc3 2 2 mcpu 750 fno exceptions mthreads mshared fPIC D_POSIX_THREADS_CALES D__ NO INCLUDE WARN g O Wall Wno unknown pragmas DPtrIntType long DCPU PPC750 DTARGET ppc750Lynx4 0 0gcc3 2 21 c Wp MD 6 1 Support for Modern C API Connext DDS provides two different C APIs which we refer to a
53. DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Release Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 DNDEBUG c Wp MD ppc604Vx6 6gcc4 1 2 rtp mhard float mlongcall mregnames mstrict align ansi mrtp fPIC shared D Static PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR _ Debug VERSION 6 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 c Wp MD mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align ansi D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 7 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD Static or Dynamic Release ppc604Vx6 7gcc4 1 2 mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align ansi D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 7 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL_FAMILY gnu DPtrIntType long DCPU PPC604 c Wp MD Static or Dynamic Debug mhard float mlongcall mregnames mstrict align ansi mrtp D PROTOTYPE 5 0 Static DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 7 O Wall Release Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu ppc604Vx6 7gcc4 1 2 rtp DPtrIntType long DCPU PPC32 DNDEBUG c Wp MD ppc604Vx6 7gco4 1 2 smp mhard float mlongcall mregnames mstric
54. INTEGRITY Platforms 4 1 Required Patches for INTEGRITY 10 0 2 and 11 0 4 20 l loool celle ccc cee sss e sse eser 27 4 2 Support for Modern CFFAPT eiere aa aaa eee a 28 4 3 Multicast Support A A aces RI le rime E ra reel M ren e a e aaa ce Se eS 28 4 4 Supported Transports Li en lle ed y ute Ad el 28 4 5 Monotonic Clock Support _ 200000000 e nananana 28 4 6 Thread Configuration 422 02820 sot ts cdl ee A OE tale t eR 28 4 6 1 Socket Enabled and POSIX Enabled Threads are Required 2 2 2 loc lee ee ee cece cece eee eee eeeees 31 4 6 2 Support for Controlling CPU Core Affinity for RTI Threads 2 0 0020022 c eee cece eee eee eee 31 4 7 Durable Writer History and Durable Reader State Features 00 00 02 c coe e eee ec eee ee eee cece ee eeee 31 4 8 Libraries Required for Using Distributed Logger _ 222222202 ooo eee 31 4 9 Libraries Required for Using Monitoring 2 2 eee rrr lr lll 32 4 10 Request Reply Communication Pattern 202 ooo cee a nono 32 4 11 Diagnostics on INTEGRITY Systems occ nes 33 4 12 Running over IP Backplane on a Dy4 Champ AVII Board 2 2 2 0 coco cece ccc e eese 33 4 13 Multi NIC Support on INTEGRITY 5 0 porgir eo pis ane ie i s rE iS err lese ler gA 33 4 14 Out of the box Transport Compatibility with Other Connext DDS Platforms LLLuuuuuuuuuuuuuuu 33 4 14 1 Smaller Shared Memory Receive Resource Queue Size 2 2 34 4 14 2 Using Shared Memory on INTEGRITY Systems 22
55. ITY LOW 9999999 Table 5 9 Thread Kinds for Linux Platforms Thread Kinds Operating System Configuration DDS THREAD SETTINGS REALTIME PRIORITY Set schedule policy to SCHED FIFO N A N N DDS THREAD SETTI GS PRIORITY ENFORCE 5 6 Durable Writer History and Durable Reader State Features To use the Durable Writer History and Durable Reader State features you must install a relational data base such as MySQL In principle you can use any database that provides an ODBC driver since ODBC is a standard However not all ODBC databases support the same feature set Therefore there is no guarantee that the persistent durability features will work with an arbitrary ODBC driver We have tested the following driver MySQL ODBC 5 1 44 Starting with 4 5e support for the TimesTen database has been removed See the Linux programmer s manuals for more information 51 5 7 Libraries Required for Using Distributed Logger To use MySQL you also need MySQL ODBC 5 1 6 or higher and UnixODBC 2 2 12 or higher The Durable Writer History and Durable Reader State features have been tested with the following Linux architectures e 186Linux2 6gcc4 1 1 e i86Linux2 6gcc4 6 3 e x64Linux2 6gcc4 1 1 e x64Linux2 6gcc4 6 3 For information on database setup please see the RTI Connext DDS Core Libraries Getting Started Guide Addendum for Database Setup 5 7 Libraries Required for Using Distributed Logger RTI Distributed L
56. Monotonic clock support e Thread configuration e Durable Writer History and Durable Reader State features support The Java API is not supported on LynxOS platforms If your application requires support for Java on LynxOS please contact your RTI account manager 1 1 Paths Mentioned in Documentation 1 1 Paths Mentioned in Documentation The documentation refers to e lt NDDSHOME gt This refers to the installation directory for Connext DDS The default installation paths are Mac OS X systems Applications rti_connext_dds 5 2 0 UNIX based systems non root user home your user name rti_connext_dds 5 2 0 UNIX based systems root user opt rti_connext_dds 5 2 0 Windows systems user without Administrator privileges lt your home directory gt rti_connext_dds 5 2 0 Windows systems user with Administrator privileges C Program Files rti_connext_dds 5 2 0 64 bit machines C Program Files x86 rti_connext_dds 5 2 0 32 bit machines You may also see NDDSHOME or NDDSHOME which refers to an environment variable set to the installation path Wherever you see lt NDDSHOME gt used in a path replace it with your installation path Note for Windows Users When using a command prompt to enter a command that includes the path C Program Files or any directory name that has a space enclose the path in quotation marks For example SCi Progrian Piles Wet Comme _cela 5 2 0 oim ctickelsgein or if you ha
57. NET IP OUTPUT DE NETINET RADIX DE Z ETINET RAW IP DE_NETINET_ROUTE DE Z ETINET SYS_SOCKET DE Z ETIN es T E DP_USRREQ DE NETINET UIPC DOM DE Z ETIN es T E IPC_MBUF DE Z ETIN es T E IPC_SOCK DE NETIN ies T UIPC SOCK2 DE Z ETIN q T_UNIXLIB DE NETMASK GET aSELECT WDB COMM TYPE can only have one type at a time In order to add INCLUDE WDB _ COMM END you should remove INCLUDE WDB COMM PIPE bInstall partition socket driver v1 3 Follow instructions from Wind River for the installation dInstall partition socket driver v1 3 Follow instructions from Wind River for the installation 122 10 14 Increasing the Receive Socket Buffer Size Table 10 12 Required Kernel Components for simpcVx653 2 3gcc3 3 2 PInstall partition socket driver v1 3 Follow instructions from Wind River for the installation 123 10 14 Increasing the Receive Socket Buffer Size Table 10 12 Required Kernel Components for simpcVx653 2 3gcc3 3 2 INCLUDE NETINET IN INCLUDE WDB COMM END INCLUDE NETINET IN CKSUM INCLUDE WINSIO aSELECT WDB COMM TYPE can only have one type at a time In order to add INCLUDE WDB _ COMM END you should remove INCLUDE WDB COMM PIPE PInstall partition socket driver v1 3 Follow instructions from Wind River for the installation 124 Chapter 11 Windows Plat
58. OR VERSION 5 Wno unknown pragmas Debug DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU SIMNT c Wp MD 111 10 1 Required Makefile Change for VxWorks 7 0 Platforms 10 1 Required Makefile Change for VxWorks 7 0 Platforms For VxWorks 7 0 platforms only After you run rtiddsgen edit the generated makefile to specify which Vxworks Source Build VSB you want to use In the generated makefile find this line and change it to match your VSB directory 32 VSB DIR Specify your VSB directory here Note RTI uses VSB 2 1 2 2 to build the Connext DDS libraries for VxWorks 7 0 10 2 Request Reply Communication Pattern The Connext DDS Professional Research Evaluation and Basic packages include support for the Request Reply Communication Pattern for all platforms in Table 10 1 Supported VxWorks Target Plat forms and all programming languages except as noted below When using C the following platforms do not support the Request Reply Communication Pattern e ppc603Vx5 5gcc e ppc604Vx5 5gcc When using a Connext DDS dynamic library for C Request Reply for kernel mode you need to per form an extra host processing step called munching and apply it to any application that is linking against the C Request Reply library In VxWorks kernel mode before a C module can be downloaded to the VxWorks kernel it must undergo an additional host processing step known as munching This step is necessary for properly ini ti
59. PRIORITY NORMAL 30 4 6 1 Socket Enabled and POSIX Enabled Threads are Required Table 4 7 Thread Priority Definitions for INTEGRITY 10 Platforms Thread Priority Definitions Operating System Priority THREAD PRIORITY LOW 1 4 6 1 Socket Enabled and POSIX Enabled Threads are Required On INTEGRITY platforms Connext DDS internally relies on the POSIX API for many of its system calls As a result any thread calling Connext DDS must be POSIX enabled By default the Initial thread of an address space is POSIX enabled provided the address space has been linked with libposix a Addi tional user threads that call Connext DDS must be spawned from the Initial thread using pthread_create Only then is the created thread also POSIX enabled Note that tasks created at build time using the Integ rate utility are not POSIX enabled Furthermore threads calling Connext DDS must be socket enabled This can be achieved by calling InitLibSocket before making any Connext DDS calls and calling ShutdownLibSocket before the thread terminates Note that an Initial thread is by default socket enabled when the address space is linked with libsocket a Please refer to the IVTEGRITY Development Guide for more information 4 6 2 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Controlling CPU Core Affinity in the User s Manual is not available for INTEGRITY platforms 4 7 Durable Wri
60. RS_KERNEL D_ PROTOTYPE 5 0 O DRTI_64BIT Dynamic DRTI X64CPU DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR Release VERSION 9 Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD pentium64V x6 9gcc4 3 3 ccpentium march x86 64 m64 mcmodel small mno red zone fno builtin ansi TOOL _ Staticor FAMILY gnu DTOOL gnu D WRS KERNEL D_ PROTOTYPE 5 0 g DRTI 64BIT Dynamic DRTI X64CPU DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR Debug VERSION 9 Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT Wp MD ccpentium march x86 64 m64 mcmodel small mno red zone fno builtin ansi mrtp Staticor TOOL FAMILY gnu DTOOL gnu D_WRS KERNEL D_ PROTOTYPE 5 0 0 Dynamic DRTI 64BIT DRTI X64CPU DVXWORKS MAJOR_VERSION 6 DVXWORKS _ Release MINOR_VERSION 9 Wall Wno unknown pragmas DRTS_VX WORKS DPtrIntType 1 DCSREAL IS FLOAT DNDEB Wp MD pentium64Vx6 9gcc4 3 3 ee _1S_FLO pall rtp ccpentium march x86 64 m64 mcmodel small mno red zone fno builtin ansi mrtp Staticor TOOL FAMILY gnu DTOOL gnu D WRS KERNEL D_ PROTOTYPE 5 0 g Dynamic DRTI 64BIT DRTI X64CPU DVXWORKS MAJOR VERSION 6 DVXWORKS _ Debug MINOR VERSION Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT Wp MD march pentium fno builtin ansi DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragm
61. RTI Connext DDS Core Libraries Platform Notes Version 5 2 0 rt 2015 Real Time Innovations Inc All rights reserved Printed in U S A First printing June 2015 Trademarks Real Time Innovations RTI NDDS RTI Data Distribution Service DataBus Connext Micro DDS the RTI logo IRTI and the phrase Your Systems Working as one are registered trademarks trademarks or service marks of Real Time Innovations Inc All other trademarks belong to their respective owners Copy and Use Restrictions No part of this publication may be reproduced stored in a retrieval system or transmitted in any form including electronic mechanical photocopy and facsimile without the prior written permission of Real Time Innovations Inc The software described in this document is furnished under and subject to the RTI software license agreement The software may be used or copied only under the terms of the license agree ment Technical Support Real Time Innovations Inc 232 E Java Drive Sunnyvale CA 94089 Phone 408 990 7444 Email support rti com Website https support rti com Chapter 1 Supported Platforms 1 1 Paths Mentioned in Documentation ns 3 Chapter 2 AIX Platforms 2 1 Suppor fot Modem CARAPL aa a a en dee She mee aes 10 22 Multicast SUPPO dl a Sal te 10 2 3 Supported Transports 253 23 td o o le ales ena RO 10 2 3 1 Notes for Using Shared Memory oooccccccccc e eee ann 11 2 4 Monotonic Clock Support osas
62. RTI TCP Transport APIs Secure WAN Transport Installation Guide for details To use the Secure WAN Transport APIs link against the additional libraries in Table 7 9 Additional Libraries for using RTI Secure WAN Transport APIs on OS X Systems Select the files appropriate for your chosen library format Table 7 9 Additional Libraries for using RTI Secure WAN Transport APIs on OS X Systems Library Format RTI Secure WAN Transport Libraries OpenSSL Libraries libnddstransportwan dylib libnddstransporttls dylib libnddstransportwand dylib libnddstransporttlsd dylib libssLso libcrypto so Static Rel libnddstransporttlsz a pee libnddstransporttlszd a libnddstransportwanz a libnddstransportwanzd a Dynamic Debug Static Debug 7 10 Libraries Required for Using RTI TCP Transport APIs To use the TCP Transport APIs link against the additional libraries in Table 7 10 Additional Libraries for using RTI TCP Transport APIs on OS X Systems If you are using RTI TLS Support see Table 7 11 Additional Libraries for using RTI TCP Transport APIs on OS X Systems with TLS Enabled Select the files appropriate for your chosen library format Table 7 10 Additional Libraries for using RTI TCP Transport APIs on OS X Systems Library Format RTI TCP Transport Libraries Dynamic Debug libnddstransporttcpd so Static Debug libnddstransporttcpzd a The libraries are in lt NDDSHOME gt 7 lib lt architecture gt PThese libraries are in
63. Red Hat Enterprise Linux 4 0 target 39 Table 5 2 Linux Platforms on Intel CPUs Operating System Red Hat Enterprise Linux 5 1 5 2 5 4 5 5 2 6 kernel Red Hat Enterprise Linux 5 2 with Real Time Extensions 2 6 kernel Red Hat Enterprise Linux 6 0 6 5 2 6 kernel Red Hat Enterprise Linux7 0 3 x kernel SUSE Linux Enterprise Server 11 SP2 3 x kernel SUSE Linux Enterprise Server 11 SP2 SP3 2 6 kernel Chapter 5 Linux Platforms RTI Architecture ee i86Linux2 6gcc4 1 2 x64Linux2 6gcc4 1 2 i86Linux2 6gcc4 1 2 i86Linux2 6gcc4 4 5 x64Linux2 6gcec4 4 5 186Linux3 gcc4 8 2 x64Linux3gcc4 8 2 i86Linux3gcc4 3 4 x64Linux2 6gcc4 3 4 40 Chapter 5 Linux Platforms Table 5 2 Linux Platforms on Intel CPUs Compiler RTI Architecture E ee ava Platform Standard Edition JDK 1 7 or Ubuntu Server 12 04 LTS gcc 4 6 3 Operating System 186Linux3 xgcc4 4 3 x64Linux3 xgcc4 6 3 ava Platform Standard Edition JDK 1 7 or gcc 4 8 2 e 186Linux3gcc4 8 2 ava Platform Standard Edition JDK 1 7 or Ubuntu 14 gcc 4 8 2 Java Platform Standard Edition JDK 1 7 or 1 8 x64Linux3gcc4 8 2 Wind River Linux 4 2 6 kernel gcc 4 4 1 x64WRLinux2 6gcc4 4 1 Table 5 3 Linux Platforms on PowerPC CPUs Operating System cu compr RTI Architecture Abbreviation Freescale P2020RDB Freescale gcc 4 3 74 based on 2 6 32 kernel 80c 4 3 2 ppc85xxLinux2 6gcc4 3 2 Wind River Linu
64. Redistributable Package Requirement You must have Visual C Redistributable for Visual Studio 2013 installed on the machine where you are running an application linked with dynamic libraries This includes C C dynamically linked and all NET and Java applications You can download Visual C Redistributable for Visual Studio 2013 from this Microsoft website http www microsoft com en us download details aspx 1d 40784 139 11 2 Windows Registry Setting for Better Performance 11 2 Windows Registry Setting for Better Performance On all Windows systems prior to Windows Vista the following registry setting change will improve per formance when sending UDP datagrams of size larger than 1024 bytes Under HKEY LOCAL MACHINE SYSTEM CurrentControlSet Services AFD Parameters add the following DWORD Name FastSendDatagramThreshold Value 65536 This will improve the Connext DDS performance for data sizes larger than 1024 bytes RTPS overhead included It allows the datagrams to bypass the I O subsystem by using a blocking send call instead of a buffer copy in the Windows Network stack 11 3 Use Dynamic MFC Library Not Static To avoid communication problems in your Connext DDS application use the dynamic MFC library not the static version If you use the static version your Connext DDS application may stop receiving DDS samples once the Windows sockets are initialized 11 4 NET API Requires Thread Affinity To maintain
65. Starting with 4 5e support for the TimesTen database has been removed To use MySQL you also need the MySQL ODBC 5 1 6 or higher driver The Durable Writer History and Durable Reader State features have been tested with the following archi tectures e 186Win32VS2008 e 186Win32VS2010 e x64Win64V S2008 e x64Win64VS2010 For more information on database setup please see the RTI Connext DDS Core Libraries Getting Started Guide Addendum for Database Setup 11 6 PPP Link Support for Windows XP Systems To use a Windows XP point to point protocol PPP link such as a serial cable the UDP transport prop erties for the Connext DDS applications running on the PPP server machine must be configured with mul ticast disabled for the PPP server interface s To disable multicast for an interface change the UDPv4 transport properties as follows Disable multicast for PPP interface because it causes problems char bad interfaces 192 168 250 100 interface addr comes lme mon becl inrerteces sizeof bad interfaces sizeof bad interfaces 0 UDIE WA propert iess perent Ceny malecicast Tncertaces ligt bac Interteces UNE ropert Ss erent Ceny anule as MAI efe e list lengtn num bad interfaces Failure to do so will result in Connext DDS being unable to send any data at all over the PPP link 141 11 7 Support for Modern C API Notes e Setting up multicast related socket options for the PPP interfa
66. Static Release libnddscorez a librticonnextmsgez a sparc64SoD 10gcc3 4 2 libnddsczd a sparc64SoD 10gcc3 4 2 Static Debug libnddscorezd a A oe eee DRTI UNIX m64 ie Ipthread Im lc librticonnextmsgezd a libnddsc so All other architectures All other architectures libnddscore so librticonnextmsgc so ldl Insl lgenIO lsocket Igen lposix4 DRTL UNIX m32 Ipthread Im lc libnddscd so libnddscored so librticonnextmsged so AChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API PThe RTI C C Java libraries are in NDDSHOME libKarchitecture gt The jar files are in NDDSHOMFE lb java The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 86 Chapter 9 Solaris Platforms Table 9 2 Building Instructions for Solaris Architectures Static Debug Dynamic Release C Traditional and Modern APIs Dynamic Debug RTI Libraries or Jar Files libnddscppz a or libnddscpp2z a libnddscz a libnddscorez a librticonnextmsgcppz a libnddscppzd a or libnddscpp2zd a libnddsczd a libnddscorezd a librticonnextmsgcppzd a libnddscpp so or libnddscpp2 so libnddsc so libnddscore so librticonnextmsgcpp so libnddscppd so or libnddscpp2d so libnddscd so libnddscored so librticonnextmsgcppd so nddsjava jar rticonnextm
67. T DCPU AMD64 DTARGET x64Linux2 6gcc4 4 5 DNDEBUG Wp MD x64Linux2 6gcc4 4 5 gcc m64 fPIC DLINUX g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 4 5 Wp MD The C libnddscpp dynamic libraries were linked using g the C dynamic libraries i e libnddscore and libnddsc were linked using gcc 46 5 1 Support for Modern C API Table 5 6 Library Creation Details for Linux Architectures Library Format RTI Architecture Compiler Flags Used by RTI Static amp Dynamic m64 fPIC DLINUX DRTI LINUX26 DRTI LINUX DRTI POSIX THREADS DRTI POSIX SEMAPHORES DRTI CPU AFFINITY O Wall Wno unknown Release pragmas DPtrIntType long DCSREAL IS FLOAT DCPU i686 DRTI ENDIAN _ LITTLE DRTI THREADS DRTI MULTICAST DRTI SHARED MEMORY DRTI IPV6 DTARGET x64Linux3 gec4 8 2 DNDEBUG c Wp MD x64Linux3 gcc4 8 2 g m64 fPIC DLINUX DRTL LINUX26 DRTI_LINUX DRTI_POSIX_THREADS DRTI_POSIX_SEMAPHORES DRTI_CPU_AFFINITY O Wall Wno unknown Debug pragmas DPtrIntType long DCSREAL IS FLOAT DCPU i686 DRTI_ENDIAN _ LITTLE DRTI THREADS DRTL MULTICAST DRTI SHARED MEMORY DRTI_ IPV6 DTARGET x64Linux3 gec4 8 2 DDEBUG c Wp MD Release m64 march x86 64 mtune generic fPIC DLINUX O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DNDEBUG x64WRLinux2 6gcc4 4 1 Debug m64 march x86 64 mtune generic fPIC
68. THREAD SETTINGS STDIO DDS THREAD maS SETTINGS FLOATING POINT mas t DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT AMAS OS default thread stack size CPU core affinity not supported cpu_rotation CPU core affinity not supported Table 7 6 Thread Priority Definitions for OS X Platforms Thread Priority Definition Operating System Priority THREAD PRIORITY DEFAULT 9999999 THREAD PRIORITY_HIGH 9999999 THREAD PRIORITY ABOVE NORMAL 9999999 THREAD PRIORITY NORMAL 9999999 THREAD PRIORITY BELOW NORMAL 9999999 THREAD PRIORITY LOW 9999999 7 6 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on OS X platforms 71 7 7 Libraries Required for Using Distributed Logger 7 7 Libraries Required for Using Distributed Logger RTI Distributed Logger is supported on OS X platforms Table 7 7 Additional Libraries for using RTI Dis tributed Logger lists the additional libraries you will need in order to use Distributed Logger Table 7 7 Additional Libraries for using RTI Distributed Logger Language CH librtidlcz a librtidlezd a librtidlc dylib librtidlcd dylib Traditional ERN A a pum a pn dylib porum dylib co wea a ibrida a librtidlc m librtidlcd mam distlog jar distlogd jar distlogdatamodel jar distlogdatamodeld jar 7 8 Libraries Required for Using Monitoring Make sure you are consistent in your use of sta
69. Thread Setting for VxWorks Platforms Applies to Kernel Tasks or Real Time Process Threads DDS a Applicable Thread ThreadSettings t Platform Specific Setting Asynchronous Publisher thread ima __ rotation CPU core affinity not supported CPU core affinity not supported DDS THREAD SETTINGS STDIO r I Database thread CPU core m ia Rca cl NN not supported 116 10 10 1 Support for Controlling CPU Core Affinity for RTI Threads Table 10 6 Thread Setting for VxWorks Platforms Applies to Kernel Tasks or Real Time Process Threads DDS ThreadSettings t DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS S FLOATING POINT Event thread Applicable Thread Platform Specific Setting CPU core affinity not supported CPU core affinity not supported DDS THREAD SETTINGS STDIO DDS_ THREAD SETTINGS FLOATING POINT i l th CPU core affinity not supported cpu_rotation CPU core affinity not supported Table 10 7 Thread Priority Definitions for VxWorks Platforms eee Definition RE a oo od Priority THREAD PRIORITY DEFAULT THREAD PRIORITY HIGH mask THREAD PRIORITY NORMAL THREAD PRIORITY BELOW NORMAL THREAD PRIORITY LOW 117 10 11 Durable Writer History and Durable Reader State Features Table 10 8 Thread Kinds for VxWorks Platforms Thread Kinds Operating System Configuration DDS THREAD SETTINGS FLOATING POINT Uses VX_FP_TASK when calling taskSpawn DDS_THREAD_SETTINGS_STDIO Uses VX_STDIO when c
70. WORKS DTOOL_FAMILY gnu DPtrIntType long DCPU PENTIUM c Wp MD march pentium fno builtin ansi DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 7 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM DNDEBUG c Wp MD Static or Dynamic Release pentiumVx6 7gcc4 1 2 march pentium fno builtin ansi DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 7 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM c Wp MD Static or Dynamic Debug 104 Chapter 10 VxWorks Platforms Table 10 4 Library Creation Details for All VxWorks Architectures Library Format RTI Architecture Compiler Flags Used by RTI march i486 ansi DTOOL gnu mrtp D_PROTOTYPE 5 0 DVXWORKS MAJOR Static VERSION 6 DVXWORKS_MINOR_VERSION 7 O Wall Wno unknown pragmas Release DRTS_VXWORKS DTOOL_FAMILY gnu DPtrIntType long DCPU PENTIUM DNDEBUG c Wp MD march i486 ansi DTOOL gnu mrtp D_PROTOTYPE 5 0 g DVXWORKS MAJOR_ Static VERSION 6 DVXWORKS_MINOR_VERSION 7 O Wall Wno unknown pragmas Debug DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM c Wp MD pentiumVx6 7gcc4 1 2 rtp march i486 ansi DTOOL gnu mrtp D PROTOTYPE 5 0 fPIC DVXWORKS _ Dynamic MAJOR VERSION 6 DVXWORKS MINOR VERSION 7 O Wall Release Wno unknown pragmas DRTS VXWORKS
71. ags Used by RTI W3 DPtrIntType long DCSREAL IS_FLOAT DCPU AMD64 DTARGET x64Win64V S2008 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V 2008 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi IMD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V 2008 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MTd EHsc RTC1 D CRT SECURE NO DEPRECATE c W3 DPtrintType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V 82008 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V S2010 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V 2010 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi IMD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Win64V S2010 DWIN32 D WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MTd EHsc RTC1 D CRT SECURE NO DEPRECATE c W3 DPtrIntType long
72. ake sure you are consistent in your use of static dynamic debug and release versions of the libraries For example if your Connext DDS application is linked with the static release version of the Connext DDS libraries you will need to also use the static release version of the monitoring library Do not link both static and dynamic libraries Similarly do not mix release and debug libraries If you are statically linking your application with DDS libraries and you want to add monitoring to your application you will also need to statically link the monitoring library The library cannot be loaded dynam ically strictly through the QoS profile because it also depends on DDS to publish its data Therefore it depends on DDS the DDS functionality would cause duplicate symbols to be found resulting in the ter mination of the process Note If you plan to use static libraries the RTI library from Table 3 7 Additional Libraries for Using Mon itoring must appear first in the list of libraries to be linked Table 3 7 Additional Libraries for Using Monitoring Static Debug Dynamic Release Dynamic Debug librtimonitoringz a librtimonitoringzd a librtimonitoring so librtimonitoringd so 22 3 9 Libraries Required for Using RTI TCP Transport APIs 3 9 Libraries Required for Using RTI TCP Transport APIs To use the TCP Transport APIs link against the additional libraries in Table 3 8 Additional Libraries for using RTI TCP Transport APIs on Andro
73. alization of static objects and to ensure that the C run time support calls the correct con structor destructors in the correct order for all static objects If you need to use the C Request Reply API for kernel mode with dynamically linked libraries you need to munch your application and link or load the Connext DDS library for C request reply in addi tion to the standard Connext DDS libraries for core C and C RTI provides pre munched Connext DDS dynamic libraries for C Request Reply with the extension lo For example if you plan to load your application at run time for kernel mode and your application uses the Request Reply API for C with dynamic libraries assuming you want to use non debug lib raries you need to first load the libnddscore so library then libnddsc so then libnddscpp so and finally librticonnextmsgcpp lo Once all these libraries are loaded you can load your munched C application The following table shows the libraries for which RTI has performed the munching process 112 10 3 Increasing the Stack Size Table 10 5 Pre Munched Kernel mode C Request Reply Dynamic Libraries librticonnextmsgcpp lo Munched Release C Request Reply library librticonnextmsgcppd lo Munched Debug C Request Reply library 10 3 Increasing the Stack Size Connext DDS applications may require more than the default stack size on VxWorks To prevent stack overrun you can create enable the DomainParticipant in
74. alling taskSpawn Kernel mode only DDS THREAD SETTINGS REALTIME PRIORITY Configures the schedule policy to SCHED FIFO DDS THREAD SETTINGS PRIORITY ENFORCE N A 10 11 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on VxWorks platforms 10 12 Libraries Required for Using Distributed Logger RTI Distributed Logger is only supported on these VxWorks architectures e VxWorks 6 7 e ppc604Vx6 7gcc4 1 2 e ppc604Vx6 7gcc4 1 2 rtp e VxWorks 6 8 e ppc604Vx6 8gcc4 1 2 e ppc604Vx6 8gcc4 1 2 rtp e VxWorks 6 9 4 e ppce500v2V x6 9 4gcc4 3 3 e ppce500v2Vx6 9 4gcc4 3 3 rtp e Works 7 0 e pentiumVx7 0gcc4 3 3 e pentiumVx7 0gcc4 3 3 rtp Table 10 9 Additional Libraries for using RTI Distributed Logger lists the additional libraries you will need in order to use Distributed Logger See VxWorks manuals for additional information 118 10 13 Libraries Required for Using Monitoring Table 10 9 Additional Libraries for using RTI Distributed Logger Language librtidlez a librtidlezd a librtidlc so librtidcd so C librtidlcz a librtidlezd a librtidlc so librtidlcd so Traditional API librtidlcppz a librtidlcppzd a librtidlcpp so librtidlcppd so 10 13 Libraries Required for Using Monitoring Make sure you are consistent in your use of static dynamic debug and release versions of the libraries For example if your Connext DDS appli
75. arch Evaluation and Basic packages include support for the Request Reply Communication Pattern for all platforms in Table 4 1 Supported INTEGRITY Target Plat forms and all programming languages except as noted below When using C the following platform does not support the Request Reply Communication Pattern e ppc85xxInty5 0 11 xes p2020 The dba files contain the debugging information You can link without these as long as they are located in the same directory as the matching d a file so that the MULTI IDE can find the debug information 32 4 11 Diagnostics on INTEGRITY Systems 4 11 Diagnostics on INTEGRITY Systems Connext DDS libraries for the INTEGRITY platforms use consolestring which prints debugging information to the serial console when available Using the serial console as opposed to the target I O win dow host I O is generally recommended Host I O will affect the real time performance of the target For more information on consolestring please refer to the INTEGRITY Development Guide 4 12 Running over IP Backplane on a Dy4 Champ AVII Board Connext DDS can run on all four CPUs provided the following hold true e Connext DDS applications on CPUs B C and D only exchange data with applications on a dif ferent CPU or off board e The IP backplane and associated routing has been properly configured Connext DDS has been tested with the following libraries built into the INTEGRITY kernel debug res
76. aries Similarly do not mix release and debug lib raries Table 8 3 Running Instructions for QNX Architectures provides details on the environment vari ables that must be set at run time for a QNX architecture For use with Windows Linux or Solaris Host as supported by QNX amp RTI 75 Chapter 8 QNX Platforms Table 8 4 Library Creation Details for QNX Architectures provides details on how the QNX libraries were built Table 8 2 Building Instructions for QNX Architectures Required Required abc Library Format RTI Libraries Systeme beanies ompilen Brags libnddscppz a or libnddscpp2z a Static Release libnddscz a libnddscorez a librticonnextmsgcppz a libnddscppzd a or libnddscpp2zd a Static Debug libnddsczd a libnddscorezd a TM librticonnextmsgcppzd a Traditional and Modern APIs Im lsocket DRTI QNX libnddscpp so or libnddscpp2 so Dynamic Release libnddsc so libnddscore so librticonnextms gcpp so libnddscppd so or libnddscpp2d so Dynamic Debug libnddscd so libnddscored so librticonnextms gcppd so AChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API bThe DDS C C libraries are in SINDDSHOME Vlib lt architecture gt The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 76 Chapter 8 QNX Platforms Tabl
77. aries Required for Using Distributed Logger RTI Distributed Logger is supported on QNX platforms on x86 CPUs It is not supported on QNX plat forms on ARM CPUs Table 8 7 Additional Libraries for using RTI Distributed Logger lists the additional libraries you will need in order to use Distributed Logger Table 8 7 Additional Libraries for using RTI Distributed Logger ASS Language librtidlcz a librtidlczd a librtidlc so librtidcd so C librtidlcz a librtidlezd a librtidlc so librtidlcd so Traditional API librtidlcppz a librtidlcppzd a librtidlcpp so librtidlcppd so 8 9 Libraries Required for Using Monitoring Make sure you are consistent in your use of static dynamic debug and release versions of the libraries For example if your Connext DDS application is linked with the static release version of the Connext DDS libraries you will need to also use the static release version of the monitoring library Do not link both static and dynamic libraries Similarly do not mix release and debug libraries If you are statically linking your application with DDS libraries and you want to add monitoring to your application you will also need to statically link the monitoring library The library cannot be loaded dynam ically strictly through the QoS profile because it also depends on DDS to publish its data Therefore it depends on DDS the DDS functionality would cause duplicate symbols to be found resulting in the ter mination of the
78. as DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM DNDEBUG c Wp MD Static or Dynamic Release pentiumVx6 6gcc4 1 2 march pentium fno builtin ansi DTOOL gnu D_WRS_KERNEL D_PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM c Wp MD Static or Dynamic Debug 103 Chapter 10 VxWorks Platforms Table 10 4 Library Creation Details for All VxWorks Architectures Library Format RTI Architecture Compiler Flags Used by RTI march i486 ansi DTOOL gnu mrtp D_PROTOTYPE 5 0 DVXWORKS MAJOR Static VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas Release DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM DNDEBUG c Wp MD march i486 ansi DTOOL gnu mrtp D_PROTOTYPE 5 0 g DVXWORKS MAJOR_ Static VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas Debug DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM c Wp MD pentiumVx6 6gcc4 1 2_rtp march i486 ansi DTOOL gnu mrtp D PROTOTYPE_5_0 fPIC DVXWORKS _ Dynamic MAJOR_VERSION 6 DVXWORKS_MINOR_VERSION 6 O Wall Wno unknown Release pragmas DRTS_VXWORKS DTOOL_FAMILY gnu DPtrIntType long DCPU PENTIUM DNDEBUG c Wp MD march i486 ansi DTOOL gnu mrtp D PROTOTYPE 5 0 fPIC g DVXWORKS _ MAJOR_VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas DRTS_VX
79. ase 3 3 Supported Transports 3 3 Supported Transports Shared memory Not supported for this release For a consumer device shared memory communication between Apps is often not desirable UDPv4 Supported and enabled by default UDPv6 Not supported The IPv6 stack implementation has been evolving in parallel with the Android OS For many of the supported Android versions there is either no or insufficient IPv6 support TCP IPv4 Supported 3 4 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is supported on all Android platforms 3 5 Thread Configuration Table 3 5 Thread Settings for Android Platforms lists the thread settings for Android platforms Table 3 6 Thread Priority Definitions for Android Platforms lists the thread priority definitions for Android platforms Table 3 5 Thread Settings for Android Platforms DDS Applicable Threads ThreadSettings _ Platform Specific Setting t ask OS default thread type priority OS default thread priority Asynchronous Publisher Asynchronous stie eio OS default stack size flushing thread cpu_list CPU core affinity not supported cpu_rotation 20 3 5 Thread Configuration Table 3 5 Thread Settings for Android Platforms DDS_ Applicable Threads ThreadSettings_ Platform Specific Setting t mask DDS THREAD SETTINGS STDIO priority OS default thread priority Database thread stack size OS default stack size cpu list
80. avior would be to receive messages only for the addresses to which the current pro cess not the host is subscribed 6 3 Supported Transports Shared memory Supported and enabled by default UDPv4 Supported and enabled by default UDPv6 Not supported TCP IPv4 Not supported 6 3 1 Shared Memory Support To see a list of shared memory resources in use use the ipes command To clean up shared memory and shared semaphore resources use the iperm command The shared memory keys used by Connext DDS are in the range of 0x400000 For example ipcs m grep 0x004 The shared semaphore keys used by Connext DDS are in the range of 0x800000 the shared mutex keys are in the range of 0xb00000 For example ipcs s grep 0x008 ipcs s grep 0x00b Please refer to the shared memory transport online documentation for details on the shared memory and semaphore keys used by Connext DDS 6 4 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is not supported on LynxOS platforms 6 5 Thread Configuration Table 6 6 Thread Settings for LynxOS Platforms lists the thread settings for LynxOS platforms Table 6 7 Thread Priority Definitions for LynxOS Platforms lists the thread priority definitions 61 6 5 1 Support for Controlling CPU Core Affinity for RTI Threads 6 5 1 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described
81. braries and JAR Filesabe Library Format Required System iba Required Compiler Flags libnddscz a libnddscorez a librticonnextmsgcz a libnddsczd a libnddscorezd a librti tm ci gezdi L SYSROOT usr lib march armv7 a mfloat abi softfp mfpu vfpv3 llog Im lc d16 mlong calls DRTI_UNIX DRTI ANDROID libnddsc so libnddscore so librticonnextmsgc so libnddscd so libnddscored so librticonnextmsgcd so Dynamic Debug When not building Apps apk nddsjava jar rticonnextmsg jar Release When building Apps apk nddsjava jar libnddsjava so libnddsc so libnddscore so rticonnextmsg jar When not building Apps apk nddsjavad jar rticonnextmsgd jar None required When building Apps apk nddsjavad jar libnddsjavad so libnddscd so libnddscored so rticonnextmsgd jar AChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API gt The RTI C C Java libraries are in NDDSHOME llibKarchitecture gt The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 18 3 1 Support for Modern C API Table 3 3 Running Instructions for Android Architectures RTI Architecture Library Format Required Environment Variables LD LIBRARY PATH SLD LIBRARY PATH lt path to ndds libs gt App apk army 7aAndroid2 3gcc4 8 for Java
82. bug libnddstlszd a libssl so OpenSSL Libraries libcrypto so AThese libraries are in lt NDDSHOME gt libKarchitecture gt 55 Chapter 6 LynxOS Platforms Table 6 1 Supported LynxOS Platforms lists the architectures supported on LynxOS operating systems Table 6 1 Supported LynxOS Platforms LynxOS 4 0 PPC 74xx such as 7410 gcc 3 2 2 ppc7400Lynx4 0 0gcc3 2 2 PPC 604 PPC 7XX such as 750 gcc 3 2 2 ppc750Lynx4 0 0gcc3 2 2 LynxOS 4 2 PPC 74xx such as 7410 gcc 3 2 2 ppc7400Lynx4 2 0gcc3 2 2 LynxOS 5 0 PPC 74xx such as 7410 gce 3 4 3 ppc7400Lynx5 0 0gcc3 4 3 Table 6 2 Building Instructions for LynxOS Architectures and Table 6 3 Building Instructions for LynxOS Architectures list the compiler flags and libraries you will need to link into your applic ation See also e Libraries Required for Using Monitoring Section 6 8 on page 63 Make sure you are consistent in your use of static dynamic debug and release versions of the lib raries Do not link both static and dynamic libraries Similarly do not mix release and debug lib raries Table 6 4 Running Instructions for LynxOS Architectures provides details on the environment vari ables that must be set at run time for a LynxOS architecture 56 Chapter 6 LynxOS Platforms Table 6 5 Library Creation Details for LynxOS Architectures provides details on how the libraries were built by RTI This table is provided strictly for informational purposes you do no
83. cation is linked with the static release version of the Connext DDS libraries you will need to also use the static release version of the monitoring library Do not link both static and dynamic libraries Similarly do not mix release and debug libraries If you are statically linking your application with DDS libraries and you want to add monitoring to your application you will also need to statically link the monitoring library The library cannot be loaded dynam ically strictly through the QoS profile because it also depends on DDS to publish its data Therefore it depends on DDS the DDS functionality would cause duplicate symbols to be found resulting in the ter mination of the process Note If you plan to use static libraries the RTI library from Table 10 10 Additional Libraries for Using Monitoring must appear first in the list of libraries to be linked Table 10 10 Additional Libraries for Using Monitoring Static Debug Dynamic Release Dynamic Debug librtimonitoringz a librtimonitoringzd a librtimonitoring so librtimonitoringd so 10 14 Increasing the Receive Socket Buffer Size For Connext DDS applications running on VxWorks 6 7 or higher systems and using UDPv4 we recom mend setting the property dds transport UDPv4 builtin recv_socket_buffer_size to a value of 128000 or higher This recommendation is due to Wind River s usage of extra receive socket buffer space to cor rect Wind River defect number WIND00135312 Dyna
84. ce can prevent future unicast sends using that socket from working e Connext DDS sets up certain sockets for multicast even if it has no multicast peers in case some show up later You avoid this by configuring the multicast deny list as described above 11 7 Support for Modern C API Connext DDS provides two different C APIs which we refer to as the Traditional C and Modern C APIs The Modern C API is available for all Windows platforms For more information on Modern C see Traditional vs Modern C in the User s Manual 11 8 Multicast Support Multicast is supported on all platforms and is configured out of the box That is the default value for the initial peers list NDDS_DISCOVERY_PEERS includes a multicast address See the online doc umentation for more information 11 9 Supported Transports Shared memory Shared memory is supported and enabled by default The Windows operating system manages the shared memory resources automatically Cleanup is not required UDPv4 Supported and enabled by default UDPv6 Supported but disabled on architectures that use Visual Studio The peers list NDDS _ DISCOVERY_PEERS must be modified to support UDPv6 No Traffic Class support TCP IPv4 Supported on architectures that use Visual Studio This is not a built in transport 11 10 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is supported on all Windows platforms
85. clude ndds dds c dds c infrastructure h line 945 warning unrecognized pragma pragma warning pop These warnings do not compromise the final application produced and can be safely ignored 4 16 4 Warning when Loading Connext DDS Applications on INTEGRITY Systems When a Connext DDS application compiled with the rtiddsgen generated project files is loaded on an INTEGRITY 5 0 x target the following warning appears 36 4 16 4 Warning when Loading Connext DDS Applications on INTEGRITY Systems Mierzmilmes Brescia as Iamkecl wide lise exo POSIX Sigmals and cancellation will not work The Connext DDS libraries do not use the additional features provided by the full POSIX implementation therefore the warning can safely be ignored This warning is due to the fact that the rtiddsgen generated project files use the Single AddressSpace POSIX library by default not the full POSIX implementation on INTEGRITY POSIX System The Connext DDS libraries only require Single AddressSpace POSIX to function correctly but will still work if you are using the POSIX System The message indicates that items such as inter process signaling or process shared semaphores will not be available more information can be found in the INTEGRITY Libraries and Utilities User s Guide chapter Introduction to POSIX on INTEGRITY 37 Chapter 5 Linux Platforms First see the basic instructions for compiling on Linux platforms provided in Building App
86. correctly For more information see the VxWorks Programmer s Guide 99 Chapter 10 VxWorks Platforms Table 10 2 Building Instructions for VxWorks 5 x 7 x Architectures Required Compiler Flags Library Format Required Kernel Components Required RTI Libraries libnddscppz a or Static libnddscpp2z a Release libnddscz a libnddscorez a librticonnextmsgcppz a libnddscppzd a or libnddscpp2zd a INCLUDE_TIMESTAMP libnddsczd a libnddscorezd a For VxWorks 6 4 and below also use DRTI_ librticonnextmsgcppzd a INCLUDE ZBUF SOCK VXWORKS C Traditional INCLUDE_IGMP and Modern APIs libnddscpp2 so for RTP mode libnddscpp2 lo for kernel mode not supported for VxWorks 5 x For VxWorks 6 3 and higher also use INCLUDE POSIX CLOCKS Dynamic librticonnextmsgcpp so for RTP mode Release librticonnextmsgcpp lo for kernel mode f not supported for VxWorks 5 x For RTI architectures with SMP support for VxWorks 6 7 and higherd also use libnddsc so INCLUDE TLS libnddscore so i libnddscpp so libnddscpp2d so for RTP mode libnddscpp2d lo for kernel mode not supported for VxWorks 5 x Dynamic librticonnextmsgcppd so for RTP mode Debug librticonnextmsgcppd lo for kernel mode not supported for VxWorks 5 x libnddscd so libnddscored so libnddscppd so AChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API gt The Connext DDS C C libra
87. d Change for Building with C Libraries for QNX Platforms Table 8 4 Library Creation Details for QNX Architectures Library Format RTI Architecture Compiler Flags Used by RTI Static amp Dynamic qec Vgcc 4 4 2 gcc_ntoarmv7le_cpp fPIC fexceptions DFD_SETSIZE 512 O Wall Wno Release unknown pragmas DRTS_QNX DPtrIntType long DCSREAL IS FLOAT DCPU ARMV7 DTARGET NX6 5 0SP1 4 4 2 DNDEB amv7aQNX6 5 0SP1qcc 7 GET armv7aQN X6 5 0SP1qcc cpp UG cpp4 4 2 ER qec Vgcc 4 4 2 gcc_ntoarmv7le_cpp fPIC fexceptions DFD_SETSIZE 512 g Wall Wno Debug unknown pragmas DRTS_QNX DPtrIntType long DCSREAL IS FLOAT DCPU ARMV7 DTARGET armv7aQNX6 5 0SP1qcc cpp4 4 2V qee Vgec 4 3 3 gcc_ntox86 Y gpp lang c fPIC fexceptions O Wall Wno unknown Release pragmas i860NX6 4 1qcc gpp DNDEBUG Debu qec Vgcc 4 3 3 gcc ntox86 Y_gpp lang c fPIC fexceptions g Wall Wno unknown 8 pragmas qec Vgcc 4 4 2 gcc_ntox86 Y_gpp m32 march i386 mtune generic fPIC fexceptions Release DFD_SETSIZE 512 O Wall Wno unknown pragmas DRTS_QNX DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86QNX6 5qce_gpp4 4 2 DNDEBUG 1860NX6 5qcc gpp4 4 2 qec Vgcc 4 4 2 gcc ntox86 Y gpp m32 march i386 mtune generic fPIC fexceptions DFD SETSIZE 512 g Wall Wno unknown pragmas DRTS QNX DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86QNX6 5qcc_gpp4 4 2 8 1 Required Change for Building with
88. d higher architectures except as noted below No Traffic Class support TCP IPv4 Not supported 10 8 1 Shared Memory Communication between Applications Running in Kernel Mode and RTP Requires Explicitly Set Participant ID By default applications using the auto generated Participant ID 1 cannot communicate between user space and kernel space on the same host via SHMEM The root cause is that the participants use the same participant ID Therefore the workaround for this issue is to explicitly provide a participant ID when cre ating the DomainParticipants The participant ID is set in the DomainParticipant s WireProtocol QoS policy 10 8 2 How To Run Connext DDS Libraries in Kernels Built without Shared Memory Since Connext DDS libraries support shared memory as a built in transport building a kernel without shared memory support will cause loading or linking errors depending on whether the Connext DDS lib raries are loaded after boot or linked at kernel build time The most straightforward way to fix these errors is to include shared memory support in the kernel INCLUDE SHARED DATA in the kernel build parameters However in some versions of VxWorks it is not possible to include shared memory support without also including RTP support If you are unwilling or unable to include shared memory support in your con figuration you will need to do the following 1 Add the component INCLUDE POSIX SEM 2 Define stubs that return
89. ddscpp lib nddsc lib nddscore lib rticonnextmsgcpp lib nddscppd lib nddscd lib nddscored lib rticonnextms gcppd lib Required System Libraries netapi32 lib advapi32 lib user32 lib ws2 32 lib netapi32 lib advapi32 lib user32 lib ws2 32 lib Required Compiler Flags Gd MT D WIN32 D RTI WIN32 D NDEBUG Gd MTd D WIN32 D RTI_WIN32 Gd MD D WIN32 D NDDS DLL _ VARIABLE D RTI WIN32 D NDEBUG Gd MDd D WIN32 D NDDS DLL _ VARIABLE D RTI WIN32 Gd EHsc MT D WIN32 D RTI_WIN32 D NDEBUG Gd EHsc MTd D WIN32 D RTI WIN32 Gd EHsc MD D WIN32 D NDDS DLL _ VARIABLE D RTI WIN32 D NDEBUG Gd EHsc MDd D WIN32 D NDDS DLL _ VARIABLE D RTI WIN32 The RTI C C Java libraries are in NDDSHOME Vib architecture Jar files are in lt NDDSHOME gt lib java gt The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 132 Chapter 11 Windows Platforms Table 11 3 Building Instructions for Windows Target Architectures API Library RTI Libraries or Jar Required System Required Compiler Format Files Libraries Flags nddsdotnet dll or nddsdotnet lt version gt dll Release rticonnextdotnet dll or rticonnextdotnet lt version gt dll nd
90. dhcdoseasnccesxaanest 70 To Thread CONSULTA LON 522 entre cto A A oo Azmi Saye ee ttum RE RUM ud 70 7 5 1 Support for Controlling CPU Core Affinity for RTI Threads cessere nnns 70 7 6 Durable Writer History and Durable Reader State Features ooocccccccccccccccccccccncccccccccccnnnncccccccoo 71 7 7 Libraries Required for Using Distributed Logger ooooccccccccccccccccccccccccccccnnnnnnnnnn eee eee 72 7 8 Libraries Required for Using Monitoring ooo eee 72 7 9 Libraries Required for Using RTI Secure WAN Transport APIs oooccccccccccccccccccccccccccnccncccccccccoo 72 7 10 Libraries Required for Using RTI TCP Transport APIs _ 2 222000 73 Chapter 8 QNX Platforms 8 1 Required Change for Building with C Libraries for QNX Platforms 2 2 2 2 cece eee eee cece ee eeee 78 8 2 Support for Modem C EE APL uas iem dite nt cuc merced A dade Pu pec Yr aque 79 8 3 Multicast SUPDOT Lt EA RS TA a A Aa A 79 SASS Pported Transports noo A e ir kr Y tt aia 79 8 5 Monotonic Clock SUPpoTrt Visitadas ta cm i A GA DIR Gc Prec XE V a die its 80 S i6 Thread Confisuratio n oss V eed ads oP EM Ie I A ferre v e ee teen Pace IE 80 8 6 1 Support for Controlling CPU Core Affinity for RTI Threads oooocccccccccccccccccccccccccccccccccoco 80 8 7 Durable Writer History and Durable Reader State Features ooooccccccccccccccccccccncccccccccccnnnncccccccoo 81 8 8 Libraries Required for Using Distributed Logger ssssssse
91. dsdotnetd dll or nddsdotnet lt version gt d dll Debug rticonnextdotnetd dll or rticonnextdotnet lt version gt d dll Gd EHsc MD D WIN32 nddscpp lib D NDDS DLL Release nddsc lib VARIABLE nddscore lib netapi32 lib RTI_WIN32 132 11 D NDEBUG CHICLI advapi32 lib user32 lib ws2_32 lib Gd EH sc MDd D WIN32 D NDDS DLL VARIABLE D RTI_WIN32 nddscppd lib Debug nddscd lib nddscored lib Release rticonnextmsg Jar N A nddsjavad jar rticonnextms gd jar Table 11 4 Running Instructions for Windows Architectures RTI Architecture Library Format Environment Variables All supported Windows architectures for Java Path NDDSHOME lib lt architecture gt Path e GsY Y XX nm The RTI C C Java libraries are in NDDSHOME Vib architecture Jar files are in lt NDDSHOME gt lib java gt The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type C Path represents the value of the Path variable prior to changing it to support Connext DDS When using nddsjava jar the Java virtual machine JVM will attempt to load release versions of the native libraries When using nddsjavad jar the JVM will attempt t
92. e 112 10 2 Request Reply Communication Pattern 2 2 2 cece cece eee cece ese cece cence cececeeeeeeeeeeeseenees 112 10 3 Increasing the Stack Size 55cm uu 113 10 4 Libraries for RTP Mode on VxWorks 6 3 and Higher Systems oooocccccccccccccccccccccccccccccccccccccccos 113 10 5 Requirement for Restarting Applications ooocccccccccccccccccccococonn cnn cnn sse cece cece cece rere ni 113 10 6 Support for Modern C API ooo s sss sl sse esee eee esses ll 114 10 7 Multicast Support siai orenen erap ane ae i e a I e E ETE OnE EELEE ERGS 114 10 8 Supported Transports a O A iP hi A A a Dose ess Les 114 10 8 1 Shared Memory Communication between Applications Running in Kernel Mode and RTP Requires Explicitly Set Participant ID 2 esses eeeeceeececscceeeeees 115 10 8 2 How To Run Connext DDS Libraries in Kernels Built without Shared Memory 115 10 9 Monotonic Clock Support orita cda nta 116 10210 Thread Configuration cdas dara ltda cierto ada 116 10 10 1 Support for Controlling CPU Core Affinity for RTI Threads 222222202 116 10 11 Durable Writer History and Durable Reader State Features 220 0020 nennen 118 10 12 Libraries Required for Using Distributed Logger 2 2 2 eee 118 10 13 Libraries Required for Using Monitoring susssssslsssssslslllllslsssss s esses nnns 119 10 14 Increasing the Receive Socket Buffer Size eee eee eee eee eens 119 Chapter 11 Windows Platforms 11 1 Requirem
93. e 8 2 Building Instructions for QNX Architectures Required Required System Libraries Compiler Flags Library Format RTI Libraries 5c libnddscz a Static Release libnddscorez a librticonnextmsgcz a libnddsczd a Static Debug libnddscorezd a librticonnextms gezd a Im Isocket DRTI QNX libnddsc so Dynamic Release libnddscore so librticonnextmsgc so libnddscd so Dynamic Debug libnddscored so librticonnextms gced so Table 8 3 Running Instructions for QNX Architectures Library Format RTI Architecture Release amp Debug Environment Variables All supported QNX architectures LD_LIBRARY_PATH NDDSHOME lib lt architecture gt LD_LIBRARY_PATH 4 2Choose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API bThe DDS C C libraries are in NDDSHOME lib lt architecture gt The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type dg NDD SHOME represents the root directory of your Connext DDS installation LD_ LIBRARY _ PATH represents the value of the LD LIBRARY PATH variable prior to changing it to support Connext DDS When using nddsjava jar the Java virtual machine JVM will attempt to load release versions of the native libraries When using nddsjavad jar the JVM will attempt to load debug versions of the native libraries 77 8 1 Require
94. e following tables e Windows host platforms Table 11 2 Building Instructions for Windows Host Architectures e Windows target platforms Table 11 3 Building Instructions for Windows Target Architectures See also e Libraries Required for Using Distributed Logger Support Section 11 13 on page 144 e Libraries Required for Using RTI Secure WAN Transport APIs Section 11 15 on page 145 e Libraries Required for Using RTI TCP Transport APIs Section 11 16 on page 146 To use libraries that are statically linked into an application link in all of the libraries listed in one of the rows of these tables To use dynamic link libraries DLL on Windows systems link in all of the libraries listed in one of the Dynamic sections of the appropriate table When the application executes it will attempt to dynamically link in the libraries which are in the directory NDDSHOME lib lt architecture gt this directory must be placed on the path before the executable is started Windows libraries are provided in formats with and without debugging symbols Choose the format appro priate for your current work Do not mix libraries built for different formats The RTI NET assemblies are supported for both the C CLI and C languages The type support code generated by rtiddsgen is in C CLI compiling the generated type support code requires Microsoft Visual C Calling the assembly from C requires Microsoft Visual C bWindows XP If you are
95. e long DCSREAL IS FLOAT Wp MD Static Debug 110 Chapter 10 VxWorks Platforms Table 10 4 Library Creation Details for All VxWorks Architectures Library Format RTI Architecture Compiler Flags Used by RTI ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 DTOOL_ FAMILY gnu DTOOL e500v2gnu te500v2 mcpu 8548 mfloat gprs double mspe yes mabi spe D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION O2 fno strict aliasing Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD Static or Dynamic Release ppce500v2V x6 9 4gcc4 3 3 ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 DTOOL _ Staticor FAMILY gnu DTOOL e500v2gnu te500v2 mcpu 8548 mfloat gprs double mspe yes Dynamic mabi spe D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR Debug VERSION 6 DVXWORKS MINOR VERSION Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT Wp MD ccppc mstrict align m32 mregnames ansi mlongcall DCPU PPC32 DTOOL _ Staticor FAMILY gnu DTOOL gnu te500v2 mcpu 8548 mfloat gprs double mspe yes Dynamic mabi spe mrtp D PROTOTYPE 5 0 O2 fno strict aliasing Wall Wno unknown Release pragmas DRTS VXWORKS DVXWORKS MAJOR VERSION 6 DVXWORKS _ ppce500v2Vx6 9 4gc04 3 3 MINOR VERSION DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD rtp ccppc mstrict align m32 mregnames an
96. ead stack size CPU core affinity not supported e 3 D 3 Q d 3 3 B E BE E e x A la a a a z zi EI cpu rotation CPU core affinity not supported 92 9 7 Durable Writer History and Durable Reader State Features Table 9 5 Thread Settings for Solaris Platforms DDS_ Applicable Thread ThreadSettings_ Platform Specific Setting t DDS THREAD SETTINGS STDIO DDS_THREAD_ SETTINGS FLOATING POINT mask priority OS default thread priority Ld stack size OS default thread stack size cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported Table 9 6 Thread Priority Definitions for Solaris Platforms Thread Priority Definition Operating System Priority THREAD PRIORITY DEFAULT 9999999 THREAD PRIORITY HIGH 9999999 THREAD PRIORITY ABOVE NORMAL 9999999 THREAD PRIORITY NORMAL 9999999 THREAD PRIORITY BELOW NORMAL 9999999 THREAD PRIORITY LOW 9999999 9 7 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on Solaris platforms 9 8 Distributed Logger Support RTI Distributed Logger is not supported on Solaris platforms 93 9 9 Libraries Required for Using Monitoring 9 9 Libraries Required for Using Monitoring Make sure you are consistent in your use of static dynamic debug and release versions of the libraries For example if your Connext DDS application is linked with the static release versio
97. eeellssssss se mnes rrr rrr 82 8 9 Libraries Required for Using Monitoring ooo s e RR RR rrr rr rrrrllls 82 8 10 Libraries Required for Using RTI Secure WAN Transport APIs 000000 2 22 cece eee cence eee eee eee 83 8 11 Libraries Required for Using RTI TCP Transport APIs LLuuuuuuuusuuellllsssssssees s sss s e eee 83 8 12 Restarting Applications on QNX Systems 2 22 2 s se esses rre leslie 84 Chapter 9 Solaris Platforms 9 1 Request Reply Communication Pattem 2 2 eee ee 89 92 S pport for Modem CRAP o a i AA eu cle 90 9 3 M lticast Suppolt A ee d ucla ae ates te hl ee dancin haat tks 614 90 9 4 Supported Transports 32 3 odor bo M EI IAE 90 9 4 1 Shared Memory Support ns 90 9 4 2 Increasing Available Shared Resources ooo 91 9 5 Monotonic Clock Support ns 91 9 6 Thread Configuration ad acia 92 9 6 1 Support for Controlling CPU Core Affinity for RTI Threads ooooccccccccccccccccccccccccccccccccoco 92 9 7 Durable Writer History and Durable Reader State Features iiiiiiuuuuuuusssssssssselesssss esses enne 93 9 8 Distributed Eogge r Support mio it nde de emu ees 22 ack icc rv9R data bajita 93 9 9 Libraries Required for Using Monitoring ooo e e RR RR rrr rrr rrr 94 9 10 Libraries Required for using RTI Secure WAN Transport APIs oo 2 2222 eee eee cece cece ee eene 94 Chapter 10 VxWorks Platforms 10 1 Required Makefile Change for VxWorks 7 0 Platforms ssiussssssssessssssssss e ser nnn
98. entium march pentium nostdlib fno builtin fno defer pop fno implicit Static or fp ansi fno zero initialized in bss Wall MD MP DCPU VX PENTIUMA DTOOL _ Dynamic FAMILY gnu DTOOL gnu D WRS KERNEL g DVXWORKS MAJOR VERSION 7 Release DVXWORKS MINOR VERSION 0 Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DNDEBUG pentiumVx7 0gcc4 3 3 ccpentium mtune pentium march pentium nostdlib fno builtin fno defer pop fno implicit Static or fp ansi fno zero initialized in bss Wall MD MP DCPU VX PENTIUMA DTOOL __ Dynamic FAMILY gnu DTOOL gnu D WRS KERNEL g DVXWORKS MAJOR VERSION 7 Debug DVXWORKS MINOR VERSION 0 Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT ccpentium mtune pentium4 march pentium4 mrtp fno strict aliasing fasm Wall MD MP Staticor D VX CPU VX PENTIUM D VX TOOL FAMILY gnu D VX TOOL gnu D Dynamic C99 D HAS C9X std c99 g Wall Wno unknown pragmas DRTS VXWORKS Release DVXWORKS MAJOR VERSION 7 DVXWORKS MINOR VERSION 0 DPtrIntType long DCSREAL IS FLOAT DNDEBUG pentiumVx7 0gcc4 3 3 rtp ccpentium mtune pentium4 march pentium4 mrtp fno strict aliasing fasm Wall MD MP Staticor D VX CPU VX PENTIUM D VX TOOL FAMILY gnu D VX TOOL gnu D Dynamic C99 D HAS C9X std c99 g Wall Wno unknown pragmas DRTS VXWORKS Debug DVXWORKS MAJOR VERSION 7 DVXWORKS MINOR VERSION 0 DPtrIntType long DCSREAL IS FLOAT DNDEBUG 1
99. ents when Using Microsoft Visual Studio 2 2 eee eee nn nn nn 138 11 2 Windows Registry Setting for Better Performance 2 22 coc eee e eee 140 11 3 Use Dynamic MFC Library Not Static 2 0 00 o elle ccc cece ee eee cece Iesse rere reli 140 11 4 NET API Requires Thread Affinity 200 2 2022 loci e cece e ee rrr Reese eeees 140 11 5 ODBC Database Compatibility 2 20 e cence ee rr rr lle 140 11 6 PPP Link Support for Windows XP Systems 0220022 ees 141 11 7 Support tor Modern CHF API eee cele heck ealesa Soe eben didas 142 11 8 Multicast Sapport lo E A A ce rPPOD UR EVER ns zone PENN 142 11 9 Supported Transports ELLE A A E i e n RR e RR DS Sod 142 11 10 Monotonic Clock Support oc 142 TI Thread Configuration sheer octets ehh a E LA CS t EE E IA A SO eA A AEE ES EET 142 11 11 1 Support for Controlling CPU Core Affinity for RTI Threads 2 0 0 0 cece cece cence eee ee ee ees 144 11 12 Durable Writer History and Durable Reader State Features ooooococcccccccccccccccocccccccccccrrnnnnnnos 144 11 13 Libraries Required for Using Distributed Logger Support 200000000 144 11 14 Libraries Required for Using Monitoring ooo 145 11 15 Libraries Required for Using RTI Secure WAN Transport APIs 2 2 0 eeees 145 11 16 Libraries Required for Using RTI TCP Transport APIs Luuuuuuuueeeeeeeeeeee eR RR RR RR rrr eres 146 Chapter 1 Supported Platforms This document provides platform specific in
100. ext DDS When using nddsjava jar the Java virtual machine JVM will attempt to load release versions of the native libraries When using nddsjavad jar the JVM will attempt to load debug versions of the native libraries 134 Chapter 11 Windows Platforms Table 11 5 Library Creation Details for Windows Architectures RTI Architecture 186Win32VS2008 i86Win32V S2010 Library Format Static Release Dynamic Release Static Debug Dynamic Debug Static Release Dynamic Release Compiler Flags Used by RTI DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Win32VS2008 DWIN32 D_WINDOWS D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN 02 Zi MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Win32VS2008 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Win32VS2008 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MTd EHsc RTC1 D CRT SECURE NO DEPRECATE c DPtrIntType long DCSREAL IS FLOAT DCPU 180586 DTARGE T i86Win32VS2008 DWIN32 D_ WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Win32VS2010 DWIN32 D WINDOWS D WIN32 WINNT 0x0501 DWIN32 LEAN
101. failure for the missing symbols sdOpen and sdUnmap as described below e For sdOpen we recommend providing an implementation that returns NULL and sets errno to ENOSYS For the function prototype refer to the file sdLib h in the VxWorks dis tribution e For sdUnmap we recommend providing an implementation that returns ERROR and sets errno to ENOSYS For the function prototype refer to the file sdLibCommon h in the VxWorks distribution 115 10 9 Monotonic Clock Support In addition to providing the symbol stubs for sdOpen and sdUnmap we also recommend disabling the SHMEM transport by using the transport_builtin mask in the QoS configuration 10 9 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is supported on VxWorks 6 3 and higher platforms This feature is not supported on VxWorks 653 2 3 platforms 10 10 Thread Configuration Table 10 6 Thread Setting for VxWorks Platforms Applies to Kernel Tasks or Real Time Process Threads lists the thread settings for VxWorks platforms Table 10 7 Thread Priority Definitions for VxWorks Platforms and Table 10 8 Thread Kinds for VxWorks Platforms list the thread priority definitions and thread kinds respectively 10 10 1 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Controlling CPU Core Affinity in the User s Manual is not available for VxWorks platforms Table 10 6
102. forms First see the basic instructions for compiling on Windows systems in the Building Applications chapter in the User s Manual The following tables provide supplemental information Table 11 1 Supported Windows Platforms lists the architectures supported on Windows operating systems 125 Chapter 11 Windows Platforms Table 11 1 Supported Windows Platforms Operating System CPU Visual Studio RTI Architecture NET JDK p 85y Version Abbreviation Version Version Windows 7 x86 Windows 8 x64 4 5 1 0 Windows 8 1 VS 2013 x64Win64V82013 VS 2008 SP1 186Win32V S2008 2 Windows 2003 VS 2008 SP1 x64Win64V S2008 dd Seryer 200g VS 2010 SP1 x64Win64VS2010 4 0 5 VS 2012 x64Win64V82012 Windows Server 2012 R x64 VS 2013 x64Win64V S2013 VS 2008 SP1 i86Win32V S2008 Windows Vista VS 2008 SP1 x64Win64V S2008 O E ee ee TE TT TIE 4The RTI NET assemblies are supported for both the C CLI and C languages The type support code generated by rtiddsgen is in C CLI compiling the generated type support code requires Microsoft Visual C Calling the assembly from C requires Microsoft Visual C 126 Chapter 11 Windows Platforms Table 11 1 Supported Windows Platforms Queratine System CPU Visual Studio RTI Architecture i A Version Abbreviation vaca eee Windows XP Pro SP2 gt c VS 2008 SP1 x64Win64V S2008 The compiler flags and the libraries you will need to link into your application are listed in th
103. g doubles for example if you specify qldb1128 or qlongdouble alone may produce unpredictable results Therefore RTI libraries compiled with qlongdouble are linked using 1C128 For more information please consult the IBM compiler reference website http pic dhe ibm com infocenter comphelp v121v141 index jsp topic 2Fcom ibm xlcpp121 aix d oc 2Fcompiler_ref 2Fopt_Idbl128 html 2 3 1 Notes for Using Shared Memory 2 3 1 Notes for Using Shared Memory By default the maximum number of shared memory segments you can use with AIX is quite small and limits the capability of Connext DDS applications to work properly over shared memory To increase the maximum number of shared memory segments an application can use set the following environment vari able before invoking your Connext DDS application EXTSHM ON This environment variable is not required if your application does not use the shared memory transport To see a list of shared memory resources in use please use the ipes command To clean up shared memory and shared semaphore resources please use the iperm command The shared memory keys used by Connext DDS are in the range of 0x400000 For example ipcs m grep 0x004 The shared semaphore keys used by Connext DDS are in the range of 0x800000 the shared mutex keys are in the range of 0xb00000 For example ipcs s grep 0x008 ipcs s grep 0x00b Please refer to the shared memory transport online documentati
104. g an Android SDK and for C C an Android NDK For a consumer device all programs applications and DDS utilities must be installed on the device as Apps apk files All Android Apps are loaded and executed by an instance of the Dalvik VM running as a Linux process No Connext DDS components or libraries have to be pre installed on the device that is taken care of by the Android build and packaging tools See the Android documentation for a full description of building and packaging Android Apps For a raw Linux distribution all programs are executables that are linked with the necessary Connext DDS libraries see Table 3 1 Supported Android Target Platforms The build process is similar to other Linux variants see Section 9 3 in the RTI Connext DDS Core Libraries User s Manual Release and Debug Terminology Android and Connext DDS use these terms differently For Android release and debug refer to how application packages apk are signed as part of the Android Security Model A release package is cryptographically signed by a key that can be trusted by virtue of some certificate chain A debug pack age is signed by a key distributed with the SDK It says nothing about the origin of the package It allows the package to be installed during development testing hence debug For Connext DDS debug means libraries created with debug symbols to facilitate debugging with gdb for example A release library does no
105. g and release versions of the libraries For example if your Connext DDS application is linked with the static release version of the Connext DDS libraries you will need to also use the static release version of the monitoring library Do not link both static and dynamic libraries Similarly do not mix release and debug libraries If you are statically linking your application with DDS libraries and you want to add monitoring to your application you will also need to statically link the monitoring library The library cannot be loaded dynam ically strictly through the QoS profile because it also depends on DDS to publish its data Therefore it depends on DDS the DDS functionality would cause duplicate symbols to be found resulting in the ter mination of the process Note If you plan to use static libraries the RTI library from Table 2 7 Additional Libraries for Using Mon itoring must appear first in the list of libraries to be linked Table 2 7 Additional Libraries for Using Monitoring Static Debug Dynamic Release Dynamic Debug librtimonitoringz a librtimonitoringzd a librtimonitoring so librtimonitoringd so Chapter 3 Android Platforms Table 3 1 Supported Android Target Platforms lists the architectures supported on the Android operating system Table 3 1 Supported Android Target Platforms Ca So CA o O dH EU eS A Abbreviation Android 2 3 4 4 ARMv7a armv7aAndroid2 3gcc4 8 an ava Platform Standard Edition JDK 1 7
106. g to your application you will also need to statically link the monitoring library The library cannot be loaded dynam ically strictly through the QoS profile because it also depends on DDS to publish its data Therefore it depends on DDS the DDS functionality would cause duplicate symbols to be found resulting in the ter mination of the process Note If you plan to use static libraries the RTI library from Table 5 11 Additional Libraries for Using Monitoring must appear first in the list of libraries to be linked Table 5 11 Additional Libraries for Using Monitoring Static Release Static Debug Dynamic Release Dynamic Debug librtimonitoringz a librtimonitoringzd a librtimonitoring so librtimonitoringd so 5 9 Libraries Required for Using RTI Secure WAN Transport APIs If you choose to use RTI Secure WAN Transport it must be downloaded and installed separately It is only available on specific architectures See the RTI Secure WAN Transport Release Notes and RTI Secure WAN Transport Installation Guide for details To use the Secure WAN Transport APIs link against the additional libraries in Table 5 12 Additional Libraries for using RTI Secure WAN Transport APIs on UNIX based Systems Select the files appro priate for your chosen library format 53 5 10 Libraries Required for Using RTI TCP Transport APIs Table 5 12 Additional Libraries for using RTI Secure WAN Transport APIs on UNIX based Systems Library Format RTI Secu
107. gome PowerPC cores such as e500v1 and e500v2 are not fully backwards compatible with PPC 604 For ppc405 the architecture string is the same for VxWorks 6 6 and 6 7 dg ome PowerPC cores such as e500v1 and e500v2 are not fully backwards compatible with PPC 604 For ppc405 the architecture string is the same for VxWorks 6 6 and 6 7 97 Chapter 10 VxWorks Platforms Table 10 1 Supported VxWorks Target Platforms System VxWorks 6 8 For Kernel Modules pentiumVx6 8gcc4 1 2 For Real Time Processes pentiumVx6 8gcc4 1 2 rtp For Kernel Modules ppc604V x6 8gcc4 1 2 Any PowerPC CPU with floating point hardware that is backwards compatible with 32 bit PowerPC 604 Pentium32 bit VxWorks 6 9 Any PowerPC CPU with floating point hardware that is backwards compatible with 32 bit PowerPC 604 For Real Time Processes ppc604V x6 8gcc4 1 2 rtp For Kernel Modules pentiumVx6 9gcc4 3 3 For Real Time Processes pentiumVx6 9gcc4 3 3_rtp For Kernel Modules ppc604V x6 9gcc4 3 3 For Real Time Processes ppc604V x6 9gcc4 3 3 rtp For Kernel Modules pentium64Vx6 9gcc4 3 3 For Real Time Processes pentium64Vx6 9gcc4 3 3_ rtp For Kernel Modules ppce500v2V x6 9 4gcc4 3 3 For Real Time Processes VxWorks i ppce500v2Vx6 9 4gcc4 3 3 VxWorks 694 PPC e500v2 rtp For Kernel Modules pentiumVx7 0gcc4 3 3 VxWorks 7 0 Pentium 32 bit gcc 4 3 3 For Real Time Processes pentiumVx7 0gcc4 3 3 rtp 3 32 VxWorks 65
108. gs_ Platform Specific Setting t cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO priority OS default thread priority Database thread stack_size 192 1024 cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported 2 6 Durable Writer History and Durable Reader State Features Table 2 5 Thread Settings for AIX Platforms DDS_ Applicable Thread ThreadSettings_ Platform Specific Setting DDS THREAD SETTINGS STDIO DDS THREAD maS SETTINGS FLOATING POINT mas t DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT ReceiverPool threads 4 192 1024 CPU core affinity not supported cpu rotation CPU core affinity not supported Table 2 6 Thread Priority Definitions for AIX Platforms Thread Priority Definition Operating System Priority THREAD PRIORITY DEFAULT 9999999 THREAD PRIORITY HIGH 9999999 THREAD PRIORITY ABOVE NORMAL 9999999 THREAD PRIORITY NORMAL 9999999 THREAD PRIORITY BELOW NORMAL 9999999 THREAD PRIORITY LOW 9999999 2 6 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on AIX platforms 2 7 Distributed Logger Support 2 7 Distributed Logger Support RTI Distributed Logger is not supported on AIX platforms 2 8 Libraries Required for Using Monitoring Make sure you are consistent in your use of static dynamic debu
109. ibcrypto so Static Rel libnddstransporttlsz a TNE libnddstransporttlszd a libnddstransportwanz a libnddstransportwanzd a Dynamic Debug Static Debug 8 11 Libraries Required for Using RTI TCP Transport APIs To use the TCP Transport APIs link against the additional libraries in Table 8 10 Additional Libraries for using RTI TCP Transport APIs on QNX 6 5 Systems It is only available for QNX 6 5 architectures If you are using RTI TLS Support see Table 8 11 Additional Libraries for using RTI TCP Transport APIs on QNX Systems with TLS Enabled Select the files appropriate for your chosen library format Table 8 10 Additional Libraries for using RTI TCP Transport APIs on QNX 6 5 Systems Library Format RTI TCP Transport Libraries Dynamic Release libnddstransporttcp so Dynamic Debug libnddstransporttcpd so The libraries are in lt NDDSHOME gt 7 lib lt architecture gt PThese libraries are in lt openssl install dir gt lt architecture gt lib These libraries are in lt NDDSHOME gt 1lib lt architecture gt 83 8 12 Restarting Applications on QNX Systems Table 8 10 Additional Libraries for using RTI TCP Transport APIs on QNX 6 5 Systems Library Format RTI TCP Transport Libraries Static Debug libnddstransporttcpzd a Table 8 11 Additional Libraries for using RTI TCP Transport APIs on QNX Systems with TLS Enabled Library Format RTI TLS Libraries Static Release libnddstlsz a Static Debug libnddstlszd
110. ic or Dynamic Debug mhard float mstrict align ansi mregnames mlongcall mrtp D PROTOTYPE 5 0 Static DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION S5 O Wall Release Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 DNDEBUG c Wp MD ppc604Vx6 5gcc3 4 4 rtp mhard float mstrict align ansi mregnames mlongcall mrtp D PROTOTYPE 5 0 g Static DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION S5 O Wall Debug Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 c Wp MD 108 Chapter 10 VxWorks Platforms Table 10 4 Library Creation Details for All VxWorks Architectures Library Format RTI Architecture Compiler Flags Used by RTI mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align ansi D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL_FAMILY gnu DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD Static or Dynamic Release ppc604V x6 6gcc4 1 2 mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align ansi D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR _ VERSION 6 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL_FAMILY gnu DPtrIntType long DCPU PPC604 c Wp MD Static or Dynamic Debug mhard float mlongcall mregnames mstrict align ansi mrtp D PROTOTYPE 5 0 Static
111. id Systems Select the files appropriate for your chosen library format Table 3 8 Additional Libraries for using RTI TCP Transport APIs on Android Systems Library Format RTI TCP Transport Libraries Dynamic Debug libnddstransporttcpd so Static Debug libnddstransporttcpzd a These libraries are in lt NDDSHOME gt lib lt architecture gt 23 Chapter 4 INTEGRITY Platforms Table 4 1 Supported INTEGRITY Target Platforms lists the architectures supported on the INTEGRITY operating system Table 4 1 Supported INTEGRITY Target Platforms INTEGRITY 5 0 11 PPC 85XX Multi 4 2 4 GHnet2 IP stack ppc85xxInty5 0 11 xes p2020 INTEGRITY 10 0 2 Multi 5 0 6 GHNet IPv4 stack pentiumInty10 0 2 pcx86 Multi 6 1 GHne v2 p4080Inty 1 1 devtree fsl e500mc comp2012 1 INTEGRITY 11 0 4 Multi 6 1 4 GHNet2 v2 p4080Inty11 devtree fsl e500mc comp2013 5 4d Pentium class Multi 6 1 4 GHNet2 pentiumInty 1 1 pcx86 smp Table 4 2 Building Instructions for INTEGRITY Architectures lists the compiler flags and the lib raries you will need to link into your application See also e Libraries Required for Using Distributed Logger Section 4 8 on page 31 e Libraries Required for Using Monitoring Section 4 9 on page 32 Do not mix release and debug libraries Kernel must be built using lip4 or lip46 DSee Required Patches for INTEGRITY 10 0 2 and 11 0 4 Section 4 1 on page 27 See Required Patches for INTEGRITY 10 0
112. imited by the size of the MTU on this interface which by default is 16384 bytes Since the default mes sage size max for the builtin UDPv4 transport is 65507 bytes the maximum UDP user payload you must adjust the size of the MTU of the loopback interface to accommodate UDP messages larger than 16384 bytes including the UDP header You can increase the size of the MTU with the following com mand gt itcoming Lol mea 65535 Note The maximum size ofthe MTU on the loopback interface is 65535 which will allow RTPS pay loads of 65507 bytes For more information on this issue contact Lynux Works Support about bug 30191 64 Chapter 7 OS X Platforms Table 7 1 Supported OS X Platformslists the architectures supported on Mac OS X operating sys tems Table 7 1 Supported OS X Platforms AO a A RTI EE A ere En Abbreviation clang 4 1 OS X 10 8 Lara Platform Stndad Edition IDK Te n onet Java isa Platform Standard Edition IDK 17 0 13 Standard Edition JDK 1 7 or 1 8 clang 6 0 OS X 10 10 x64 x64Darwinl4clang6 0 Java rior unti aon DK 170r 18 ava Platform Standard Edition JDK 1 7 or 1 8 Table 7 2 Building Instructions for OS X Architectures lists the compiler flags and libraries you will need to link into your application See also e Libraries Required for Using Distributed Logger Section 7 7 on page 72 e Libraries Required for Using Monitoring Section 7 8 on page 72 Libraries Required for Using RTI Secu
113. ion Table 4 6 Thread Priority Definitions for INTEGRITY 5 and 11 Platforms and Table 4 7 Thread Priority Definitions for INTEGRITY 10 Platforms list the thread priority definitions Table 4 5 Thread Settings for INTEGRITY Platforms DDS_ Applicable Thread ThreadSettings_ Platform Specific Setting t OS default thread type 127 for INTEGRITY 10 0 2 a a priority 16 for all other supported INTEGRITY platforms Asynchronous Publisher Asynchronous flushing thread stack_size 20 1024 cpu list CPU core affinity not supported cpu_rotation CPU core affinity not supported mask DDS THREAD SETTINGS STDIO 60 priority 1 INTEGRITY 10 0 2 only Database thread stack size 20 1024 cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported E DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT cpu rotation CPU core affinity not supported 29 4 6 Thread Configuration Table 4 5 Thread Settings for INTEGRITY Platforms DDS_ Applicable Thread ThreadSettings_ Platform Specific Setting t DDS THREAD SETTINGS STDIO ReceiverPool threads 4 20 1024 CPU core affinity not supported cpu rotation CPU core affinity not supported Table 4 6 Thread Priority Definitions for INTEGRITY 5 and 11 Platforms THREAD PRIORITY LOW 60 Table 4 7 Thread Priority Definitions for INTEGRITY 10 Platforms Thread Priority Definitions Operating System Priority THREAD PRIORITY ABOVE NORMAL THREAD
114. itional and Modern q 32 64 APIs libnddscpp so or libnddscpp2 so Dynamic Release libnddsc so libnddscore so librticonnextmsgcpp so qlongdouble 1d1 Insl Im pthread brtl libnddscppd so pose or libnddscpp2d so Dynamic Debug libnddscd so libnddscored so librticonnextms gcppd so AChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API PConnext DDS C C libraries are in NDD SHOME lib lt architecture gt NDDSHOME is where Connext DDS is installed see Paths Mentioned in Documentation Section 1 1 on page 3 The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type A Transports other than the default IP transport such as StarFabric may require linking in additional libraries For details see the API Reference HTML documentation or contact support rti com Use q32 if you build 32 bit code or q64 for 64 bit code Chapter 2 AIX Platforms Table 2 2 Building Instructions for AIX Architectures Library Required RTI Required System Required Compiler Format Libraries b c Libraries Flags libnddscz a Static Release libnddscorez a librticonnextmsgcz a Idi Insl Im pthread libnddsczd a eee Static Debug libnddscorezd a DRTI AIX librticonnextmsgezd a DRTI_UNIX q 32 64 libnddsc so qlongdouble Dynamic Release libnddsco
115. lic ations in the User s Manual The following tables provide supplemental information Table 5 1 Linux Platforms on ARM CPUs through Table 5 3 Linux Platforms on PowerPC CPUs list the supported Linux architectures Table 5 1 Linux Platforms on ARM CPUs k RTI Architecture gcc 4 7 2 Raspbian Wheezy 7 0 3 x ARMv6 D armv6vfphLinux3 xgcc4 7 2 kernel Java Platform Standard Edition JDK 1 7 or 1 8 Requires Linaro Gnueabihf Cross Compiler 38 Chapter 5 Linux Platforms Table 5 2 Linux Platforms on Intel CPUs Compiler RTI Architecture E Abbreviation gcc 4 1 2 Operating System 186Linux2 6gcc4 1 2 Java Platform Standard Edition JDK 1 7 or 1oOLinuxz Ogcc 1 8 gcc 4 1 2 CentOS 5 4 5 5 2 6 kernel ae x64Linux2 6gcc4 1 2 Java Platform Standard Edition JDK 1 7 or 1 8 gcc 4 4 5 Java Platform Standard Edition JDK 1 7 or x86 1 8 CentOS 6 0 6 2 6 4 2 6 kernel gcc 4 4 5 x64 i86Linux2 6gcc4 4 5 si x64Linux2 6gcc4 4 5 Java Platform Standard Edition JDK 1 7 or 1 8 Java Platform Standard Edition JDK 1 7 or 1 8 gcc 4 1 1 Java Platform Standard Edition JDK 1 7 or 1 8 Red Hat Enterprise Linux 4 0 2 6 kernel i86Linux2 6gcc4 1 1 Red Hat Enterprise Linux 5 0 2 6 kernel x64Linux2 6gcc4 1 1 R unning rtiddsgen on this platform is not supported because it uses an older JRE You can however run rtiddsgen on a newer Linux platform to generate code that can be used on the
116. load socket itcpip lbp queue ifbp idb bsl 4 13 Multi NIC Support on INTEGRITY 5 0 Due to limitations with the API of the InterPeak stack for INTEGRITY 5 0 Connext DDS only supports a single NIC when the InterPeak stack is used This NIC must be called eth0 By default on an INTEGRITY system this will correspond to the first network card which can be changed by recon figuring the kernel This limitation does not affect the InterNiche stack 4 14 Out of the box Transport Compatibility with Other Connext DDS Platforms Due to some default kernel parameters on INTEGRITY platforms the default value for message_size_ max for the UDPv4 transport and the default values for message size max received message count max and recv buffer size for the shared memory transport are different than those for other platforms This will cause out of the box compatibility issues that may result in lack of communication For more information on transport incompatibility see Transport Compatibility in the RTI Connext DDS Core Libraries Release Notes The mismatch in transport configuration between INTEGRITY and other plat forms applies to Connext DDS 5 1 0 and higher To address the compatibility issues you can change the default transport settings of other platforms to match those of the INTEGRITY platform Alternatively you can update the INTEGRITY kernel para meters as described below so that the INTEGRITY platform will support larger transpo
117. longcall DCPU PPC32 Staticor DTOOL FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 g Wall Wno Dynamic unknown pragmas DRTS VXWORKS DVXWORKS MAJOR VERSION 6 Debug DVXWORKS MINOR VERSION 8 DPtrIntType long DCSREAL IS FLOAT Wp MD ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 DTOOL _ FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 9 O2 fno strict aliasing Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD Static Release ppc604Vx6 9gcc4 3 3 ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 DTOOL_ FAMILY gnu DTOOL gnu D WRS KERNEL D_ PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS_MINOR_VERSION 9 Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT Wp MD Static Debug ccppc mhard float mstrict align m32 mregnames ansi mlongcall DCPU PPC32 DTOOL FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 O2 fno strict aliasing Wall Wno unknown pragmas DRTS VXWORKS DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 9 DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD Static Release ppc604Vx6 9gcc4 3 3 rtp ccppc mhard float mstrict align m32 mregnames ansi mlongcall DCPU PPC32 DTOOL FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 g Wall Wno unknown pragmas DRTS VXWORKS DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 9 DPtrIntTyp
118. mic libraries are not supported for VxWorks platforms on PPC CPUs using RTP mode PDynamic libraries are not supported for VxWorks platforms on PPC CPUs using RTP mode 119 10 14 Increasing the Receive Socket Buffer Size Table 10 11 Required Kernel Components for sbc8641Vx653 2 3gcc3 3 2 Install partition_socket_driver_v1 3 Follow instructions from Wind River for the installation 120 10 14 Increasing the Receive Socket Buffer Size Table 10 11 Required Kernel Components for sbc8641Vx653 2 3gcc3 3 2 PInstall partition socket driver v1 3 Follow instructions from Wind River for the installation 121 10 14 Increasing the Receive Socket Buffer Size Table 10 11 Required Kernel Components for sbc8641Vx653 2 3gcc3 3 2 INCLUDE NETDEV NAMEGET INCLUDE USR FS UTILS INCLUDE NETINET IF INCLUDE WDB INCLUDE NETINET IF ETHER INCLUDE WDB COMM END Table 10 12 Required Kernel Components for simpcVx653 2 3gcc3 3 24 DE ARINC SCHEDULER INIT DE ARP API DE BOOT LINE DE BOOT LINE INIT DE BSD SOCKET DE BSP MODULES Z Q DE BSP VXWORKS Z Q DE DEBUG CORE Z Q DE DEBUG UTIL Z Q DE END DE END BOOT Z Q DE FTP Z Q DE HOST TBL Z G DE ICMP Z Q DE IGMP DE IO EXTRA INIT DE NETINET IN PCB DE NETINET IN PROTO DE NETINET IP ICMP DE NETINET IP INPUT DE NETI
119. mlongcall DTOOL gnu mstrict align mno implicit fp ansi D _ WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 3 O Wall Wno unknown pragmas DRTS _ VXWORKS DTOOL_FAMILY gnu DPtrIntType long DCPU PPC604 c Wp MD Static or Dynamic Debug mhard float mlongcall mregnames mstrict align ansi DTOOL gnu mrtp D _ Static PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR Release VERSION 3 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 DNDEBUG c Wp MD ppc604Vx6 3gcc3 4 4 rtp mhard float mlongcall mregnames mstrict align ansi DTOOL gnu mrtp fPIC shared D Static PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR _ Debug VERSION 3 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL _ FAMILY gnu DPtrIntType long DCPU PPC32 c Wp MD mcpu 604 mstrict align fno builtin ansi mlongcall mno implicit fp D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION S O Wall Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL_FAMILY gnu DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD Static or Dynamic Release ppc604Vx6 5gcc3 4 4 mcpu 604 mstrict align fno builtin ansi mlongcall mno implicit fp D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION S O Wall Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL_FAMILY gnu DPtrIntType long DCPU PPC604 c Wp MD Stat
120. n of the Connext DDS libraries you will need to also use the static release version of the monitoring library Do not link both static and dynamic libraries Similarly do not mix release and debug libraries If you are statically linking your application with DDS libraries and you want to add monitoring to your application you will also need to statically link the monitoring library The library cannot be loaded dynam ically strictly through the QoS profile because it also depends on DDS to publish its data Therefore it depends on DDS the DDS functionality would cause duplicate symbols to be found resulting in the ter mination of the process Note If you plan to use static libraries the RTI library from Table 9 7 Additional Libraries for Using Mon itoring must appear first in the list of libraries to be linked Table 9 7 Additional Libraries for Using Monitoring Static Debug Dynamic Release Dynamic Debug librtimonitoringz a librtimonitoringzd a librtimonitoring so librtimonitoringd so 9 10 Libraries Required for using RTI Secure WAN Transport APIs This section is only relevant if you have installed RTI Secure WAN Transport This feature is not part of the standard Connext DDS package If you choose to use it it must be downloaded and installed sep arately It is only available on specific architectures See the RTI Secure WAN Transport Release Notes and RTI Secure WAN Transport Installation Guide for details To use the Sec
121. ng them having 100 System V semaphores will allow you to use 25 domain ID participant index combinations for Connext DDS applications You probably will not need to increase the shared memory parameters since the default allows 100 shared memory areas enough for 50 applications 9 5 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is supported on all Solaris plat forms 91 9 6 Thread Configuration 9 6 Thread Configuration Table 9 5 Thread Settings for Solaris Platforms lists the thread settings for Solaris platforms Table 9 6 Thread Priority Definitions for Solaris Platforms lists the thread priority definitions 9 6 1 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Controlling CPU Core Affinity in the User s Manual is not available for Solaris platforms Table 9 5 Thread Settings for Solaris Platforms DDS_ Applicable Thread ThreadSettings_ Platform Specific Setting t spine ont CPU core affinity not supported cpu_rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO OS default thread priority OS default thread stack size CPU core affinity not supported CPU core affinity not supported priority Database thread stack size cpu rotation priority DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT OS default thread priority Event thread stack size OS default thr
122. not be enough one is often used by the system so you ll run out at the 3rd application To increase the number of semaphores available to Connext DDS change the values of the following two parameters in etc system Starting in Solaris 10 there is an alternate mechanism to control these values but changing ete system will also work The following values are just an example set semsys seminfo semmni 100 set semsys seminfo semmns 100 If these parameters already exist in etc system change their values otherwise add the above lines to your letc system file WARNING Changing etc system should be done VERY carefully incorrect editing of the file can render your system unbootable System V semaphores are allocated by creating groups of individual semaphores The first parameter above controls the maximum number of semaphore groups and the second controls the maximum total number of semaphores within any and all groups Each Connext DDS application that has shared memory enabled allocates 4 groups of 1 semaphore each per DDS domain So setting the two values to the same number will work fine as far as Connext DDS is concerned However if other applications in the system want to allocate bigger groups you could set semsys seminfo_semmns larger than sem sys seminfo semmni Setting semmni bigger than semmns does not make any sense since groups can t have less than 1 semaphore In the absence of other applications usi
123. o load debug versions of the native libraries 133 Chapter 11 Windows Platforms Table 11 4 Running Instructions for Windows Architectures RTI Architecture Library Format Environment Variables Dynamic Release and Debug Path NDDSHOME lib lt architecture gt Path All other supported Windows architectures Table 11 5 Library Creation Details for Windows Architectures RTI Library O Earmiat Compiler Flags Used by RTI Dynamic 02 GL D WIN32 D NDEBUG D NDDS_DLL_VARIABLE Rc D WINDLL D UNICODE D UNICODE FD EHa MD c AII 32 bit Windows Zi clr TP architectures for NET Dynamic Od D WIN32 D _DEBUG D NDDS_DLL_VARIABLE ynam WINDLL D UNICODE D UNICODE FD EHa MDd c Debug e E Zi clr TP Dynamic O2 GL D WIN64 D NDEBUG D NDDS DLL VARIABLE Release D _WINDLL D _UNICODE D UNICODE FD EHa MD All 64 bit Windows c Zi clr TP architectures for NET Od D WIN64 D _DEBUG D NDDS_DLL_VARIABLE Dynamic D _WINDLL D UNICODE D UNICODE FD EHa Debug MDd c Zi clr TP Dynamic Release target 1 4 source 1 4 All 32 bit Windows architectures for Java Dynamic Debug target 1 4 source 1 4 g Dynamic Release target 1 4 source 1 6 All 64 bit Windows architectures for Java Dynamic Debug target 1 4 source 1 6 g a6 Path represents the value of the Path variable prior to changing it to support Conn
124. ogger is supported on all the platforms in Table 5 1 Linux Platforms on ARM CPUs through Table 5 3 Linux Platforms on PowerPC CPUsexcept the following e Freescale P2020RDB e Linux platforms on PowerPC CPUs e Red Hat Enterprise 4 0 5 2 with Real Time Extensions e Wind River Linux 3 and 4 e Yellow Dog Linux 4 0 To use the Distributed Logger APIs links against the additional libraries in Table 5 10 Additional Librar ies for using RTI Distributed Logger Select the files appropriate for your chosen library format Table 5 10 Additional Libraries for using RTI Distributed Logger Language esd librtidlez a librtidlezd a librtidlc so Hb ddso 000 so C librtidlez a librtidlez a librtidlc so librtidled so Traditional API librtidlcppz a librtidlcppz a librtidlcpp so librtidlcppd so distlog jar distlogd jar distlogdatamodel jar distlogdatamodeld jar 52 5 8 Libraries Required for Using Monitoring 5 8 Libraries Required for Using Monitoring Make sure you are consistent in your use of static dynamic debug and release versions of the libraries For example if your Connext DDS application is linked with the static release version of the Connext DDS libraries you will need to also use the static release version of the monitoring library Do not link both static and dynamic libraries Similarly do not mix release and debug libraries If you are statically linking your application with DDS libraries and you want to add monitorin
125. on for details on the shared memory and semaphore keys used by Connext DDS 2 4 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is not supported on AIX archi tectures 2 5 Thread Configuration Table 2 5 Thread Settings for AIX Platforms lists the thread settings for AIX platforms Table 2 6 Thread Priority Definitions for AIX Platforms lists the thread priority definitions for AIX plat forms 2 5 1 Changing Thread Priority Due to the AIX threading model implementation there are situations that require you to run your Connext DDS application with root privileges 2 5 2 Support for Controlling CPU Core Affinity for RTI Threads e For all APIs Your application must have root privileges to use the thread option DDS _ THREAD SETTINGS REALTIME PRIORITY for the event and receiver pool thread QoS DDS_DomainParticipantQos event thread DDS_DomainParticipantQos receiver_pool thread e For the Java API only Your application must have root privileges to change the event and receiver pool thread priorities DDS_DomainParticipantQos event thread DDS_DomainPar ticipantQos receiver_pool thread 2 5 2 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Controlling CPU Core Affinity in the User s Manual is not available for AIX platforms Table 2 5 Thread Settings for AIX Platforms DDS_ Applicable Thread ThreadSettin
126. onnext DDS is installed see Paths Mentioned in Documentation Section 1 1 on page 3 The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 67 Chapter 7 OS X Platforms Table 7 3 Running Instructions for OS X Architectures Library Format RTI Architecture Required Environment Variables Release amp Debug x64Darwin 1 2clang4 1 TREE DYLD LIBRARY PATH NDDSHOME lib x64Darwin12clang4 1 DYLD 7 LIBRARY PATH x64Darwinl2clang4 1 for N A DYLD LIBRARY PATH NDDSHOME lib x64Darwin12clang4 1 DYLD_ Java LIBRARY PATHj x64Darwinl4clang6 0 MEOS DYLD LIBRARY PATH NDDSHOME lib x64Darwinl4clang6 0 S DYLD y LIBRARY PATH x64Darwin14clang6 0 for DYLD LIBRARY PATH NDDSHOME J lib x64Darwinl4clang6 0 DYLD Java LIBRARY PATH Table 7 4 Library Creation Details for OS X Architectures Library Format RTI Architecture Compiler Flags Used by RTI Static amp Dynamic Rel O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT MS DCPU AMD64 DTARGET x64Darwin12clang4 1 c Wp MD x64Darwinl2clang4 1 g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT Debug DCPU AMD64 DTARGET x64Darwin12clang4 1 c Wp MD a NDDSHOME is where Connext DDS is installed DYLD_LIBRARY_ PATH represents the value of the DYLD LIBRARY PATH va
127. ooccccccccccccccccccccccccccccnnnnnnnn cnn ss sse esee 52 5 8 Libraries Required for Using Monitoring ooo II RR RR rrr rrr Ille 53 5 9 Libraries Required for Using RTI Secure WAN Transport APIs uuuuuueeuelesesssse cece eee ceeceeeees 53 5 10 Libraries Required for Using RTI TCP Transport APIs 2 22222 s er ee 54 Chapter 6 LynxOS Platforms 6 1 Support for Modern C API oo ee ne ll rl le e esses 60 62 Multicast Support 12 4 Stt A eh eee ee a ee gU EG 60 6 3 Supported Transports cr A WE EIE UI a SER IOdii 61 6 3 1 Shared Memory Support _ 20000000 occ cece eee lll lr lll 61 6 4 Monotonic Clock Support o nan 61 6 5 Thread Configuration 61 6 5 1 Support for Controlling CPU Core Affinity for RTI Threads 20 222222 e eee eee eee eee 62 6 6 Durable Writer History and Durable Reader State Features 000 000000000 cece cece ccc cece eee e eee eeeeee 63 6 7 Distributed Logger Support 2 2 eee lr ene e e esee 63 6 8 Libraries Required for Using Monitoring ccslllllllllllllllllslnmI mI RR RI RR Ir Ir rrr 63 6 9 IP Fragmentation ISSUES via Satie I pe tt RI had bse ey ue 64 Chapter 7 OS X Platforms Support tor Modern C CE ARI id tt a nieedek eR AIRaR iN RIA EE 69 T2 Multicast Support cerises llull dais ddr iodine ini et REI feos 69 7 3 Supported Prams pos 2t ecce ob A A acd dos ane ea onu dek ades As ela Lii 69 74 Monotonice Glock Support 2 2 uidere rti a iiidoc Seeks th dda docs
128. or 1 85 Table 3 2 Building Instructions for Android Architectures lists the compiler flags and libraries you will need to link into your application See also e Libraries Required for Using RTI TCP Transport APIs Section 3 9 on page 23 e Libraries Required for Using Monitoring Section 3 8 on page 22 Make sure you are consistent in your use of static dynamic debug and release versions of the lib raries Do not link both static and dynamic libraries Similarly do not mix release and debug lib raries Table 3 3 Running Instructions for Android Architectures provides details on the environment vari ables that must be set at run time for an Android architecture Table 3 4 Library Creation Details for Android Architectures provides details on how the libraries were built This table is provided strictly for informational purposes you do not need to use these Built against Android 2 3 and tested on Android 4 2 bDalvik VM is JDK 1 5 with some features from 1 6 See Android documentation for details Chapter 3 Android Platforms parameters to compile your application You may find this information useful if you are involved in any in depth debugging Connext DDS supports the Android operating system as a target platform The target can be in one of two configurations a consumer device e g a Google Nexus 7 tablet or as a raw Linux distribution Building applications for the target occurs on a development machine usin
129. pe warnings non shared exceptions unknown pragma silent Rel link templat p4080Inty1 1 devtree fs1 LCP ink_once_templates e500mc comp2013 5 4 Static 1 Debug bsp devtree fsl e500mc prototype warnings non shared exceptions Static bspname pcx86 prefixed msgs unknown pragma silent G DPtrIntType long DCSREAL _ Release IS FLOAT DCPU DTARGET pentiumiInty10 0 2 pcx86 DNDEBUG c pentiumInty10 0 2 pcx86 Static bspname pcx86 prefixed_msgs unknown pragma silent G DPtrIntType long DCSREAL _ Debug IS FLOAT DCPU DTARGET pentiumInty10 0 2 pcx86 c bsp pcx86 smp prefixed_msgs unknown_pragma silent link_once_templates fexceptions DPtrIntType long DCSREAL IS FLOAT DCPU pentium DTARGET pentiumInty1 1 pcx86 smp DNDEBUG Static Release pentiumInty1 1 pcx86 sm P bsp pcx86 smp prefixed msgs unknown pragma silent link once templates fexceptions DRTS INTY DPtrIntType long DCSREAL IS FLOAT DCPU pentium DTARGET pentiumInty1 1 pcx86 smp Static Debug Static bspname xes p2020 prefixed_msgs unknown pragma silent G DPtrIntType long Release DCSREAL IS FLOAT DCPU DTARGET ppc85xxInty5 0 11 xes p2020 DNDEBUG c ppc85xxInty5 0 11 xes p2020 A bspname xes p2020 prefixed_msgs unknown pragma silent G DPtrIntType long DCSREAL IS FLOAT DCPU DTARGETS ppc85xxInty5 0 11 xes p2020 c 4 1 Required Patches for INTEGRITY 10 0 2 and 11 0 4 For
130. point hardware that is gcc 3 4 4 backwards compatible with 32 bit PowerPC 604 For kernel modules ppc604V x6 5gcc3 4 4 VxWorks 6 5 For Real Time Processes ppc604V x6 5gcc3 4 4 rtp as use with Windows and or Solaris Hosts as supported by Wind River Systems bg ome PowerPC cores such as e500v1 and e500v2 are not fully backwards compatible with PPC 604 96 Chapter 10 VxWorks Platforms Table 10 1 Supported VxWorks Target Platforms System For Kernel Modules pentiumVx6 6gcc4 1 2 Pentium For Real Time Processes pentiumVx6 6gcc4 1 2 rtp For Kernel Modules Any PowerPC CPU with floating point hardware that is ppc604V x6 6gcc4 1 2 Vx Works 6 6 backwards compatible with 32 bit PowerPC 604 For Real Time Processes ppc604V x6 6gcc4 1 2 rtp For Kernel Modules ppc405Vx6 6gcc4 1 2 PPC 405 For Real Time Processes ppc405Vx6 6gcc4 1 2_rtp For Kernel Modules pentiumVx6 7gcc4 1 2 Pentium For Real Time Processes pentiumVx6 7gcc4 1 2 rtp For Kernel Modules ppc604V x6 7gcc4 1 2 For Real Time Processes Any PowerPC CPU with floating point hardware that is on non SMP systems IO Bo backwards compatible with 32 bit PowerPC 6044 ppc604Vx6 7gcc4 1 2 rtp For Real Time Processes on SMP systems ppc604Vx6 7gcc4 1 2 smp For Kernel Modules ppc405Vx6 7gcc4 1 2 PPC 405 For Real Time Processes ppc405V x6 7gcc4 1 2 rtp AFor use with Windows and or Solaris Hosts as supported by Wind River Systems b
131. port for Controlling CPU Core Affinity for RTI Threads Table 11 7 Thread Priority Definitions for Windows Platforms Thread Priority Definition Operating System Priority THREAD PRIORITY LOW Table 11 8 Thread Kinds for Windows Platforms R Kinds em Caer Configuration DDS THREAD SETTINGS STDIO porc NE THREAD SETTINGS REALTIME PRIORITY bosmme serras PRIORITY esrorce THREAD SETTINGS PRIORITY ENFORCE 11 11 1 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Controlling CPU Core Affinity in the User s Manual is not available for Windows platforms 11 12 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are only supported on platforms that use 32 bit 64 bit Visual Studio 2008 and Visual Studio 2010 11 13 Libraries Required for Using Distributed Logger Support RTI Distributed Logger is supported on all Windows platforms Table 11 9 Additional Libraries for using RTI Distributed Logger lists the additional libraries you will need in order to use Distributed Logger See Windows manuals for additional information 144 11 14 Libraries Required for Using Monitoring Table 11 9 Additional Libraries for using RTI Distributed Logger Language e eitis lib rtidlczd lib rtidlc dll iaat dll distlog jar distlogd jar Java NA NA distlogdatamodel jar distlogdatamodeld jar rtidlez
132. pported on CentOS 5 4 and higher Red Hat Enterprise Linux 4 0 and higher Ubuntu server 10 04 and higher Raspbian Wheezy 7 0 SUSE Linux Enterprise Server 11 This is not a built in transport 5 3 1 Shared Memory Support To see a list of shared memory resources in use please use the ipes command To clean up shared memory and shared semaphore resources please use the iperm command The shared memory keys used by Connext DDS are in the range of 0x400000 For example ipcs m grep 0x004 The shared semaphore keys used by Connext DDS are in the range of 0x800000 the shared mutex keys are in the range of 0xb00000 For example ios a ciao QOO ipcs s grep 0x00b Please refer to the shared memory transport online documentation for details on the shared memory and semaphore keys used by Connext DDS 5 4 Monotonic Clock Support The monotonic clock described in Clock Selection in the User s Manual is supported on platforms with all Linux 2 6 kernel or higher 5 5 Thread Configuration Table 5 7 Thread Settings for Linux Platforms lists the thread settings for Linux platforms Table 5 8 Thread Priority Definitions for Linux Platforms and Table 5 9 Thread Kinds for Linux Plat formslist the thread priority definitions and thread kinds respectively 48 5 5 1 Native POSIX Thread Library NPTL Requirements 5 5 1 Native POSIX Thread Library NPTL Requirements This section applies only to these platforms Red
133. process Note If you are plan to use static libraries the RTI library from Table 8 8 Additional Libraries for Using Monitoring must appear first in the list of libraries to be linked Table 8 8 Additional Libraries for Using Monitoring Static Debug Dynamic Release Dynamic Debug librtimonitoringz a librtimonitoringzd a librtimonitoring so librtimonitoringd so To use dynamic libraries make sure the permissions on the so library files are readable by everyone gt To use dynamic libraries make sure the permissions on the so library files are readable by everyone 82 8 10 Libraries Required for Using RTI Secure WAN Transport APIs 8 10 Libraries Required for Using RTI Secure WAN Transport APIs If you choose to use RTI Secure WAN Transport it must be downloaded and installed separately It is only available for QNX 6 5 architectures See the RTI Secure WAN Transport Release Notes and RTI Secure WAN Transport Installation Guide for details To use the Secure WAN Transport APIs link against the additional libraries in Table 8 9 Additional Libraries for using RTI Secure WAN Transport APIs on QNX 6 5 Systems Select the files appropriate for your chosen library format Table 8 9 Additional Libraries for using RTI Secure WAN Transport APIs on QNX 6 5 Systems Library Format RTI Secure WAN Transport Libraries OpenSSL Libraries f libnddstransportwan so libnddstransportwand so libnddstransporttlsd so libssl so l
134. proper concurrency control NET threads that call a Connext DDS API must correspond one to one with operating system threads In most applications this will always be the case However it may not be the case if the threads you are using are managed in a more advanced way for example Microsoft SQL Server does this or you may do so in your own application If you intend to call Connext DDS APIs from explicitly managed threads you must first call Thread Be ginThreadAffinity in each such thread to ensure that it remains attached to a single operating system thread See http msdn microsoft com en us library system threading thread beginthreadaffinity aspx When you are done making RTI calls from a given thread you should call Thread EndThreadA ffinity 0 In any case be sure to consult the RTI API documentation for more information about the thread safety contracts of the operations you use 11 5 ODBC Database Compatibility To use the Durable Writer History and Durable Reader State features you must install a relational data base such as MySQL 140 11 6 PPP Link Support for Windows XP Systems In principle you can use any database that provides an ODBC driver since ODBC is a standard However not all ODBC databases support the same feature set Therefore there is no guarantee that the persistent durability features will work with an arbitrary ODBC driver We have tested the following driver e MySQL ODBC 5 1 44 Note
135. re WAN Transport APIs Section 7 9 on page 72 Libraries Required for Using RTI TCP Transport APIs Section 7 10 on page 73 Make sure you are consistent in your use of static dynamic debug and release versions of the lib raries Do not link both static and dynamic libraries Similarly do not mix release and debug lib raries Table 7 3 Running Instructions for OS X Architectures provides details on the environment vari ables that must be set at run time for an OS X architecture 65 Chapter 7 OS X Platforms Table 7 4 Library Creation Details for OS X Architectures provides details on how the libraries were built by RTI This table is provided strictly for informational purposes you do not need to use these parameters to compile your application You may find this information useful if you are involved in any in depth debugging Table 7 2 Building Instructions for OS X Architectures Library ua ape Required System A API Required RTI Libraries EDan Required Compiler Flags libnddscppz a or libnddscpp2z a Static Release libnddscz a libnddscorez a librticonnextms gcppz a libnddscppzd a or dynamic libnddscpp2zd a Static Debug lpthread libnddsczd a libnddscorezd a lc C librticonnextms gcppzd a single module Traditional and ldl Im Ipthread Modem APIs libnddscpp dylib DETLUNES or DRTI DARWIN Dynamic libnddscpp2 dylib DRI DURCH Release libnddsc dylib T libnddscore dylib DRTI 64BIT librticonnextmsgcpp
136. re WAN Transport Libraries OpenSSL Libraries libnddstransportwan so Dynamic Release libnddstransporttls so libnddstransportwand so Dynamic Debug libnddstransporttlsd so libssl so libnddstransporttlsz a libcrypto so Static Release libnddstransporttlszd a libnddstransportwanz a Static Debug libnddstransportwanzd a 5 10 Libraries Required for Using RTI TCP Transport APIs To use the TCP Transport APIs link against the additional libraries inTable 5 13 Additional Libraries for using RTI TCP Transport APIs on UNIX based Systems If you are using RTI TLS Support see Table 5 14 Additional Libraries for using RTI TCP Transport APIs on UNIX based Systems with TLS Enabled Select the files appropriate for your chosen library format Table 5 13 Additional Libraries for using RTI TCP Transport APIs on UNIX based Systems Library Format RTI TCP Transport Libraries Dynamic Debug libnddstransporttcpd so Static Debug libnddstransporttcpzd a The libraries are in lt NDDSHOME gt 7 lib lt architecture gt PThese libraries are in lt openssl install dir gt lt architecture gt lib These libraries are in lt NDDSHOME gt 1lib lt architecture gt 54 5 10 Libraries Required for Using RTI TCP Transport APIs Table 5 14 Additional Libraries for using RTI TCP Transport APIs on UNIX based Systems with TLS Enabled Library Format RTI TLS Libraries Dynamic Release libnddstls so Dynamic Debug libnddstlsd so Static De
137. re so qthreaded f librti t A ibrticonnextmsgc so aide Im pth brtl libnddscd so pthread b Dynamic Debug libnddscored so librticonnextmsgcd so rticonnextmsg Jar N A nddsjavad jar rticonnextms gd jar 2Choose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API PConnext DDS C C libraries are in NDD SHOME lib lt architecture gt NDDSHOME is where Connext DDS is installed see Paths Mentioned in Documentation Section 1 1 on page 3 The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type A Transports other than the default IP transport such as StarFabric may require linking in additional libraries For details see the API Reference HTML documentation or contact support rti com Use q32 if you build 32 bit code or q64 for 64 bit code The qthreaded option is automatically set if you use one of the compilers that ends with r such as cc_ r xlc_r xIC r See the IBM XLC reference manual for more information Chapter 2 AIX Platforms Table 2 3 Running Instructions for AIX Architectures Library Format RTI Architecture Release amp Required Environment Variables Debug All supported AIX architectures for N A LIBPATH S NDDSHOME y lib lt arch gt S LIBPATH Java EXTSHM ON LIBPATH S NDDSHOME y lib lt arch gt LIBPATH EXTSHM ON
138. ri pheral compatibility across BSPs 4 16 Issues with INTEGRITY Systems 4 16 1 Delay When Writing to Unreachable Peers On INTEGRITY systems if a publishing application s initial peers list includes a nonexistent or simply unreachable host calls to writeQ may block for approximately 1 second This long block is caused by the stack trying to resolve the invalid unreachable host Most IP stacks do not block the sending thread because of this reason and you may include invalid unreachable hosts in your ini tial peers list If you find that your stack does block the sending thread please consult your IP stack vendor on how to change its behavior RTI Issue ID CORE 1637 4 16 2 Linking with libivfs a without a File System If you link your application with libivfs a and are using a system that does not have a file system you may notice the application blocks for 2 seconds at start up 4 16 3 Compiler Warnings Regarding Unrecognized pragma Directives Building Connext DDS projects for INTEGRITY causes the compiler to produce several warnings about pragma directives not recognized in some Connext DDS header files For example Building default bld C ndds ndds 4 4x include ndds dds c dds c infrastructure h line 926 warning unrecognized pragma pragma warning push C ndds ndds 4 4x include ndds dds c dds c infrastructure h line 927 warning unrecognized pragma pragma warning disable 4190 C ndds ndds 4 4x in
139. riable prior to changing it to support Connext DDS When using nddsjava jar the Java virtual machine JVM will attempt to load release versions of the native libraries nddsjava dylib nddscore dylib nddsc dylib When using nddsjavad jar the JVM will attempt to load debug versions of the native libraries nddsjava dylib nddscore dylib nddsc dylib 68 7 1 Support for Modern C API Table 7 4 Library Creation Details for OS X Architectures Library Format RTI Architecture Compiler Flags Used by RTI Static amp Dynamic Rel target 1 4 14 x64Darwinl2clang4 1 arge SOUICE for Java Debug target 1 4 source 1 4 g O Wall Wno unknown pragmas DPtrIntType long DCSREAL_IS_FLOAT DCPU AMD64 DTARGET x64Darwin14gcc6 0 c Wp MD x64Darwinl4gcc6 0 g Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Darwin 1 4gcc6 0 c Wp MD Rel target 1 4 1 4 x64Darwinl4gcc6 0 TET I for Java Debug target 1 4 source 1 4 g 7 1 Support for Modern C API Connext DDS provides two different C APIs which we refer to as the Traditional C and Modern C APIs The Modern C API is available for all OS X platforms For more information on Modern C see Traditional vs Modern C in the User s Manual 7 2 Multicast Support Multicast is supported on OS X platforms and is configured out of the box That is the default value for the initial peers list NDDS DISCOVERY
140. ries are in lt NDDSHOME gt lib lt architecture gt The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type din this version only ppc604Vx6 7gcc4 1 2 smp 100 Chapter 10 VxWorks Platforms Table 10 2 Building Instructions for VxWorks 5 x 7 x Architectures Required Compiler Flags Library Format Required Kernel Components Required RTI Libraries libnddscz a INCLUDE_TIMESTAMP libnddscorez a librticonnextmsgcz a Static Release For VxWorks 6 4 and below also use libnddsczd a INCLUDE_ZBUF SOCK libnddscorezd a INCLUDE_IGMP librticonnextmsgczd a DRTI VXWORKS libnddsc so For VxWorks 6 3 and higher also use libnddscore so INCLUDE POSIX CLOCKS librticonnextmsgc so libnddscd so For RTI architectures with SMP support libnddscored so for VxWorks 6 7 and higher also use librticonnextmsgced so INCLUDE_TLS 2Choose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API gt The Connext DDS C C libraries are in lt NDDSHOME gt lib lt architecture gt The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type dIn this version only ppc604Vx6 7gcc4 1 2 smp 101 Chapter 10 VxWorks Platforms Table 10 3 Building
141. rt settings The directive GM IP FRAG ENTRY MAX SIZE limits the size of UDP packets that can be sent and received by INTEGRITY platforms For details on this directive please see Section 5 4 2 in the net working pdf manual provided with the INTEGRITY kernel The default value of GM IP FRAG 33 4 14 1 Smaller Shared Memory Receive Resource Queue Size ENTRY MAX SIZE is 9216 bytes not 16 000 bytes as is stated in the INTEGRITY documentation which is why the default message_size_max for all transports supported for INTEGRITY is 9216 bytes If you want to send UDP messages larger than 9k you must increase the value of GM IP FRAG _ ENTRY MAX SIZE and rebuild the kernel You may also have to reconfigure other kernel parameters such as the socket stack and heap sizes to accommodate the larger value for GM IP FRAG ENTRY _ MAX SIZE Failing to increase this value will cause failures when sending large UDP packets and in some cases for example with the 5 0 11 kernel the sendto call will fail silently 4 14 1 Smaller Shared Memory Receive Resource Queue Size INTEGRITY s shared memory pluggable transport uses the shared memory POSIX API This API is part of the standard INTEGRITY distribution and is shipped as a library The current version 5 0 4 of this lib rary uses a hard coded value for the total amount of memory that can be shared with an address space This limits the overall buffer space that can be used by the DomainParticipants
142. s the Traditional C and Modem C APIs The Modem C API is only available for the LynxOS 5 0 platform For more information on Modern C see Traditional vs Modern C in the User s Manual 6 2 Multicast Support Multicast is supported on all LynxOS platforms but it is not configured out of the box That is the default value for the initial peers list NDDS DISCOVERY PEERS does not include a multicast address To configure a LynxOS target to use multicast you need to add routes so multicast packets will be sent via the proper network interfaces To add routes use the route add command The specific parameters depend on how the target is configured the name of the interface such as elxl0 in the example below etc Please refer to your LynxOS documentation for details on the route add command For example route add net 224 0 0 0 netmask 240 0 0 0 interface elxl0 Note Group Address Ignored for Multicast Reception on Loopback On LynxOS architectures the multicast loopback implementation ignores the group address when receiving messages This causes 60 6 3 Supported Transports Connext DDS to receive all outgoing multicast traffic originating from the host for that port Thus if you have two participants on the same host and in the same DDS domain both listening for discovery traffic over multicast they will discover each other regardless of the multicast address to which they are listen ing The correct beh
143. s to your project files 145 11 16 Libraries Required for Using RTI TCP Transport APIs Table 11 11 Additional Libraries for Using RTI Secure WAN Transport APIs on Windows Systems Library Format RTI Secure WAN Transport Libraries OpenSSL Libraries nddstransportwan lib Dynamic Release nddstransporttls lib nddstransporttlsd lib Dynamic Debug nddstransportwand lib ssleay32 lib libeay32 lib nddstransportwanz lib Static Release nddstransporttlsz lib nddstransportwanzd lib Static Debug nddstransporttlszd lib 11 16 Libraries Required for Using RTI TCP Transport APIs To use the TCP Transport APIs link against the additional libraries from Table 11 12 Additional Libraries for Using RTI TCP Transport APIs on Windows Systems or Table 11 13 Additional Libraries for using RTI TCP Transport APIs on Windows Systems with TLS Enabled Select the files appropriate for your chosen library format Table 11 12 Additional Libraries for Using RTI TCP Transport APIs on Windows Systems Library Format RTI TCP Transport Libraries Dynamic Debug nddstransporttcpd dll Static Debug nddstransporttcpzd lib These libraries are in lt lt NDDSHOME gt lib lt architecture gt PThese libraries are in lt openssl install dir gt lt architecture gt lib where lt openssl install dir is where OpenSSL is installed The libraries are in NDDSHOME Vib architecture 146 11 16 Libraries Required for Using RTI TCP Transport
144. se e ioe a e eee sess sess ssec llllllll 11 2 5 Thread Configuration Astrid Eu Rte A us s al ae 11 2 5 T Changing Thread Priority 25 32 62 IES eut UE TALLE EDI 11 2 5 2 Support for Controlling CPU Core Affinity for RTI Threads 2 2 2 0 00 ccc ccc cee cece cece eee 12 2 6 Durable Writer History and Durable Reader State Features 0 000000 o cece cece eee eee eens 13 2 7 Distributed Logger Support 22 2 ee eee eect e ellen 14 2 8 Libraries Required for Using Monitoring 2 2 2 eee eee eee cece rrr lll 14 Chapter 3 Android Platforms 3 1 Support for Modern C API oo eee sre ele ee e essen 19 3 2 Multicast Support _ 22 2 2 eee eee e eee raaraa nannaa 19 3 3 Supported Transports e Son05 x coceusus were dent pop eee qoo ete E Stone ruu voe eoe tanc dardo 20 34 Monotonic Clock Support cerillas Jecdeccuisdssseecuenck eie ni ii Rc itin chddace tds On CE NATO 20 3 5 Thread Configuration eerte Ri RI Ma iN n MI dem dene cie Ud mM red 20 3 5 1 Support for Controlling CPU Core Affinity for RTI Threads ooocccccccccccccccccccccccccccccccccoco 22 3 6 Durable Writer History and Durable Reader State Features 00 000000000 cece eee ccc cece cece eeeeees 22 3 7 Distnbuted Logger Support Basica atte nine Ene id gie RR NEA 22 3 8 Libraries Required for Using Monitoring ooo s e RR RR rrr rrr llle 22 3 9 Libraries Required for Using RTI TCP Transport APIs 00 0 022222 cece cece eee eee cence cece eee eeeee 23 Chapter 4
145. sg jar nddsjavad jar rticonnextms gd jar Required System Libraries sparc64Sol2 10gcc3 4 2 ldl Ins Isocket Igen lposix4 Ipthread Im lc All other architectures ldl Insl lgenIO lsocket Igen lposix4 Ipthread Im lc Required Compiler Flags sparc64Sol2 10gcc3 4 2 DRTL UNIX m64 All other architectures DRTL UNIX m32 None required AChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API bThe RTI C C Java libraries are in NDDSHOME libKarchitecture gt The jar files are in lt NDDSHOME gt 1lib java The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 87 Chapter 9 Solaris Platforms Table 9 3 Running Instructions for Solaris Architectures Library Format RTI Architecture Release amp Environment Variables Debug LD_LIBRARY PATH Api S NDDSHOME lib lt architecture gt LD_LIBRARY_PATH Java Note For all 64 bit Java architectures use d64 in the command line LD LIBRARY PATH NDDSHOME lib lt architecture gt LD LIBRARY PATH All supported Solaris native architectures Table 9 4 Library Creation Details for Solaris Architectures Library RTI Architecture Format Compiler Flags Used by RTI Static and D POSIX C SOURCE 199506L D_ EXTENSIONS DSolaris2 DSVR5 DSUNA Dynamic
146. si mlongcall DCPU PPC32 DTOOL _ Staticor FAMILY gnu DTOOL gnu te500v2 mcpu 8548 mfloat gprs double mspe yes Dynamic mabi spe mrtp D__PROTOTYPE_5_0 g Wall Wno unknown pragmas DRTS_ Debug VXWORKS DVXWORKS_MAJOR_VERSION 6 DVXWORKS_MINOR_VERSION 9 DPtrIntType long DCSREAL IS FLOAT Wp MD DTOOL_FAMILY gnu DTOOL gnu mlongcall Wall G 0 fno builtin mlongcall D_ WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 5 DVXWORKS MINOR VERSION S O Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU PPC604 DNDEBUG c Wp MD Static or Dynamic Release sbc8641Vx653 2 3gcc3 3 2 DTOOL FAMILY gnu DTOOL gnu mlongcall Wall G 0 fno builtin mlongcall D _ WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 5 DVXWORKS MINOR VERSION S5 Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU PPC604 c Wp MD Static or Dynamic Debug DTOOL_FAMILY gnu DTOOL gnu DCPU SIMNT Wall nostdlib fno defer pop fno Static or builtin mcpu pentium D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS _ Dynamic MAJOR VERSION 5 DVXWORKS MINOR VERSION S O Wno unknown pragmas Release DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU SIMNT DNDEBUG c Wp MD simpcVx653 2 3gcc3 3 2 DTOOL_FAMILY gnu DTOOL gnu DCPU SIMNT Wall nostdlib fno defer pop fno Static or builtin mcpu pentium D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS _ Dynamic MAJOR VERSION 5 DVXWORKS MIN
147. structions on how to compile link and run RTI Con next DDS applications Table 1 1 Available Platforms lists the platforms available with Connext DDS 5 2 0 Table 1 1 Available Platforms AIX AIX 5 3 7 1 AIX Platforms Chapter 2 on page 5 Android 2 3 4 4 Android Platforms Chapter 3 on page 15 ETT INTEGRITY Platforms Chapter 4 on page 24 ane CPU A CentOS 5 4 5 5 6 0 6 2 6 4 Red Hat Enterprise Linux 4 0 5 0 5 2 5 4 5 5 6 0 6 5 Linux 7 Linux Platforms Chapter 5 on page 38 Intel CPU SUSE Linux Enterprise Server 11 SP2 SP3 Ubuntu Server 12 04 LTS Ubuntu 14 Wind River Linux 4 Freescale P2020RDB Linux PowerPC Wind River Linux 3 CPU Yellow Dog M Linux 4 0 Chapter 1 Supported Platforms Table 1 1 Available Platforms VxWorks 5 5 6 3 6 9 6 9 3 2 6 9 4 7 0 VxWorks VxWorks Platforms Chapter 10 on page 96 VxWorks 653 2 3 Windows 7 8 8 1 Windows Server 2003 2008 R2 2012 R2 Windows Platforms Chapter 11 on page 125 Windows Vista Windows XP Professional SP2 For each platform this document provides information on e Supported operating systems and compilers e Required Connext DDS and system libraries e Required compiler and linker flags e Required environment variables for running the application if any e Details on how the Connext DDS libraries were built e Support for the Modern C API e Multicast support e Supported transports e
148. t Java Platform Standard Edition JDK 1 7 or 1 8 Table 9 2 Building Instructions for Solaris Architectures lists the compiler flags and the libraries you will need to link into your application gcc3 4 2 ItraSPAR Sol2 10gcc3 4 2 iras c Java Platform Standard Edition JDK 1 7 pasen ET or 1 8 Solaris 10 See also e VxWorks Platforms Chapter 10 on page 96 e Libraries Required for Using Monitoring Section 9 9 on page 94 e Libraries Required for using RTI Secure WAN Transport APIs Section 9 10 on page 94 85 Chapter 9 Solaris Platforms Make sure you are consistent in your use of static dynamic debug and release versions of the libraries Do not link both static and dynamic libraries Similarly do not mix release and debug libraries Table 9 3 Running Instructions for Solaris Architectures provides details on the environment variables that must be set at run time for a Solaris architecture When running on a Java 64 bit architecture use the d64 flag in the command line Table 9 4 Library Creation Details for Solaris Architectures provides details on how the libraries were built by RTI This table is provided strictly for informational purposes you do not need to use these para meters to compile your application You may find this information useful if you are involved in any in depth debugging Table 9 2 Building Instructions for Solaris Architectures Library RTI Libraries or R Required Compiler libnddscz a
149. t align ansi mrtp fPIC shared D Static PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR Debug VERSION 7 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 c Wp MD 109 Chapter 10 VxWorks Platforms Table 10 4 Library Creation Details for All VxWorks Architectures Library Format RTI Architecture Compiler Flags Used by RTI ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 DTOOL_ Staticor FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS _ Dynamic MAJOR VERSION 6 DVXWORKS MINOR VERSION 8 O2 fno strict aliasing Wall Release Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD ppc604Vx6 8gcc4 1 2 ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 DTOOL_ Staticor FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 g Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 8 Wall Wno Debug unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT Wp MD ccppc m32 mhard float mstrict align mregnames ansi mlongcall DCPU PPC32 Staticor DTOOL FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 O2 fno strict aliasing Dynamic Wall Wno unknown pragmas DRTS VXWORKS DVXWORKS MAJOR VERSION 6 Release DVXWORKS MINOR VERSION 8 DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD ppc604Vx6 8gcc4 1 2 rtp ccppe m32 mhard float mstrict align mregnames ansi m
150. t contain debug information Additional Documentation See the RTI Connext DDS Core Libraries Getting Started Guide Addendum for Android Platforms Chapter 3 Android Platforms Table 3 2 Building Instructions for Android Architectures Required RTI Libraries and JAR Filesabe Library Format Required System Libraries Required Compiler Flags libnddscppz a or libnddscpp2z a libnddscz a libnddscorez a libgnustl_shared a librticonnextmsgcppz a libnddscppzd a or libnddscpp2zd a libnddsczd a libnddscorezd a libgnustl_shared a C librticonnextms gcppzd a L SYSROOT usr lib Traditional and llog Im lc Ignustl_ Modern APIs libnddscpp so shared or libnddscpp2 so march armv7 a mfloat abi softfp mfpu vfpv3 d16 mlong calls DRTI_UNIX DRTI ANDROID libnddsc so libnddscore so libgnustl_shared so librticonnextms gcpp so libnddscppd so or libnddscpp2d so libnddscd so libnddscored so libgnustl_shared so librticonnextmsgcppd so AChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API gt The RTI C C Java libraries are in NDDSHOME llibKarchitecture gt The rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 17 Chapter 3 Android Platforms Table 3 2 Building Instructions for Android Architectures Required RTI Li
151. t need to use these para meters to compile your application You may find this information useful if you are involved in any in depth debugging Note The Java API is not currently supported on LynxOS platforms If you would like Java to be sup ported on LynxOS please contact your RTI account manager Table 6 2 Building Instructions for LynxOS Architectures Library Format Required RTI Libraries Ped libnddscppz a or libnddscpp2z a Static Release libnddscz a libnddscorez a librticonnextmsgcppz a libnddscppzd a or libnddscpp2zd a Static Debug libnddsczd a libnddscorezd a SE librticonnextmsgcppzd a Traditional and Modern APIs libnddscpp so or libnddscpp2 so libnddsc so libnddscore so librticonnextms gcpp so libnddscppd so or libnddscpp2d so URINE libnddscd so libnddscored so librticonnextmsgcppd so 4D ynamic libraries are not supported under LynxOS 178 PChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API The RTI C C libraries are in S NDDSHOME Ylib lt architecture gt where NDDSHOME is where Connext DDS is installed see Paths Mentioned in Documentation Section 1 1 on page 3 dThe rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type Dynamic Release 57 Chapter 6 LynxOS Platforms Table 6 2 Building Instructions for Lyn
152. tatic and Dynamic Release sparcSol2 9cc5 4 Static and Dynamic Debug Static and Dynamic Release sparcSol2 10gcc3 4 2 Static and Dynamic Debug Static and Dynamic Release sparc64S012 10gcc3 4 2 Static and Dynamic Debug Dynamic Release All supported Solaris architectures for Java Compiler Flags Used by RTI D_POSIX_C_SOURCE 199506L D_ EXTENSIONS DSolaris2 DSV R5 DSUN4_ SOLARIS2 KPIC O w DPtrIntType long DCPU SPARC DTARGET sparcS012 9cc5 4 DNDEBUG c D_POSIX_C_SOURCE 199506L D_ EXTENSIONS DSolaris2 DSVR5 DSUN4_ SOLARIS2 KPIC g w DPtrIntType long DCPU SPARC DTARGET sparcS012 9cc5 4 c D POSIX C SOURCE 199506L D_ EXTENSIONS DSolaris2 DSVR5 DSUNA SOLARIS2 O Wall Woverloaded virtual Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU SPARC DTARGET sparcSol2 10gcc3 4 21 DNDEBUG c Wp MD D POSIX C SOURCE 199506L D_ EXTENSIONS DSolaris2 DSVR5 DSUNA SOLARIS2 g O Wall Woverloaded virtual Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU SPARC DTARGET sparcSoD 10gcc3 4 2V c Wp MD m64 fPIC D POSIX C SOURCE 199506L D__ EXTENSIONS DSolaris2 DSVRS DSUNA SOLARIS O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU SPARC DTARGET sparc64Sol2 10gcc3 4 21 DNDEBUG c Wp MD m64 fPIC D POSIX C SOURCE 199506L D__ EXTENSIONS DSolaris2 DSVRS DSUNA SOLARIS g O Wall Wno unknown pragmas DP
153. tecture S LD EM LIBRARY PATH Table 6 5 Library Creation Details for LynxOS Architectures Library Format RTI Architecture Compiler Flags Used by RTI Static amp Dynamic mthreads mshared fPIC D POSIX THREADS CALLS D NO INCLUDE WARN Release O Wall Wno unknown pragmas DPtrIntType long DCPU I80586 DTARGET i86Lynx4 0 0gcc3 2 2 DNDEBUG c Wp MD 186Lynx4 0 0gcc3 2 2 mthreads mshared fPIC D POSIX THREADS CALLS D NO INCLUDE WARN g O Wall Wno unknown pragmas DPtrIntType long DCPU I80586 DTARGET i86Lynx4 0 0gcc3 2 2V c Wp MD mcpu 7400 maltivec mabi altivec fno exceptions mthreads mshared fPIC D POSIX Release THREADS CALLS D NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntType long DCPU PPC7400 DTARGET ppc7400Lynx4 0 0gcc3 2 2 DNDEBUG c Wp MD ppc7400Lynx4 0 0gcc3 2 2 mcpu 7400 maltivec mabi altivec fno exceptions mthreads mshared fPIC D_POSIX_ THREADS CALLS D NO INCLUDE WARN g O Wall Wno unknown pragmas DPtrIntType long DCPU PPC7400 DTARGET ppc7400Lynx4 0 0gcc3 2 2V c Wp MD mcpu 7400 maltivec mabi altivec fno exceptions mthreads mshared fPIC D POSIX THREADS CALLS D NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU PPC7400 DTARGET ppc7400Lynx4 2 0gcc3 2 21 DNDEBUG c Wp MD Release ppc7400Lynx4 2 0gec3 2 2 mcpu 7400 maltivec mabi altivec fno exceptions mthreads mshared fPIC
154. ter History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on INTEGRITY plat forms 4 8 Libraries Required for Using Distributed Logger RTI Distributed Logger is only supported for this architecture p4080Inty 1 1 devtree fsl e500m c comp2013 5 4 It is not supported on other INTEGRITY platforms Table 4 8 Additional Libraries for using RTI Distributed Logger lists the additional libraries you will need in order to use Distributed Logger 31 4 9 Libraries Required for Using Monitoring Table 4 8 Additional Libraries for using RTI Distributed Logger Language librtidlezd a a af i E EM librtidlezd a C librtidlcz a librtidlcppzd a Traditional API librtidlcppz a librtidlezd dba librtidlcppzd dba 4 9 Libraries Required for Using Monitoring Make sure you are consistent in your use of debug and release versions of the libraries For example if your Connext DDS application is linked with the release version of the Connext DDS libraries you will need to also use the release version of the monitoring library Note The RTI library from Table 4 9 Additional Libraries for Using Monitoring must appear first in the list of libraries to be linked Table 4 9 Additional Libraries for Using Monitoring Static Release Static Debug librtimonitoringz a librtimonitoringzd a 4 10 Request Reply Communication Pattern The Connext DDS Professional Rese
155. tic dynamic debug and release versions of the libraries For example if your Connext DDS application is linked with the static release version of the Connext DDS libraries you will need to also use the static release version of the monitoring library Do not link both static and dynamic libraries Similarly do not mix release and debug libraries If you are statically linking your application with DDS libraries and you want to add monitoring to your application you will also need to statically link the monitoring library The library cannot be loaded dynam ically strictly through the QoS profile because it also depends on DDS to publish its data Therefore it depends on DDS the DDS functionality would cause duplicate symbols to be found resulting in the ter mination of the process Note If you are plan to use static libraries the RTI library from Table 7 8 Additional Libraries for Using Monitoring must appear first in the list of libraries to be linked Table 7 8 Additional Libraries for Using Monitoring Static Debug Dynamic Release Dynamic Debug librtimonitoringz a librtimonitoringzd a librtimonitoring dylib librtimonitoringd dylib 7 9 Libraries Required for Using RTI Secure WAN Transport APIs If you choose to use RTI Secure WAN Transport it must be downloaded and installed separately It is available on all Mac OS X architectures See the RTI Secure WAN Transport Release Notes and RTI 72 7 10 Libraries Required for Using
156. trIntType long DCSREAL IS FLOAT DCPU SPARC DTARGET sparc64Sol2 10gcc3 4 21 c Wp MD target 1 4 source 1 4 target 1 4 source 1 4 g 9 1 Request Reply Communication Pattern The Connext DDS Professional Research Basic and Evaluation packages include support for the Request Reply Communication Pattern for all platforms in Table 9 1 Supported Solaris Platforms and all programming languages except as noted below The C and libnddsc were linked using gcc bThe C libnddscpp dynamic libraries were linked using g the C dynamic libraries i e libnddscore libnddscpp dynamic libraries were linked using g the C dynamic libraries i e libnddscore and libnddsc were linked using gcc 89 9 2 Support for Modern C API When using C the following platform does not support the Request Reply Communication Pattern e sparcSol2 9cc5 4 9 2 Support for Modern C API Connext DDS provides two different C APIs which we refer to as the Traditional C and Modern C APIs The Modern C API is only available for Solaris 2 10 platforms For more information on Modern C see Traditional vs Modern C in the User s Manual 9 3 Multicast Support Multicast is supported on Solaris platforms and is configured out of the box That is the default value for the initial peers list NDDS_DISCOVERY_PEERS includes a multicast address See the online doc umentation for more information
157. tructions for Windows Host Architectures Library C CLI Debug RTI Libraries or Jar Files nddscpp lib nddsc lib nddscore lib And one of these depending on your version of NET nddsdotnet dll for NET 2 0 nddsdotnet40 dll for NET 4 0 nddsdotnet45 dll for NET 4 5 nddsdotnet451 dll for NET 4 5 1 nddscppd lib nddscd lib nddscored lib And one of these depending on your version of NET nddsdotnetd dll for NET 2 0 nddsdotnet40d dll for NET 4 0 nddsdotnet45d dll for NET 4 5 nddsdotnet45 1d dll for NET 4 5 1 Required System Libraries Required Compiler Flags D RTI_WIN32 D NDDS_DLL_ VARIABLE MD D WIN32 LEAN AND MEAN D RTI WIN32 D NDDS DLL _ VARIABLE MDd D WIN32 LEAN AND MEAN 2Choose nddscpp for the Traditional C API or nddscpp2 for the Modern C API bThe RTI C C Java libraries are in NDDSHOME Vib architecture Jar files are in lt NDDSHOME gt lib java 130 Chapter 11 Windows Platforms Table 11 2 Building Instructions for Windows Host Architectures Library Release CH Debug Java RTI Libraries or Jar Files One of these depending on your version of NET nddsdotnet dll for NET 2 0 nddsdotnet40 dll for NET 4 0 nddsdotnet45 dll for NET 4 5 nddsdotnet451 dll for NET 4 5 1 And one of these depending on your version of NET rticonnextdotnet dll for NET 2 0 rticonnextdotnet40 dll for NET 4
158. ure WAN Transport APIs link against the additional libraries in Table 9 8 Additional Libraries for using RTI Secure WAN Transport APIs Select the files appropriate for your chosen library format 94 9 10 Libraries Required for using RTI Secure WAN Transport APIs Table 9 8 Additional Libraries for using RTI Secure WAN Transport APIs Library Format RTI Secure WAN Transport Libraries OpenSSL Libraries libnddstransportwan so Dynamic Release libnddstransporttls so libnddstransportwand so Dynamic Debug libnddstransporttlsd so libssl a libnddstransporttlsz a libcrypto a Static Release libnddstransporttlszd a libnddstransportwanz a Static Debug libnddstransportwanzd a These libraries are in lt NDDSHOME gt lib lt architecture gt These libraries are in openssl install dir gt lt architecture gt lib where openssl install dir is where OpenSSL is i 95 Chapter 10 VxWorks Platforms Table 10 1 Supported VxWorks Target Platforms lists the architectures supported on VxWorks operating systems You can build a VxWorks application by cross compiling from your devel opment host Table 10 1 Supported VxWorks Target Platforms PPC 603 gcc 2 96 ppc603 Vx5 5gcc PPC 604 gcc 2 96 ppc604Vx5 5gcc VxWorks 5 5 PPC 750 gcc 2 96 ppc603 Vx5 5gcc PPC 7400 gcc 2 96 ppc603 Vx5 5gcc For kernel modules VxWorks 6 3 ppc604V x6 3gcc3 4 4 6 4 For Real Time Processes ppc604V x6 3gcc3 4 4 rtp Any PowerPC CPU with floating
159. using JDK 5 0 and want to use Intel s HyperThreading technology use JDK 5 0 Update 6 build 1 5 0_06 which includes fixes to JNI and HyperThreading If you must use Update 5 build 1 5 0 05 you should disable HyperThreading Windows XP does not support IP TOS unless registry changes are made See http support microsoft com kb 248611 http Awww microsoft com technet technetmag issues 2007 02 CableGuy default aspx 127 Chapter 11 Windows Platforms Table 11 4 Running Instructions for Windows Architectures provides details on the environment variables that must be set at run time for a Windows architecture For details on how the libraries were built by RTI see Table 11 5 Library Creation Details for Windows Architectures This information is provided strictly for informational purposes you do not need to use these parameters to compile your application You may find this information useful if you are involved in any in depth debugging Table 11 2 Building Instructions for Windows Host Architectures Library Format Static Release Static Debug Dynamic Release RTI Libraries or Jar Files E Libraries nddscz lib nddscorez lib rticonnextmsgcz lib nddsczd lib nddscorezd lib rticonnextmsgczd lib netapi32 lib advapi32 lib nddsc lib user32 lib ws2_32 lib nddscore lib rticonnextmsgc lib nddscd lib nddscored lib rticonnextmsgcd lib Required System Required Compiler Flags D RTI WIN32 MT
160. ve defined the NDDSHOME environment variable SNDDSHOME bin rtiddsgen lt path to examples gt 1 1 Paths Mentioned in Documentation By default examples are copied into your home directory the first time you run RTI Launcher or any script in lt NDDSHOME gt bin This document refers to the location of the copied examples as lt path to examples gt Wherever you see lt path to examples gt replace it with the appropriate path Default path to the examples e Mac OS X systems Users your user name rti_workspace 5 2 0 examples e UNIX based systems home your user name rti_workspace 5 2 0 examples e Windows systems your Windows documents folder rti_workspace 5 2 0 examples Where your Windows documents folder depends on your version of Windows For example on Windows 7 the folder is CAUsersiyour user name Documents on Windows Server 2003 the folder is C Documents and Settings your user name Documents Note You can specify a different location for rti workspace You can also specify that you do not want the examples copied to the workspace Chapter 2 AIX Platforms Table 2 1 Supported AIX Target Platforms lists the architectures supported on the IBM AIX oper ating system Table 2 1 Supported AIX Target Platforms Operating System EA RTI Mn AE Abbreviation AIX 5 3 POWERS 64 bit POWERS 64 bit mode BM XLC for AIX v9 0 64p5AIX5 3xlc9 0 BM xIC r for AIX v12 1 POWER7 32 bit mode p7AIX7 1xlc12 1 BM Java 1
161. within the same address space to communicate over shared memory with other DomainParticipants To allow more DomainParticipants to run within the same address space we reduced the default size of the queue for each receive resource of the shared memory transport The queue size is reduced to eight messages the default for other platforms is 32 This change only applies to INTEGRITY architectures and this default value can be overwritten through the shared memory transport QoS 4 14 2 Using Shared Memory on INTEGRITY Systems Connext DDS uses the single address space POSIX library to implement the shared memory transport on INTEGRITY 10 0 operating systems To use shared memory you must configure your system to include the POSIX shared memory library The posix shm manager must be running in an AddressSpace solely dedicated to it After building any Connext DDS application that uses shared memory you must use the intex utility provided with the INTEGRITY development environment to pack the application with multiple address spaces one or more to contain the Connext DDS application s and another one to contain the posix shm manager Connext DDS will run on a target without the posix shm manager but the POSIX functions will fail and return ENOSYS and the participants will fail to communicate through shared memory To include the POSIX Shared Memory Manager in its own Address Space The project files generated by rtiddsgen for MULTI will
162. x 3 PPC 85xx gce 4 3 2 ppc85xxWRLinux2 6gcc4 3 2 Yellow Dog Linux 4 0 PPC 74xx such as 400Linux2 3 3 3 2 6 kernel 7410 ppc7400Linux2 6gcc Table 5 4 Building Instructions for Linux Architectures lists the compiler flags and libraries you will need to link into your application See also e Libraries Required for Using Distributed Logger Section 5 7 on page 52 e Libraries Required for Using Monitoring Section 5 8 on page 53 41 Chapter 5 Linux Platforms e Libraries Required for Using RTI Secure WAN Transport APIs Section 5 9 on page 53 e Libraries Required for Using RTI TCP Transport APIs Section 5 10 on page 54 Make sure you are consistent in your use of static dynamic debug and release versions of the libraries Do not link both static and dynamic libraries Similarly do not mix release and debug libraries Table 5 4 Building Instructions for Linux Architectures API C Traditional and Modern APIs Library Format Static Release Static Debug Required RTI Libraries or Jar Files bc libnddscppz a or libnddscpp2z a libnddscz a libnddscorez a librticonnextmsgcz a libnddscppzd a or libnddscpp2zd a libnddsczd a libnddscorezd a librticonnextmsgcppzd a libnddscpp so or libnddscpp2 so libnddsc so libnddscore so librticonnextmsgcpp so libnddscppd so or libnddscpp2d so libnddscd so libnddscored so librticonnextmsgcppd so Required System Libraries Al Linux2 6gcc
163. xOS Architectures Library Format Required RTI Libraries ed libnddscz a Static Release libnddscorez a librticonnextmsgcz a libnddsczd a Static Debug libnddscorezd a librticonnextms gezd a libnddsc so Dynamic Release libnddscore so librticonnextmsgc so libnddscd so Dynamic Debug libnddscored so librticonnextms gced so Table 6 3 Building Instructions for LynxOS Architectures Required System RTI Architecture prados Required Compiler Flags 186Lynx4 0 0gcc3 2 2 ppc7400Lynx4 0 0gcc3 2 2 C and ci E mth C Traditional and Modern ppc7400Lynx4 2 0gcc3 2 2 Idb Im Irpc lc Ilynx eee mshared APIs ppc7400Lynx5 0 0gcc3 4 3 m 2 2 4D ynamic libraries are not supported under LynxOS 178 PChoose libnddscpp for the Traditional C API or libnddscpp2 for the Modern C API The RTI C C libraries are in NDDSHOME lib lt architecture gt where S NDDSHOME is where Connext DDS is installed see Paths Mentioned in Documentation Section 1 1 on page 3 dThe rticonnextmsg library only applies if you have the RTI Connext DDS Professional Evaluation or Basic package type It is not provided with the RTI Connext DDS Core package type 58 Chapter 6 LynxOS Platforms Table 6 4 Running Instructions for LynxOS Architectures Library Format RTI Architecture Release amp Required Environment Variables Debug All supported LynxOS architectures D LD LIBRARY PATH NDDSHOME lb archi

My Document - Community RTI Connext Users

Contents

Download Pdf Manuals

Related Search

Related Contents