Home

Platform Notes - Community RTI Connext Users

1. 4 Supported transports 1 Monotonic clock support Thread configuration 1 Durable Writer History and Durable Reader State features support Table 1 2 lists additional target libraries available with Connext 5 1 0 for which RTI offers custom support If you are interested in using one of these platforms please contact your local RTI rep resentative or email sales rti com These custom platforms are not described in this document each has separate documentation that is provided with the custom library distribution Custom Supported Platforms Operating System CPU Compiler EY A e INTEGRITY 5 0 11 PPC8349 GHnet2 TCP IP stack ppc8349Inty5 0 11 mds8349 2 AIX Platforms Table 1 2 Custom Supported Platforms RTI Architecture Operating System CPU Compiler Abbreviation NI Linux Real Time armv7AngstromLinux3 2 3 28 gce 441 gcc4 4 1 cortex a9 gcc 4 2 1 i86Linux2 6gcc4 2 1 d an Don eed x86 Java Platform Stan pa 2 2 dard Edition JDK 1 7 i86Linux2 6gcc4 2 1jdk 5 Red Hat Enterprise A e A POWER7 gcc 444 power7Linux2 6gcc4 4 4 2 6 32 70 el ppc64 RedHawk Linux 6 0 x64 gcc 4 4 5 x64Linux2 6gcc4 4 5 a Pentium class gcc 4 3 2 i86WRLinux2 6gcc4 3 2 Any PowerPC CPU For Kernel Modules g with floating point Ppc604Vx6 7gcc4 1 2jdk 8 hardware that is back Jamaica VM 6 2 1 with z wards compatible
2. UDPv4 Supported and enabled by default UDPv6 Supported on VxWorks 6 7 and higher architectures except as noted below No Traffic Class support Not supported on mips32r2sfbeVx6 9gcc4 3 3 mips32r2sfbeVx6 9gcc4 3 3 rtp ppce500v2Vx6 9gcc4 3 3 and ppce500v2Vx6 9gcc4 3 3_rtp platforms TCP IPv4 Not supported How to Run Connext Libraries in Kernels Built without Shared Memory Since Connext 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 libraries 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 49 VxWorks Platforms 9 7 9 8 9 8 1 Table 9 3 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 configuration you will need to do the following 1 Add the component INCLUDE_POSIX_SEM 2 Define stubs that return failure for the missing symbols sdOpen and sdUnmap as described below 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 distribution For sdUnmap we recomme
3. 2 CLUDE NET SETUP INCLUDE TIME MONITOR INIT 2 CLUDE NET SYM TBL INCLUDE UDP 2 CLUDE NET TASK INCLUDE USER APPL 2 CLUDE NETDEV CONFIG INCLUDE USR DEVSPLIT NCLUDE NETDEV NAMEGET INCLUDE USR FS UTILS NCLUDE NETINET IF INCLUDE WDB I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I NCLUDE NETINET IF ETHER INCLUDE WDB COMM END a Install partition socket driver v1 3 Follow instructions from Wind River for the installation Required Kernel Components for simpcVx653 2 3gcc3 3 29 INCLUDE ARINC SCHEDULER INIT INCLUDE NETINET IN PCB INCLUDE ARP API INCLUDE BOOT LINE INCLUDE NETINET IN PROTO INCLUDE NETINET IP ICMP INCLUDE BOOT LINE INIT INCLUDE NETINET IP INPUT 62 VxWorks Platforms Table 9 11 Required Kernel Components for simpcVx653 2 3gcc3 3 29 INCLUDE BSD SOCKET INCLUDE NETINET IP OUTPUT INCLUDE BSP MODULES INCLUDE NETINET RADIX INCLUDE BSP VXWORKS INCLUDE NETINET RAW IP INCLUDE DEBUG CORE INCLUDE NETINET ROUTE INCLUDE DEBUG UTIL INCLUDE NETINET SYS SOCKET INCLUDE END INCLUDE NETINET UDP USRREQ INCLUDE END BOOT INCLUDE NETINET UIPC DOM INCLUDE INCLUDE NETINET UIPC MBUF INCLU
4. DVXWORKS MINOR VERSION 8 DPtrIntType long DCSREAL IS FLOAT Wp MD 56 VxWorks Platforms 99 Library Creation Details for All VxWorks Architectures RTI Architecture HUAN Compiler Flags Used by RTI ccpentium m32 march pentium fno builtin ansi DCPU PENTIUM Static or DTOOL_FAMILY gnu DTOOL gnu D WRS KERNEL D__PROTOTYPE_5_0 O Dynamic DVXWORKS_MAJOR_VERSION 6 DVXWORKS_MINOR_VERSION 9 Wall Release Wno unknown pragmas DRTS_VXWORKS DPtrIntIype long DCSREAL IS FLOAT DNDEBUG Wp MD pentiumVx6 9gcc4 3 3 ccpentium m32 march pentium fno builtin ansi DCPU PENTIUM Static or DTOOL FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 g Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION Wall Debug Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU PENTIUM Wp MD ccpentium m32 march pentium ansi DCPU PENTIUM DTOOL FAMILY gnu Static or DTOOL gnu mrtp D__ PROTOTYPE 5 0 O Wall Wno unknown pragmas Dynamic DRTS_VXWORKS DVXWORKS MAJOR VERSION 6 Release DVXWORKS MINOR VERSION DPtrIntType long DCSREAL 15 FLOAT DNDEBUG Wp MD pentiumVx6 9gcc4 3 3 rtp ccpentium m32 march pentium ansi DCPU PENTIUM DTOOL FAMILY gnu Static or DTOOL gnu mrtp D__ PROTOTYPE 5 0 g Wall Wno unknown pragmas Dynamic DRTS VXWORKS DVXWORKS MAJOR VERSION 6 Debug DVXWORKS MINOR VERSION DPtrIntType long DCSRE
5. DWIN32 LEAN AND MEAN O2 Zi MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 x64Win64VS2010 Dynamic DTARGET x64Win64VS2010 DWIN32 D WINDOWS Release D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Note linker O2 Zi MD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c requires W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 MACHINE X64 Static DTARGET x64Win64VS2010 DWIN32 D WINDOWS option Debug 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 Dynamic DTARGET x64Win64VS2010 DWIN32 D WINDOWS Debug D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c 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 Static Release Static Debug nddstransportwanz lib nddstransporttlsz lib nddstransportwanzd lib nddstransporttlszd lib ssleay32 lib libeay32 lib a These libraries are located in wan install dir gt lib lt architecture gt where wan install dir is where RTI Secure WAN Transport is installed such as c rti ndds 5 x y b These libr
6. Debug D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MTd EHsc RTC1 D CRT SECURE NO DEPRECATE c DPtrIntType long DCSREAL 15 FLOAT DCPU I80586 Dynamic DTARGE T i86Win32VS2010 DWIN32 D WINDOWS Debug D WIN32 WINNT 20x0501 DWIN232 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c Dvnamic O2 GL D WIN64 D NDEBUG D NDDS DLL VARIABLE y D WINDLL D UNICODF D UNICODF FD EHa MD c Zi Release x64Win64dotnet2 0 clr TP x64Win64dotnet4 0 Od D WIN64 D DEBUG D NDDS DLL VARIABLE Dynamic WINDLL D UNICODE D UNICODE FD EHa MDd c Zi Debug clr TP Dynamic target 1 4 source 1 6 Release x64Win64jdk target 1 4 source 1 6 g W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 Static DTARGET x64Win64VS2005 DWIN32 D WINDOWS Release D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN C2 Zi MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 x64Win64VS2005 Dynamic DTARGET x64Win64VS2005 DWIN32 D WINDOWS Release D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MD ED EHsc D CRT SECURE NO DEPRECATE DNDEBUG c requires W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 MACHINE X64 Static DTARGET x64Win64VS2005 DWIN32 D WINDOWS option Debug 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 DCP
7. Java Release nddsjava jar For Connext Messaging also include rticonnextmsg jar Debug nddsjavad jar For Connext Messaging also include rticonnextmsgd jar N A N A a The RTI C C libraries are located in NDDSHOME lib lt architecture gt The RTI Java libraries are located in NDDSHOME class where NDDSHOME is where Connext is installed such as c rti ndds 5 x y 72 Windows Platforms Table 10 6 Building Instructions for Windows Target Architectures Libra Required API ry RTI Libraries or Jar Files System Required Compiler Flags Format Libraries nddscz lib 7 Static nddscorez lib Gd MT D WIN32 D RTI WIN32 Release For Connext Messaging also include D NDEBUG rticonnextmsgcz lib nddsczd lib Static nddscorezd lib Gd MTd D WIN32 Debug For Connext Messaging also include netapi32 lib D RTI WINS2 rticonnextmsgczd lib advapi32 lib nddsc lib user32lib MD D WIN32 Dynamic nddscore lib ws2 32ib jp NDDS_DLL_VARIABLE Release For Connext Messaging also include D RTI WINS2 rticonnextmsgc lib D NDEBUG n Gd MDd D WIN32 ic nddscored lib PY D NDDS_DLL_VARIABLE Debug For Connext Messaging also include D RTI WIN32 rticonnextmsgcd lib nddscppz lib nddscz lib Gd EHsc MT D WIN32 dh nddscorez lib D RT
8. RITY documentation 1 If you are already using shared memory through the POSIX library there may be a possi ble conflict INTEGRITY 5 has two different types of POSIX library a single address space one or light and another one complete POSIX implementation Connext uses the first one but will work if you are using the complete POSIX implementation 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 grace fully or ungracefully any new application on the same domain index within the same 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 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 Con next The error message is benign and will not prevent the remaining applications from commu nicating 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 Using rtiddsping and rtiddsspy
9. X Java Platform Standard Edition JDK 1 7 i86Linux3 xgcc4 6 3jdk Ubuntu Server 12 04 LTS e gcc 4 6 3 x64Linux3 xgcc4 6 3 Java Platform Standard Edition JDK 1 7 x64Linux3 xgcc4 6 3jdk Wind River Linux 4 2 6 kernel x64 gcc 4 4 1 x64WRLinux2 6gcc4 4 1 a Reguires a custom version of gcc 4 5 1 Table 44 Linux Platforms on PowerPC CPUs RTI Architecture Operating System CPU Compiler Abbreviation Freescale P2020RDB Freescale gcc 4 3 74 based 2 6 32 kernel 85 on gcc 4 32 ppc85xxLinux2 6gcc4 3 2 SELinux 2 6 32 kernel PPC 4xxFP gcc 4 5 1 glibc 2 9 ppc4xxFPLinux2 6gcc4 5 1 Wind River Linux 3 PPC 85xx gcc 4 3 2 ppc85xxWRLinux2 6gcc4 3 2 Yellow Dog Linux 4 0 PPC 74xx such 2 6 kernel as 7410 gcc 3 3 3 ppc7400Linux2 6gcc3 3 3 Table 4 5 lists the compiler flags and libraries you will need to link into your application See also Monotonic Clock Support Section 4 3 Table 4 6 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 jdk use the d64 flag on the command line Table 4 7 provides details on how the Linux libraries were built This table is provided strictly for informational purposes you do not need to use these parameters to compile your applica tion You may find this information useful if you are involved in any in depth debugging Table 4 8 through Table 4 10 list additional libraries reguired when u
10. libnddscorez a For Connext Messaging also include librticonnextmsgcppz a Static Debug libnddscppzd a libnddsczd a libnddscorezd a For Connext Messaging also include librticonnextmsgcppzd a ldl Insl Im pthread Dynamic Release libnddscpp so libnddsc so libnddscore so For Connext Messaging also include librticonnextmsgcpp so Dynamic Debug libnddscppd so libnddscd so libnddscored so For Connext Messaging also include librticonnextmsgcppd so ldl Insl Im pthread brtl DRTI AIX DRTI UNIX q 32164 glongdouble Static Release libnddscz a libnddscorez a For Connext Messaging also include librticonnextmsgcz a Static Debug libnddsczd a libnddscorezd a For Connext Messaging also include librticonnextmsgczd a ldl Insl Im pthread Dynamic Release libnddsc so libnddscore so For Connext Messaging also include librticonnextmsgc so Dynamic Debug libnddscd so libnddscored so For Connext Messaging also include librticonnextmsgcd so ldl Insl Im pthread brtl DRTI AIX DRTI UNIX q 32164 qlongdouble qthreaded d Java Release nddsjava jar For Connext Messaging also include rticonnextmsg jar Debug nddsjavad jar For Connext Messaging also include rticonnextmsgd jar N A N A a The Connext C C libraries are located NDDSHOME lib lt architecture gt whe
11. route add command The spe cific 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 architec tures the multicast loopback implementation ignores the group address when receiving mes sages This causes Connext 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 domain both lis tening for discovery traffic over multicast they will discover each other regardless of the multi cast address to which they are listening The correct behavior would be to receive messages only for the addresses to which the current process not the host is subscribed Supported Transports Shared memory Supported and enabled by default UDPv4 Supported and enabled by default UDPv6 Not supported TCP IPv4 Not supported 29 LynxOS Platforms 5 2 1 5 3 5 4 5 5 5 5 1 Table 5 6 Shared Memory Support To see a list of shared memory resources in use use the ipcs command To clean up shared memory and shared semaphore resources use the ipcrm command The shared memory keys used by Connext are in the range of 0x400000 For example i
12. 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 DVD or if you have upgraded your system through the distribution s update site 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 Note Make sure the environment variable LD ASSUME KERNEL is either not defined at all or is set to 2 4 20 or higher The middleware will not run if it is set to less than 2 4 20 1 1 The dynamic loader ld is configured by default to load the NPTL library as long as LD ASSUME KERNEL is NOT defined Linux and Fedora Platforms 4 4 2 4 5 4 6 4 7 Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Section 19 5 in the RTI Core Libraries and Utilities User s Manual is available on all supported Linux SUSE and Fedora platforms Note The API for controlling CPU core affinity may change in future releases Durable Writer History and Durable Reader State Features To use the Durable Writer History and Durable Reader State features you must install a rela tional database such as MySQL In principle you can use any database that provides an ODBC driver since ODBC is a standard How ever not all ODBC datab
13. 0x400000 For example ipcs m grep 0x004 The shared semaphore keys used by Connext 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 Monotonic Clock Support The monotonic clock described in Section 8 6 in the RTI Core Libraries and Utilities User s Manual is supported on platforms with all Linux 2 6 kernel or higher Thread Configuration Table 4 11 lists the thread settings for Linux and Fedora platforms Table 4 12 and Table 4 13 list the thread priority definitions and thread kinds respectively Native POSIX Thread Library NPTL Requirements This section applies only to these platforms Red Hat Enterprise Linux 4 0 i86Linux2 6gcc3 4 3 x64Linux2 6gcc3 4 5 L 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 When you build the application you must have the development NPTL library installed in usr lib nptl This library is not installed by default 1 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 If NPTL is not installed
14. 29 Table 9 11 NCLUDE FTP INCLUDE NETINET UIPC MBUF NCLUDE HOST TBL INCLUDE NETINET UIPC SOCK NCLUDE ICMP INCLUDE NETINET UIPC SOCK2 2 CLUDE IGMP INCLUDE NETINET UNIXLIB 2 CLUDE IO EXTRA INIT INCLUDE NETMASK GET 2 CLUDE IO SYSTEM INIT INCLUDE NETWORK 2 CLUDE IP INCLUDE NETWRS ETHERMULTILIB 2 CLUDE KERNEL BASIC INCLUDE NETWRS IFLIB 2 CLUDE KERNEL BASIC INIT INCLUDE NETWRS INETLIB 2 CLUDE KERNEL BASIC INIT2 INCLUDE NETWRS NETBUFLIB 2 CLUDE KERNEL CORE NCLUDE NETWRS REMLIB 2 CLUDE KERNEL FULL NCLUDE NETWRS ROUTELIB 2 CLUDE KERNEL NORMAL MODE NCLUDE NETWRS XDR 2 CLUDE KERNEL SHOW NCLUDE NV RAM 2 CLUDE KERNEL UTIL mt NCLUDE PARTITION INIT 2 CLUDE LOADER INCLUDE POST KERNEL CORE INIT 2 CLUDE LOADER EXTRA INCLUDE POST KERNEL CORE INIT2 2 CLUDE LOOPBACK INCLUDE PPCDECTIMER 2 CLUDE MIILIB INCLUDE PRE KERNEL CORE INIT 2 CLUDE MMU BASIC INCLUDE SERIAL 2 CLUDE_MOTTSECEND INCLUDE_SHELL 2 CLUDE MUX INCLUDE SHELL VI MODE 2 CLUDE NET DRV INCLUDE SOCKET DEV 2 CLUDE NET HOST SETUP INCLUDE SYM TBL INIT 2 CLUDE NET INIT INCLUDE SYSCLK 2 CLUDE NET LIB INCLUDE SYSTEM START INIT 2 CLUDE NET RANDOM INCLUDE TCP 2 CLUDE NET REM IO INCLUDE TFIP CLIENT
15. 6 kernel Freescale P2020RDB 2 6 32 kernel Linux SELinux 2 6 32 kernel PowerPC Table 4 4 on page 17 CPU Wind River Linux 3 Yellow Dog Linux 4 0 LynxOSG LynxOS 4 0 4 2 5 0 Table 5 1 on page 26 Mac OS Mac OS X 10 8 Table 6 1 on page 31 QNX QNX Neutrino 6 4 1 6 5 Table 7 1 on page 35 Solaris Solaris 2 9 2 10 Table 8 1 on page 40 Supported Platforms Table 1 1 Table 1 2 Platforms Available with Release 5 1 0 Operating System Reference VxWorks VxWorks 5 5 6 3 6 9 VxWorks 653 2 3 VxWorks MILS 2 1 1 Table 9 1 on page 46 Windows Windows 7 32 bit and 64 bit Editions Windows 8 32 bit and 64 bit Editions Windows Server 2003 32 bit and 64 bit Editions Windows Server 2008 R2 64 bit Edition Windows Server 2012 R2 64 bit Edition Windows Vista 32 bit and 64 bit Editions Windows XP Professional SP2 32 bit and 64 bit Editions Table 10 1 on page 64 a The Java API is not supported on LynxOS platforms in 5 1 0 If your application requires support for Java on LynxOS please contact your RTI account manager For each platform this document provides information on 1 Supported operating systems and compilers E Required Connext and system libraries LI Required compiler and linker flags I Required environment variables for running the application if any Details on how the Connext libraries were built Multicast support
16. D WIN32 Debug nddscd lib D NDDS DLL VARIABLE nddscored lib D RTI WIN32 nddsjava jar Release For Connext Messaging also include rticonnextmsg jar Java N A N A nddsjavad jar Debug For Connext Messaging also include rticonnextmsgd jar a The RTI C C libraries are located in NDDSHOME XIibX lt architecture gt NX The RTI Java libraries are located in NDDSHOME class where NDDSHOME is where Connext is installed such as c rti ndds 5 x y Table 10 7 Running Instructions for Windows Architectures RTI Architecture Library Format Environment Variables All supported Windows N A Path 2eNDDSHOMEPE MlibN architecture Path architectures for Java Static Release and None required All other supported Debug Windows architectures i Rd Release and 5 o NDDSHOME9oNlibN architecture a Y NDDSHOME represents the root directory of your Connext installation Path represents the value of the Path variable prior to changing it to support Connext 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 74 Windows Platforms Table 10 8 Library Creation Details for Windows Host Architectures RTI Libra Architecture Format
17. Dynamic libnddscore so All other Linux For Connext Messaging also include architectures librticonnextmsgc so ldl Insl Im libnddscd so Dynamic libnddscored so Debug For Connext Messaging also include librticonnextmsgcd so nddsjava jar Release For Connext Messaging also include rticonnextmsg jar N A N ed one require Java nddsjavad jar 1 Debug For Connext Messaging also include rticonnextmsgd jar a RTI C C libraries are in NDDSHOME lib lt architecture gt RTI Java files are in NDDSHOME class where NDDSHOME is where Connext is installed such as local rti ndds 5 x y 20 Linux and Fedora Platforms Table 46 Running Instructions for Linux and Fedora Architectures RTI Architecture Library Format Environment Variables LD LIBRARY PATH NDDSHOME lib architecture All supported Linux LD LIBRARY PATH SUSE Fedora archi N A tectures for Java Note For all 64 bit Java architectures 64Linux jdk use d64 in the command line Static Release amp All other supported Debug None required Linux SUSE Fedora architectures Dynamic Release LD LIBRARY PATH NDDSHOME lib architecture amp Debug 10 LIBRARY PATH a NDDSHOME represents the root directory of your Connext installation LD LIBRARY PATH represents the value of the LD_LIBRARY_PATH variable prior to changing it to support Co
18. FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc3 4 5 fmessage length 0 c Wp MD x64Linux2 6gcc4 1 1 Release m64 fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 1 1 DNDEBUG c Wp MD Debug m64 fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET V x64Linux2 6gcc4 1 1 V fmessage length 0 c Wp MD x64Linux2 6gcc4 1 2 Release m64 fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 1 2 DNDEBUG c Wp MD Debug m64 fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET V x64Linux2 6gcc4 1 2 V fmessage length 0 c Wp MD x64Linux2 6gcc4 3 4 x64Linux2 6gcc4 4 4 Release m64 fPIC DLINUX O Wall Wno unknown pragmas DRTS_UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcec c Wp MD Debug Release m64 fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 3 4 c Wp MD m64 fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 4 4 DNDEBUG c Wp MD Debug m64 fPIC DLINUX g Wall Wno unknown pra
19. Flags Used by RTI ccmips G 0 mno branch likely mips32r2 mgp32 mfp32 EB msoft float Static DCPU MIPSI32R2 DTOOL FAMILY gnu DTOOL sfgnu mlong calls Dynamic D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 Release DVXWORKS MINOR VERSION Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD mips32r2sfbeVx6 9gcc4 3 3 ccmips 0 mno branch likely mips32r2 mgp32 mfp32 msoft float Static DCPU MIPSI32R2 DTOOL FAMILY gnu DTOOL sfgnu mlong calls Dynamic D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 Debug DVXWORKS MINOR VERSION Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT Wp MD ccmips G 0 mno branch likely mips32r2 mgp32 mfp32 EB msoft float Static or DRTI_GCC4 DTOOL sfgnu mxgot mlong calls DCPU MIPSI32R2 Dynamic DTOOL_FAMILY gnu mrtp mips32r2 D__PROTOTYPE_5_0 Wall Release Wno unknown pragmas DRTS_VXWORKS DVXWORKS_MAJOR_VERSION 6 DVXWORKS_MINOR_VERSION 9 DPtrIntType long DCSREAL_IS_FLOAT mips32r2sfbeVx6 9gcc4 3 3_ DNDEBUG Wp MD rtp ccmips G 0 mno branch likely mips32r2 mgp32 mfp32 EB msoft float SEO DRTI_GCC4 DTOOL sfgnu mxgot mlong calls DCPU MIPSI32R2 Dynamic DTOOL_FAMILY gnu mrtp mips32r2 D__PROTOTYPE_5_0 g Wall Du Wno unknown pragmas DRTS VXWORKS DVXWORKS MAJOR VERSION 6 5 DVXWORKS MINOR VERSION DPtrIntType long DCSREAL IS FLOAT Wp MD march pentium fn
20. For Connext Messaging also include librticonnextmsgcz a libnddsczd a libnddscorezd a dynamic lpthread Static Debug For Connext Messaging also include Ic single module librticonnextmsgczd a Im DRTI_UNIX libnddsc dylib Ipthread DRTI DARWIN Dynamic libnddscore dylib DRTI DARWIN10 Release For Connext Messaging also include DRTI_64BIT librticonnextmsgc dylib libnddscd dylib Dynamic libnddscored dylib Debug For Connext Messaging also include librticonnextmsgcd dylib nddsjava jar Release For Connext Messaging also include rticonnextmsg jar N A N one reguire Java nddsjavad jar 3 Debug For Connext Messaging also include rticonnextmsgd jar a The Connext C C libraries are located in 0NDDSHOME lib architecture where NDDSHOME is where Connext is installed such as local rti ndds 5 x y Running Instructions for Mac OS Architectures Library RTI Architecture Format Required Environment Variables Release amp Debug Static None required x64Darwin10gcc4 2 1 Da DYLD LIBRARY PATH NDDSHOME lib ynamuc x64Darwin10gcc4 2 1 4 DYLD LIBRARY PATH DYLD LIBRARY PATH NDDSHOME lib E D NA x64Darwinl0gcc4 2 1jdk DYLD LIBRARY PATH a NDDSHOME represents the root directory of your Connext installation DYLD LIBRARY represents the value of the DYLD LIBRARY PATH variable prior to changing it to support Connext When using nddsjava jar
21. Format RTI Architecture Veris Debug Environment Variables Static None required All supported ONX LD LIBRARY PATH architectures Dynamic NDDSHOME lib architecture LD LIBRARY PATH a NDDSHOME represents the root directory of your Connext installation LD LIBRARY PATH represents the value of the LD_LIBRARY_PATH variable prior to changing it to support Connext 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 Table 7 4 Library Creation Details for QNX Architectures Library RTI Architecture dues Compiler Flags Used by RTI Dynamic qcc Vgcc 4 3 3 gcc_ntox86 Y gpp lang c fPIC fexceptions O Wall Wno unknown pragmas DNDEBUG Vgcc 4 3 3 gcc_ntox86 Y gpp lang c fPIC fexceptions g Wall Wno unknown pragmas Release i860NX6 4 1qcc gpp Debug gcc Vgcc 4 4 2 gcc_ntox86 Y gpp m32 march i386 mtune generic fPIC fexceptions DFD SETSIZE 512 O Wall Release Wno unknown pragmas DRTS ONX DPtrIntIype long DCSREAL IS FLOAT DCPU I80586 DTARGET i86QNX6 5qcec_gpp4 4 2 DNDEBUG Vgcc 4 4 2 gcc_ntox86 Y gpp m32 march i386 mtune generic fPIC fexceptions DFD SETSIZE 512 g Wall Debug Wno unknown pragmas DRTS ONX DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86QNX
22. Messaging also include For RTI architectures with ibrticonnextmsgcpp so SMP support for VxWorks 6 7 libnddscppd so and higher also use Mibnddsed so INCLUDE TLS Dynamic libnddscored so Debug For Connext Messaging also include librticonnextmsgcppd so libnddscz a Static libnddscorez a INCLUDE_TIMESTAMP Release For Connext Messaging also include librticonnextmsgez a For VxWorks 6 4 and below libnddsczd a also use Static libnddscorezd a INCLUDE_ZBUF_SOCK INCLUDE_IGMP Debug For Connext Messaging also include librticonnextmsgczd a C For VxWorks 6 3 and higher VXWORKS libnddsc so also use Dynamic libnddscore so INCLUDE_POSIX_CLOCKS Release For Connext Messaging also include librticonnextmsgc so For RTI architectures with libnddscd so SMP support for VxWorks 6 7 Dynamic libnddscored so and higher also use Debug Connext Messaging also include INCLUDE_TLS librticonnextmsgcd so a The Connext C C libraries are located in NDDSHOME lib lt architecture gt where NDDSHOME is where Connext is installed such as c rti ndds 5 x y b In this version only ppc604Vx6 7gcc4 1 2 smp 52 VxWorks Platforms Table 9 7 Building Instructions for VxWorks 653 Architectures Library Required Required AP Format Reged Kernel Components Compiler Flags libnddscppz a Bd libnddscz a i libnddscorez a For Connext Messagin
23. SECURE NO DEPRECATE DNDEBUG c DPtrIntType long DCSREAL 15 FLOAT DCPU I80586 Dynamic DTARGET i86Win32VS2008 DWIN32 D WINDOWS Release D WIN32 WINNTZ20x0501 DWIN32 LEAN AND MEAN O2 Zi MD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c i86Win32VS2008 DPtrIntType long DCSREAL IS FLOAT DCPU I80586 Static DTARGET i86Win32VS2008 DWIN32 D WINDOWS Debug D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MTd EHsc RTC1 D CRT SECURE NO DEPRECATE c DPtrIntType long DCSREAL 15 FLOAT DCPU I80586 Dynamic DTARGE T i86Win32VS2008 DWIN32 D WINDOWS Debug D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c 75 Windows Platforms Table 10 8 Library Creation Details for Windows Host Architectures RTI Libra Architecture Format Compiler Flags Used by RTI DPtrIntType long DCSREAL 15 FLOAT DCPU I80586 Static DTARGET i86Win32VS2010 DWIN32 D WINDOWS Release D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN C2 Zi MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c DPtrIntType long DCSREAL 15 FLOAT DCPU I80586 Dynamic DTARGET i86Win32VS2010 DWIN32 D WINDOWS Release D WIN32 WINNT20x0501 DWIN32 LEAN AND MEAN O2 Zi MD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c i86Win32VS2010 DPtrIntType long DCSREAL_IS_FLOAT DCPU I80586 Static DTARGET i86Win32VS2010 DWIN32 D WINDOWS
24. Supported on Linux SUSE and Fedora platforms ra 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 Table 4 13 Thread Kinds for Linux and Fedora Platforms 5 Table 5 1 Thread Kinds Operating System Configuration DDS_THREAD_SETTINGS_FLOATING_POINT N A DDS_THREAD_SETTINGS_STDIO N A DDS_THREAD_SETTINGS_REALTIME_PRIORITY Set schedule policy to SCHED_FIFO DDS_THREAD_SETTINGS_PRIORITY_ENFORCE N A a See Linux programmer s manuals for more information LynxOS Platforms Table 5 1 lists the architectures supported on LynxOS operating systems Supported LynxOS Platforms Operating System CPU Compiler RTI Architecture x86 gcc 3 2 2 i86Lynx4 0 0gcc3 2 2 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 22 ppc750Lynx4 0 0gcc3 2 2 LynxOS 42 PPC 74xx such as7410 gcc 3 2 2 ppc7400Lynx4 2 0gcc3 2 2 LynxOS 5 0 PPC 74xx such as 7410 gcc 3 4 3 ppc7400Lynx5 0 0gcc3 4 3 26 LynxOS Platforms Table 5 2 and Table 5 3 list the compiler flags and libraries you will need to link into your appli cation Table 5 4 provides details on the environment variables th
25. XLC reference manual for a description of the different compil ers For a list of the additional settings defined by default for the XIC compiler see the file etc vac cfg 53 AIX Platforms 2 1 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 online documentation for more information 2 2 Supported Transports Shared memory Supported and enabled by default UDPv4 Supported and enabled by default UDPv6 Not supported TCP IPv4 Not supported 2 2 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 applications to work properly over shared memory To increase the maximum number of shared memory segments an application can use set the fol lowing environment variable before invoking your Connext 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 ipcs command To clean up shared memory and shared semaphore resources please use the ipcrm command The shared memory keys used by Connext are in the range of 0x400000 For example ipcs m grep 0x004 The shared semaphore keys used by Connext are in the range of 0x800
26. more information on database setup please see the Addendum for Database Setup 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 trans port properties for the Connext applications running on the PPP server machine must be config ured with multicast 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 const int num_bad_interfaces sizeof bad_interfaces sizeof bad_interfaces 0 UDPv4Properties parent deny multicast interfaces list bad interfaces UDPv4Properties parent deny multicast interfaces list length num bad interfaces Failure to do so will result in Connext being unable to send any data at all over the PPP link Notes 1 Setting up multicast related socket options for the PPP interface can prevent future uni cast sends using that socket from working 21 Connext 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 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 packag
27. on PowerPC INTEGRITY Systems While the RTI libraries for INTEGRITY can be used with any BSP providing the PowerPC pro cessor 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 dependent You will not be able to run them successfully on your target if it is not compatible with the BSP listed in the architecture name such as mvme5100 7400 Please refer to your hardware documentation for peripheral compatibility across BSPs Monotonic Clock Support The monotonic clock described in Section 8 6 in the RTI Core Libraries and Utilities User s Manual is not supported Thread Configuration Table 3 5 lists the thread settings for INTEGRITY platforms Table 3 6 and Table 3 7 list the thread priority definitions Table 3 6 applies to all INTEGRITY platforms except INTEGRITY 10 02 Table 3 7 applies to INTEGRITY 10 02 only INTEGRITY Platforms Table 3 5 Thread Settings for INTEGRITY Platforms Table 3 6 Table 3 7 Applicable Thread DDS ThreadSettings t Platform Specific Setting mask OS default thread type Asynchronous Publisher priority 80 Asynchronous flushing thread stack_size 4 20 1024 ReceiverPool threads cpu list CPU core affinity not supported rotation CPU core affinity not supported mask DDS THREAD SETTINGS STDIO 60 pr
28. resources remove the files listed in dev sem The permissions for the semaphores created by Connext are modified by the process umask value If you want to have shared memory support between different users run the com mand umask 000 to change the default umask value to 0 before running your Connext 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 i8G6ONX6 5gcc_cpp4 4 2 TLS Supported on i86QNX6 5qcc_cpp4 4 2 Monotonic Clock Support The monotonic clock described in Section 8 6 in the RTI Core Libraries and Utilities User s Manual is supported on ONX platforms Thread Configuration Table 7 5 lists the thread settings for ONX platforms Table 7 6 lists the thread priority definitions Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Section 19 5 in the RTI Core Libraries and Utilities User s Manual is not available for ONX platforms Table7 5 Thread Settings for QNX Platforms Applicable Thread DDS ThreadSettings t Platform Specific Setting mask OS default thread type priority OS defa
29. so libnddscd so Dynamic Debug libnddscored so For Connext Messaging also include librticonnextmsgcd so a Dynamic libraries are not supported under LynxOS 178 b The Connext C C libraries are located in NDDSHOME lib lt architecture gt where NDDSHOME is where Connext is installed such as c rti ndds 5 x y 27 LynxOS Platforms Table 5 3 Table 5 4 Table 5 5 Building Instructions for LynxOS Architectures System Libraries and Compiler Flags API RTI Architecture Required System Libraries Required Compiler Flags i86Lynx4 0 0gcc3 2 2 ppc7400Lynx4 0 0gcc3 2 2 AT AGA DRTI LYNX mthreads ppc7400Lynx4 2 0gcc3 2 2 ldb Im Irpc lc llynx md ppc7400Lynx5 0 0gcc3 4 3 ppc750Lynx4 0 0gcc3 2 2 Running Instructions for LynxOS Architectures Library Format RTI Architecture Release amp Debug Required Environment Variables Static None required All supported LynxOS architectures LD LIBRARY PATH NDDSHOME lib architecture Dynamic LD LIBRARY PATH Library Creation Details for LynxOS Architectures RTI Architecture Library Format Static amp Dynamic Compiler Flags Used by RTI i86Lynx4 0 0gcc3 2 2 Release mthreads mshared fPIC D POSIX THREADS CALLS D__ NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntType long DCPU I80586 DTARGET V i86Lynx4 0 0gcc3 2 2 V DNDEB
30. systems in Section 9 4 in the RTI Core Libraries and Utilities User s Manual The following tables provide supplemental information Table 10 1 lists the architectures supported on Windows operating systems Table 10 1 Supported Windows Architectures Operating System CPU Software Dd Kit RTI Architecture Visual Studio 2010 i86Win32VS2010 Windows 7 32 bit Edition x86 Visual Studio 2010 C CLI C 8 0 or 9 0 i86Win32dotnet4 0 Java Platform Standard Edition JDK 1 7 i86Win32jdk Visual Studio 2010 x64Win64VS2010 Windows 7 64 bit Edition x64 Visual Studio 2010 C CLI C 8 0 or 9 0 x64Win64dotnet4 0 Java Platform Standard Edition JDK 1 7 x64Win64jdk Visual Studio 2012 x64Win64VS2012 Windows 8 32 bit Edition x86 Visual Studio 2012 i86Win32dotnet4 5 Java Platform Standard Edition JDK 1 7 x64Win64jdk Visual Studio 2012 x64Win64VS2012 Windows 8 64 bit Edition x64 Visual Studio 2012 x64Win64dotnet4 5 Java Platform Standard Edition JDK 1 7 x64Win64jdk Visual Studio 2005 SP 1 i86Win32VS2005 Visual Studio 2005 SP 1 C CLI C 8 0 or 9 0 i86Win32dotnet2 0 eir HR 2003 x86 Visual Studio 2008 SP1 i86Win32VS2008 Visual Studio 2008 SP 1 C CLI C 8 0 or 9 0 i86Win32dotnet2 0 Java Platform Standard Edition JDK 1 7 i86Win32jdk Visual Studio 2005 SP 1 x64Win64VS2005 Windows Server 2003 Visual Studio 2005 SP 1 C CLI C 8 0 or 9 0 x64Win64dotn
31. 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 33 Mac OS Platforms 64 Library Creation Details for Mac OS Architectures 6 1 6 2 6 3 6 4 6 4 1 Library RTI Architecture Format Compiler Flags Used by RTI Static amp Dynamic O Wall Wno unknown pragmas DRTS_UNIX DPtrIntType long Release DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Darwin10gcc4 2 1 c Wp MD x64Darwin10gcc4 2 1 g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long Debug DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Darwinl0gcc4 2 1V c Wp MD Release target 1 4 source 1 4 x64Darwin10gcc4 2 1jdk Debug target 1 4 source 1 4 g Multicast Support Multicast is supported on Mac OS platforms and is configured out of the box Thatis the default value for the initial peers list NDDS_DISCOVERY_PEERS includes a multicast address See the online documentation for more information Supported Transports Shared memory Supported and enabled by default UDPv4 Supported and enabled by default UDPv6 Not supported TCP IPv4 Not supported Monotonic Clock Support The monotonic clock described in Section 8 6 in the RTI Core Libraries and Utilities User s Man
32. 000 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 2 3 Monotonic Clock Support The monotonic clock described in Section 8 6 in the RTI Core Libraries and Utilities User s Manual is not supported on AIX platforms 2 4 Thread Configuration Table 2 5 lists the thread settings for AIX platforms Table 2 6 lists the thread priority definitions for AIX platforms Table 2 5 Thread Settings for AIX Platforms Applicable Thread DDS ThreadSettings t Platform Specific Setting mask OS default thread type Asynchronous Publisher priority OS default thread priority Asynchronous flushing stack size 4 192 1024 thread cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported AIX Platforms Table 2 5 Thread Settings for AIX Platforms Table 2 6 2 4 1 Table 2 7 Applicable Thread DDS_ThreadSettings_t Platform Specific Setting mask 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 DDS_THREAD_SETTINGS_STDIO mask DDS_THREAD_SETTINGS_FLOATING_POINT priority OS default thread priority D stack size 4 192 1024 cpu list C
33. 4 gcc 3 4 5 x64Linux2 6gcc3 4 5 gcc 4 1 1 i86Linux2 6gcc4 1 1 Red Hat Enterprise Linux 5 0 Java Platform Standard Edition JDK 1 7 i86Linux2 6gcc4 1 1jdk 2 6 kernel gcc 4 1 1 x64Linux2 6gcc4 1 1 _ Java Platform Standard Edition JDK 1 7 x64Linux2 6gcc4 1 1jdk gcc 4 1 2 i86Linux2 6gcc4 1 2 Red Hat Enterprise Linux 5 1 iii Java Platform Standard Edition JDK 1 7 i86Linux2 6gcc4 1 2jdk 52 5 4 5 5 Q 6 kernel gcc 4 1 2 x64Linux2 6gcc4 1 2 a Java Platform Standard Edition JDK 1 7 x64Linux2 6gcc4 1 2jdk Red Hat Enterprise Linux 5 2 gcc 4 1 2 i86Linux2 6gcc4 1 2 with Real Time Extensions 2 6 x86 kernel Java Platform Standard Edition JDK 1 7 i86Linux2 6gcc4 1 2jdk gcc 4 4 5 i86Linux2 6gcc4 4 5 Red Hat Enterprise Linux 6 0 ae Java Platform Standard Edition JDK 1 7 i86Linux2 6gcc4 4 5jdk 6 4 2 6 kernel gcc 4 4 5 x64Linux2 6gcc4 4 5 ib Java Platform Standard Edition JDK 1 7 x64Linux2 6gcc4 4 5jdk SUSE Linux Enterprise Server x64 gcc 4 3 4 x64Linux2 6gcc4 3 4 11 SP2 2 6 kernel Java Platform Standard Edition JDK 1 7 x 4Linux2 6gcc4 3 4jdk SUSE Linux Enterprise Server x86 gcc 4 3 4 i86Linux3gcc4 3 4 11 SP2 3 x kernel Java Platform Standard Edition JDK 1 7 i86Linux3gcc4 3 4jdk 16 Linux and Fedora Platforms Table 43 Linux Platforms on Intel CPUs RTI Architecture Operating System CPU Compiler Abbreviation a gcc 4 6 3 i86Linux3 xgcc4 4 3
34. 4 march x86 64 mtune generic fPIC DLINUX O Wall Release Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DNDEBUG x64WRLinux2 6gcc4 4 1 m64 march x86 64 mtune generic fPIC DLINUX O Wall Debug Wno unknown pragmas DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DNDEBUG Dynamic All supported Linux and c m target 1 4 source 1 4 Fedora architectures for Java D idk ynamic _ _ _ Debug target 1 4 source 1 4 g a The C libnddscpp dynamic libraries were linked using g the C dynamic libraries i e libnddscore and libnddsc were linked using gcc Table 4 8 Additional Libraries for using RTI Secure WAN Transport APIs on UNIX based Systems Library Format RTI Secure WAN Transport Libraries OpenSSL Libraries libnddstransportwan so Dynamic Release y libnddstransporttls so D ic Deb libnddstransportwand so namic Debu B libnddstransporttlsd so libssl so libnddstransporttlsz a libcrypto so Static Release libnddstransporttlszd a libnddstransportwanz a Static Debug libnddstransportwanzd a a The libraries are located in wan install dir lib architecture where wan install dir is where you installed RTI Secure WAN Transport such as local rti ndds 5 x y b These libraries are located lt openssl install dir architecture lib where openssl install dir is where you installed OpenSSL such as
35. 5 Windows XP 64 bit Visual Studio 2005 SP 1 C CLI C 8 0 or 9 0 x64Win64dotnet2 0 Professional Edition SP2 id Visual Studio 2008 SP 1 x64Win64VS2008 Java Platform Standard Edition JDK 1 7 x64Win64jdk a On Windows XP If you are 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 and HyperThreading If you must use Update 5 build 1 5 0 05 you should disable HyperThreading b 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 c Windows XP does not support IP TOS unless registry changes are made See http support microsoft com kb 248611 http www microsoft com technet technetmag issues 2007 02 CableGuy default aspx The compiler flags and the libraries you will need to link into your application are listed in the following tables Windows XP Professional x64 Edition Table 10 6 on page 73 J All other supported Windows platforms Table 10 5 on page 71 See also Libraries Required for Using RTI Secure WAN Transport APIs Section 10 10 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 Win
36. 6 5qcec_gpp4 4 2 i860NX6 5qcc gpp4 4 2 7 1 Required Change for Building with Libraries for Platforms For QNX architectures in Connext 5 0 and higher The C libraries are now built without the A fno rtti flag and with the fexceptions flag To build QNX architectures with Connext 5 0 and higher you must build your C applications without fno exceptions in order to link with the RTI libraries In summary 4 Do not use fno exceptions when building a C application or the build will fail It is not necessary to use fexceptions but doing so will not cause a problem It is no longer necessary to use fno rtti but doing so will not cause a problem 7 2 Multicast Support Multicast is supported on ONX 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 documentation for more information 7 3 Supported Transports Shared Memory Supported and enabled by default To see a list of the shared memory resources enter 1 dev shmem RTIOsapiSharedMemorySegment 37 QNX Platforms 7 4 7 5 7 5 1 To clean up the shared memory resources remove the files listed in dev shmem The shared resource names used by Connext begin with RTIOsapiSharedMemorySem To see a list of shared semaphores enter ls dev sem RTIOsapiSharedMemorySemMutex To clean up the shared semaphore
37. 68 10 7 Thread Contig ira tions rte ier P debet tee rie prp 68 10 8 ODBC Database Compatibility esee eisie e eteri er 69 10 9 PPP Link Support for Windows XP Systems sse eene en nnns 70 10 10 Libraries Required for Using RTI Secure WAN Transport APlIs eee 70 10 11 Libraries Required for Using RTI TCP Transport APlIs sees eee ene 70 Platform Notes Table 1 1 This document provides platform specific instructions on how to compile link and run RTI Connext formerly RTI Data Distribution Service applications Supported Platforms Table 1 1 lists the platforms available with Connext 5 1 0 Platforms Available with Release 5 1 0 Operating System Reference AIX AIX 5 3 7 1 Table 2 1 on page 3 INTEGRITY INTEGRITY 5 0 11 10 0 2 Table 3 1 on page 8 Gee CPU Raspbian Wheezy 7 0 3 x kernel Table 4 1 on page 15 Linux Cell BE Fedora 12 2 6 32 kernel Table 4 2 on page 16 CPU CentOS 5 4 5 5 6 0 6 2 6 4 2 6 kernel Fedora 12 2 6 32 kernel Fedora 12 2 6 32 kernel with gcc 4 5 1 ae Red Hat Enterprise Linux 4 0 5 0 5 2 5 4 5 5 6 0 6 4 2 6 kernel Intel CPU Red Hat Enterprise Linux 5 2 with Real Time Extensions Table 4 3 on page 16 2 6 kernel SUSE Linux Enterprise Server 11 SP2 2 6 and 3 x kernel Ubuntu Server 12 04 LTS 3 x kernel Wind River Linux 4 2
38. 86Linux2 6gcc4 4 5 V Wp MD i86Linux3gcc4 3 4 Release fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Linux3gcc4 3 4 fmessage length 0 DNDEBUG c Wp MD Debug fPIC DLINUX g Wall Wno unknown pragmas DRTS_UNIX DPtrIntType long DCSREAL_IS_FLOAT DCPU I80586 DTARGET i86Linux3gcc4 3 4 fmessage length 0 c Wp MD ppc7400Linux2 6gcc3 3 3 Release fPIC DLINUX O Wall Wno unknown pragmas DRTS_UNIX DPtrIntType long DCSREAL_IS_FLOAT DCPU PPC7400 DTARGET ppc7400Linux2 6g c3 3 3 DNDEBUG c Wp MD Debug fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU PPC7400 DTARGET V ppc7400Linux2 6gcc3 3 3 c Wp MD ppc4xxFPLinux2 6gcc4 3 3 Release fPIC DLINUX O Wall Wno unknown pragmas DRTS_UNIX DPtrIntType long DCSREAL IS FLOAT DCPU 4xxFP DTARGET V ppc4xxFPLinux2 6gcc4 3 3V DNDEBUG c Wp MD Debug fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU 4xxFP DTARGET ppc4xxFPLinux2 6gcc4 3 3 DNDEBUG c Wp MD ppc4xxFPLinux2 6gcc4 5 1 Release fPIC DLINUX O Wall Wno unknown pragmas DRTS_UNIX DPtrIntType long DCSREAL IS FLOAT DCPU 4xxFP DTARGET ppc4xxFPLinux2 6gcc4 5 1 DNDEBUG c Wp MD Debug fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrInt
39. AL IS FLOAT Wp MD mcpu 405 fno builtin mlongcall DTOOL gnu mstrict align msoft float Static or ansi D_WRS_KERNEL D_PROTOTYPE_5_0 DVXWORKS_MAJOR_VERSION 6 Dynamic DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas Release DRTS VXWORKS 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 Static or ansi D WRS KERNEL D PROTOTYPE 5 0 g Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Debug Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL_FAMILY gnu DPtrIntType long DCPU PPC405 c Wp MD msoft float mlongcall mregnames mstrict align ansi DTOOL gnu mrtp Static D_PROTOTYPE_5_0 DVXWORKS_MAJOR_VERSION 6 DVXWORKS MINOR 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 Static shared D PROTOTYPE 5 0 g DVXWORKS_MAJOR_VERSION 6 Debug DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL sfgnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 c Wp MD Static or mcpu 603 G 0 fno builtin mlongcall D_PROTOTYPE_5_0 Dynamic DVXWORKS MAJOR VERSION 5 DVXWORKS MINOR VERSION 5 O Wall Release Wno unknown pragmas DRTS_VXWORKS DPtrIntType long DCSREAL IS FLO
40. AT DCPU PPC603 DNDEBUG c Wp MD ppc603Vx5 5gcc Static or mcpu 603 G 0 fno builtin mlongcall D__PROTOTYPE_5_0 g Dynamic DVXWORKS MAJOR VERSION 5 DVXWORKS MINOR VERSION 5 O Wall Debug Wno unknown pragmas DRTS_VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU PPC603 c Wp MD 57 VxWorks Platforms 99 Library Creation Details for All VxWorks Architectures RTI Architecture Eu Compiler Flags Used by RTI Static or mcpu 604 G 0 fno builtin mlongcall D__PROTOTYPE_5_0 Dynamic DVXWORKS MAJOR VERSION 5 DVXWORKS_MINOR_VERSION 5 O Wall Release Wno unknown pragmas DRTS_VXWORKS DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD ppc604Vx5 5gcc Geo mcpu 604 G 0 fno builtin mlongcall D__ PROTOTYPE 5 0 g Dynamic DVXWORKS MAJOR VERSION 5 DVXWORKS MINOR VERSION 5 O Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCPU PPC604 Debug c Wp MD mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align mno implicit fp Static or ansi D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 3 O Wall Wno unknown pragmas Release DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD ppc604Vx6 3gcc3 4 4 mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align mno implicit fp Static or ansi D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 Dynamic D
41. Compiler Flags Used by RTI Dynamic O2 GL D WIN32 D NDEBUG D NDDS DLL VARIABLE y D WINDLL D UNICODF D UNICODF FD EHa MD c Release i86Win32dotnet2 0 Zi clr TP i86Win32dotnet4 0 5 __ Od D WIN32 D DEBUG D NDDS DLL VARIABLE D WINDLL D UNICODE D UNICODE FD EHa MDd c Zi dr TP Dynamic target 1 4 source 1 4 Release i86Win32jdk cda target 1 4 source 1 4 g DPtrIntType long DCSREAL IS FLOAT DCPU 180586 Static DTARGET i86Win32VS2005 DWIN32 D WINDOWS Release D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MT EHsc D CRT SECURE NO DEPRECATE DNDEBUG c DPtrIntType long DCSREAL 15 FLOAT DCPU I80586 Dynamic DTARGET i86Win32VS2005 DWIN32 D WINDOWS Release D WIN32 WINNTZ20x0501 DWIN32 LEAN AND MEAN O2 Zi MD EHsc D CRT SECURE NO DEPRECATE DNDEBUG c i86Win32VS2005 DPtrIntType long DCSREAL_IS_FLOAT DCPU I80586 Static DTARGET i86Win32VS2005 DWIN32 D_WINDOWS Debug 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 Dynamic DTARGE T i86Win32VS2005 DWIN32 D WINDOWS Debug D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c DPtrIntType long DCSREAL 15 FLOAT DCPU I80586 Static DTARGET i86Win32VS2008 DWIN32 D WINDOWS Release D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MT EHsc D CRT
42. DE HOST TBL INCLUDE NETINET UIPC SOCK INCLUDE ICMP INCLUDE NETINET UIPC SOCK2 INCLUDE IGMP INCLUDE NETINET UNIXLIB INCLUDE IO EXTRA INIT INCLUDE NETMASK GET INCLUDE IO SYSTEM INIT INCLUDE NETWORK INCLUDE IP INCLUDE NETWRS ETHERMULTILIB INCLUDE KERNEL BASIC INCLUDE NETWRS IFLIB INCLUDE KERNEL BASIC INIT INCLUDE NETWRS INETLIB INCLUDE KERNEL BASIC INIT2 INCLUDE NETWRS NETBUFLIB INCLUDE KERNEL CORE INCLUDE NETWRS REMLIB INCLUDE KERNEL FULL INCLUDE NETWRS ROUTELIB INCLUDE KERNEL NORMAL MODE INCLUDE NETWRS XDR INCLUDE LOOPBACK INCLUDE NTEND INCLUDE MUX INCLUDE NTPASSFS INCLUDE NET DRV INCLUDE NULLNVRAM INCLUDE NET HOST SETUP INCLUDE PARTITION INIT INCLUDE NET INIT INCLUDE POST KERNEL CORE INIT INCLUDE NET LIB INCLUDE POST KERNEL CORE INIT2 INCLUDE NET RANDOM INCLUDE PRE KERNEL CORE INIT INCLUDE NET REM IO INCLUDE SIMPCTIMER INCLUDE NET SETUP INCLUDE SOCKET DEV INCLUDE NET TASK INCLUDE SYSTEM START INIT INCLUDE NETDEV CONFIG INCLUDE TCP INCLUDE NETDEV NAMEGET INCLUDE TFIP CLIENT INCLUDE NETINET IF INCLUDE TIME MONITOR INIT INCLUDE NETINET IF ETHER INCLUDE UDP INCLUDE NETINET IF SUBR INCLUDE USER APPL INCLUDE NETINET IGMP INCLUDE WDB INCLUDE NETINET IN INCLUDE WDB COMM END INCLUDE NETINET IN CKSUM INCLUDE WINSIO a Install partition socket driver v1 3 Follow instructions from Wind River for the installation 63 Windows Platforms 10 Windows Platforms First see the basic instructions for compiling on Windows
43. 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 Static D PROTOTYPE 5 0 g DVXWORKS_MAJOR_VERSION 6 Debug DVXWORKS MINOR 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 Static or D WRS KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 7 O Wall Wno unknown pragmas Release DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD ppc604Vx6 7gcc4 1 2 mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align ansi Static or D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 7 O Wall Wno unknown pragmas Debug DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC604 c Wp MD mhard float mlongcall mregnames mstrict align ansi mrtp D PROTOTYPE 5 0 Static DVXWORKS MAJOR VERSION 26 DVXWORKS MINOR VERSION 7 O Wall Release Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 DNDEBUG c Wp MD ppc604Vx6 7gcc4 1 2 rtp ppc604Vx6 7gcc4 1 2_smp mhard float mlongcall mregnames mstrict align ansi mrtp fPIC shared Static D_PROTOTYPE_5_0 g DVXWORKS MAJOR VERSION 6 Debug DVXWORKS MINOR VER
44. E 199506L D EXTENSIONS DSolaris2 DSVR5 and DSUNA SOLARI g O Wall Wno unknown pragmas fPIC Dynamic DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU i386 Debug DTARGET i86S012 9 cc3 3 2 c Wp MD Wp Siac D POSIX C SOURCE 199506L D EXTENSIONS__ DSolaris2 DSVR5 Dynamic DSUN4_SOLARIS2 KPIC O w DRTS_UNIX DPtrIntType long s DCPU SPARC DTARGET V sparcSol2 9cc5 4V DNDEBUG c sparcSol2 9cc5 4 Static POSIX C SOURCE 199506L D EXTENSIONS__ DSolaris2 DSVR5 Dynamic DSUN4_SOLARIS2 KPIC g w DRTS_UNIX DPtrIntType long DCPU SPARC DTARGET sparcSol2 9cc5 4 c ebug Static D_POSIX_C_SOURCE 199506L D EXTEN SION S DSolaris2 DSVR5 and DSUN4_SOLARIS2 O Wall Woverloaded virtual Dynamic Wno unknown pragmas DRTS_UNIX DPtrIntType long DCSREAL IS FLOAT DCPU SPARC DTARGET sparcSol2 10gcc3 4 2 DNDEBUG c Wp MD sparcSol2 10gcc3 4 2 Static D_POSIX_C_SOURCE 199506L D_EXTENSIONS __ DSolaris2 DSVR5 DSUN4_SOLARIS2 g O Wall Woverloaded virtual Dynamic Wno unknown pragmas DRTS_UNIX DPtrIntType long Debug DCSREAL_IS_FLOAT DCPU SPARC DTARGET sparcSol2 10gcc3 4 2 c Wp MD Static m64 fPIC D_POSIX_C_SOURCE 199506L D__EXTENSIONS__ and DSolaris2 DSVR5 DSUN4_SOLARIS2 O Wall Wno unknown pragmas Dynamic DRTS_UNIX DPtrIntType long DCSREAL IS FLOAT DCPU SPARC Release DTARGET sparc64Sol2 10gcc3 4 2 DNDEBUG c Wp MD 45 12 10 3 4 2 E
45. Features sse 44 VxWorks Platforms ue daed ded xe ea ess dues sated epe save Cep dn 46 9 1 Support for Reguest Reply Communication Pattern sss 48 9 2 Increasing th Stack Size eoe e Ree Sue peni quite eee 48 9 3 Libraries for RTP Mode on VxWorks 6 3 and Higher Systems sss 48 9 4 Requirement for Restarting 49 95 Multicast SUpport acorde Pe ee en etae tg drin EC Rr a REN T E EE I ege Euge 49 9 6 Supported Transport heu eee iecore deett eet be en pdt Eee e eed 49 9 7 Monotonic Clock Support noe teda epe diet eerie e tete ier Ded eed 50 9 8 Thread Configuration uo rete d e in bec tihi t EG Y e Ret 50 9 9 Durable Writer History and Durable Reader State Features seen 51 9 10 Increasing the Receive Socket Buffer 512 nennen 51 TO Windows Platforms oed eere meten entes ect enect etin 64 10 1 Use Dynamic MFC Library Not Static sese eee iarsan 67 10 2 Visual Studio 2005 Required when Using RTI Debug Libraries for Java or NET APIs 67 10 3 API Requires Thread Affinity sse ee eee eene nm 67 104 Multicast Support FR eei fet tee eec YY TF RE 68 105 Supported Transports edi eee freie tecti tite e MR ad Od bee ires 68 10 6 Monotonic Clock Support ate te et dte n ilte tee s e rb AD
46. L WIN32 elease NT YB For Connext Messaging also include D NDEBUG rticonnextmsgcppz lib nddscppzd lib nddsczd lib Static hddscorezd lib Gd EHsc MTd D WIN32 Debug D RTI WIN32 For Connext Messaging also include netapi32 lib rticonnextmsgc d lib 132 li 1 gcppza h ARN nddscpp lib user32 5 nddsc lib ws2 32lib Gd EHsc MD D WIN32 Dynamic nddscore lib D NDDS_DLL_VARIABLE Release D RTI WIN32 For Connext Messaging also include D NDEBUG rticonnextmsgcpp lib nddscppd lib 5 nddscd lib Gd EHsc MDd D WIN32 o nddscored lib D NDDS_DLL_VARIABLE n 5 For Connext Messaging also include D RII WIN22 rticonnextmsgcppd lib 73 Windows Platforms Table 10 6 Building Instructions for Windows Target Architectures Required RTI Libraries or Jar Files System Required Compiler Flags Libraries Library API Format nddsdotnet dll or nddsdotnet40 dll Release For Connext Messaging also include rticonnextdotnet dll or rticonnextdotnet40 dll Ci N A N A nddsdotnetd dll or nddsdotnet40d dll Debug For Connext Messaging also include rticonnextdotnetd dll or rticonnextdotnet40d dll Gd EHsc MD D WIN32 D NDDS_DLL_VARIABLE D RTI WIN32 nddscore lib advapi32 lib D NDEBUG CLI user32 lib nddscpp lib Release nddsc lib netapi32 lib nddscppd lib ws2 32 lib Gd EHsc MDd
47. 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 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 ver sion 5 0 4 of this library 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 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 Using Shared Memory on INTEGRITY Systems Connext 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
48. Monoctonic Clock Support eee ertet e ce 34 64 Thread Configuration uote ue eor te t irent iet b en tete ipe iras 34 65 Durable Writer History and Durable Reader State Features sse 35 ONN PlatfOEnis 35 71 Required Change for Building with C Libraries for QNX Platforms sse 37 72 oMulHcastoupport ee 6 ocaeca ita n tette ate dede OLA 37 73 Supported Iransportss s oeste Restat itera tab eene ie i AF Wn 37 74 Monotonic Clock Support tenente nennen nene nennen nnne nenne 38 7 5 Ihread Contiguratioti s c wy WYT EW WE Y eee tenete ne i e pee rere Wych 38 7 6 Durable Writer History and Durable Reader State Features sse 39 7 7 Restarting Applications on QNX Systems sssssssessee eene nene nennen nennen 39 Solatis PlatfOEms i ien eei rie ete 40 8 1 Support for Reguest Reply Communication Pattern sse 42 82 Multicast Supports eee eei eei n te E ices etnies YW WD FY eet PP e SWN 43 8 9 Supported Transports e eec efe te entente en e ete Pete i 43 84 Monotonic Clock Support Iit WDD DF WYAF Uu 44 8 5 Libraries Required for using RTI Secure WAN Transport APIs esses 44 8 6 Thread Configuration DG eh eer eee n ie ee 44 87 Durable Writer History and Durable Reader State
49. N m64 fPIC D POSIX C SOURCE 199506L D EXTENSIONS tanie DSolaris2 DSVR5 DSUN4 SOLARIS2 g O Wall Dynamic Wno unknown pragmas DRTS UNIX DPtrIntType long Debug DCSREAL IS FLOAT DCPU SPARC DTARGET sparc64Sol2 10gcc3 4 2 c Wp MD All supported Solaris target 1 4 source 1 4 architectures for Java pm target 1 4 source 1 4 g a The C libnddscpp dynamic libraries were linked using g the C dynamic libraries i e libnddscore and libnddsc were linked using gcc Support for Request Reply Communication Pattern RTI Connext Messaging includes support for the Request Reply Communication Pattern for all the platforms described in Table 8 1 on page 40 and all programming languages except as noted below When using C the following platforms do not support the Request Reply Communication Pattern 4 sparcSol2 9cc5 4 42 Solaris Platforms Table 85 Additional Libraries for using RTI Secure WAN Transport APIs on UNIX based Systems 8 2 8 3 8 3 1 8 3 2 Library Format RTI Secure WAN Transport Libraries OpenSSL Libraries libnddstransportwan so Dynamic Release libnddstransporttls so mb libnddstransportwand so nam y I libnddstransporttlsd so libssl a libnddstransporttlsz a libcrypto a Static Release libnddstransporttlszd a libnddstransportwanz a Static Debug libnddstransportwanzd a a The libraries are
50. OL gnu mrtp D PROTOTYPE 5 0 g Wall Dynamic Wno 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 Static DTOOL_FAMILY gnu DTOOL gnu D_WRS_KERNEL D__PROTOTYPE_5_0 Release 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 ppc604Vx6 9gcc4 3 3 ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 Static DTOOL_FAMILY gnu DTOOL gnu D WRS KERNEL D__PROTOTYPE_5_0 g Debu DVXWORKS_MAJOR_VERSION 6 DVXWORKS_MINOR_VERSION 9 Wall 8 Wno unknown pragmas DRTS_VXWORKS DPtrIntType long DCSREAL IS FLOAT Wp MD ccppc mhard float mstrict align m32 mregnames ansi mlongcall DCPU PPC32 Static DTOOL FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 O2 Release 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 ppc604Vx6 9gcc4 3 3_rtp ccppc mhard float mstrict align m32 mregnames ansi mlongcall DCPU PPC32 Static DTOOL_FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 g Wall Debug Wno unknown pragmas DRTS VXWORKS DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION DPtrIntType long DCSREAL IS FLOAT Wp MD Static or fno zero initi
51. PU core affinity not supported cpu rotation CPU core affinity not supported ReceiverPool threads DDS THREAD SETTINGS STDIO HER DDS THREAD SETTINGS FLOATING POINT priority OS default thread priority stack size 4 192 1024 cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported 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 Changing Thread Priority Due to the AIX threading model implementation there are situations that require you to run your Connext application with root privileges 1 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 DomainParticipantOos receiver _pool thread 1 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_DomainParticipantQos receiver_pool thread Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described i
52. PU with TI ppc604Vx6 8gcc4 1 2 floating point hardware For Real Time Processes ppc604Vx6 8gcc4 1 2_rtp For Kernel Modules pentiumVx6 9gcc4 3 3 Pentium32 bit gcc 4 3 3 For Real Time Processes entiumVx6 9gcc4 3 3 VxWorks 6 9 o ae For Kernel Modules Any Wind River PPC32 CPU with ppc604Vx6 9gcc4 3 3 gcc 4 3 3 floating point hardware For Real Time Processes ppc604Vx6 9gcc4 3 3_rtp For Kernel Modules ppce500v2Vx6 9gcc4 3 3 For Real Time Processes ppce500v2Vx6 9gcc4 3 3_rtp e500v2 PPC with SPE gcc 4 3 3 VxWorks 6 9 3 2 For Kernel Modules mips32r2sfbeVx6 9gcc4 3 3 For Real Time Processes mips32r2sfbeVx6 9gcc4 3 3 rtp MIPS gcc 4 3 3 sbc8641d gcc 3 32 sbc8641Vx653 2 3gcc3 3 2 VxWorks 653 2 3 SIMPC gcc 3 32 simpcVx653 2 3gcc3 3 2 VxWorks MILS 2 1 1 with vThreads 2 2 3 ppc85xx gcc 3 3 2 ppc85xxVxT2 2 3gcc3 3 2 a For use with Windows and or Solaris Hosts as supported by Wind River Systems b For ppc405 the architecture string is the same for VxWorks 6 6 and 6 7 c Available Q1 2014 The following tables list the libraries you will need to link into your application and the required compiler flags Table 9 6 Building Instructions for VxWorks 5 x and 6 x Architectures on page 52 I Table 9 7 Building Instructions for VxWorks 653 Architectures on page 53 Table 9 8 Building Instructions for VxWorks MILS Architectures on page 54 Compil
53. PtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Linux2 6gcc4 1 1 fmessage length 0 c Wp MD fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU 180586 DTARGET i86Linux2 6gcc4 1 2 fmessage length 0 i86Linux2 6gcc4 1 2 DNDEBUG c Wp MD Release fPIC DLINUX g Wall Wno unknown pragmas DRTS_UNIX Debug DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Linux2 6gcc4 1 2 fmessage length 0 c Wp MD 21 Linux and Fedora Platforms Table 4 7 Library Creation Details for Linux and Fedora Architectures RTI Architecture Library Format Static amp Dynamic Compiler Flags Used by RTI i86Linux2 6gcc4 4 3 Release fPIC DLINUX O Wall Wno unknown pragmas DRTS_UNIX DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Linux2 6gcc4 4 3 fmessage length 0 DNDEBUG c Wp MD Debug fPIC DLINUX g Wall Wno unknown pragmas DRTS_UNIX DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Linux2 6gcc4 4 3 fmessage length 0 c Wp MD i86Linux2 6gcc4 4 5 Release gcc m32 fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU I80586 DTARGET i86Linux2 6gcc4 4 5 V DNDEBUG Wp MD Debug gcc m32 fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU 180586 DTARGETS i
54. RTI Connext DDS Core Libraries and Utilities Platform Notes Version 5 1 0 f t Your systems Working as one 2012 2013 Real Time Innovations Inc All rights reserved Printed in U S A First printing December 2013 Trademarks Real Time Innovations RTI DataBus and Connext are trademarks or registered trademarks of Real Time Innovations Inc All other trademarks used in this document are the property of their respective owners and Use Restrictions of this publication may be reproduced stored a retrieval system or transmitted in any form including electronic mechanical photocopy and facsimile without the PEE written permission of Real Time Innovations Inc The software described in this 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 agreement 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 Contents 1 S pp rted Platforms 1 2 E E E E 3 2 1 MulticastS ppott cei eere hier irn tren HERRERA EE EH SEHE FD 6 22 Supported Transports cene Reni Haee eee aee ente res 6 2 3 Monotonic Clock Support FEN Y e FEES ene toed 6 24 T
55. SION 7 O Wall Wno unknown pragmas DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 c Wp MD ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 Static or DTOOL FAMILY gnu DTOOL gnu D_WRS_KERNEL D__PROTOTYPE_5_0 Dynamic DVXWORKS_MAJOR_VERSION 6 DVXWORKS_MINOR_VERSION 8 O2 Release fno strict aliasing Wall 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 Static or DTOOL FAMILY gnu DTOOL gnu D_WRS_KERNEL D__PROTOTYPE_5_0 g Dynamic DVXWORKS_MAJOR_VERSION 6 DVXWORKS MINOR VERSION 8 Wall Debug Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT Wp MD 59 VxWorks Platforms Table 9 9 Library Creation Details for All VxWorks Architectures RTI Architecture Library Format Compiler Flags Used by RTI ccppc m32 mhard float mstrict align mregnames ansi mlongcall DCPU PPC32 Static or DTOOL FAMILY gnu DTOOL gnu mrtp D PROTOTYPE 5 0 O2 Dynamic fno strict aliasing Wall Wno unknown pragmas DRTS VXWORKS Release DVXWORKS MAJOR VERSION 26 DVXWORKS MINOR VERSION 8 DPtrIntType long DCSREAL IS FLOAT DNDEBUG Wp MD ppc604Vx6 8gcc4 1 2 rtp ccppc m32 mhard float mstrict align mregnames ansi mlongcall DCPU PPC32 Static or DTOOL FAMILY gnu DTO
56. SREAL_IS_FLOAT DCPU p4080 Static bspname pcx86 prefixed_msgs unknown_pragma_silent G Release DPtrIntType long DCSREAL_IS_FLOAT DCPU DTARGET pentiumInty10 0 2 pcx86 DNDEBUG c pentiumInty10 0 2 pcx86 Static bspname pcx86 prefixed_msgs unknown_pragma_silent G Debug DPtrIntType long DCSREAL IS FLOAT DCPU DTARGET pentiumInty10 0 2 pcx86 c INTEGRITY Platforms 34 Library Creation Details for INTEGRITY Architectures 3 3 3 4 3 5 3 6 3 7 3 8 RTI Architecture Le Compiler Flags Used by RTI ormat Static bspname xes p2020 prefixed_msgs unknown_pragma_silent Relea G DPtrIntType long DCSREAL_IS_FLOAT DCPU eease DTARGET ppc85xxInty5 0 11 xes p2020 DNDEBUG c ppc85xxInty5 0 11 xes p2020 Static bspname xes p2020 prefixed msgs unknown pragma silent Deb G DPtrIntType long DCSREAL IS FLOAT DCPU 5798 DTARGET Vppc85xxInty5 0 11 xes p2020 V c Diagnostics on INTEGRITY Systems Connext 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 tar get I O window host I O is generally recommended Host I O will affect the real time perfor mance of the target For more information on consolestring please refer to the INTEGRITY Development Guide Running over IP Backplane on a Dy4 Champ AVII Board C
57. TOTYPE_5_0 Dynamic DVXWORKS_MAJOR_VERSION 5 DVXWORKS_MINOR_VERSION 5 O Release Wno unknown pragmas 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 Static or fno builtin mcpu pentium D WRS KERNEL D__PROTOTYPE_5_0 g Dynamic DVXWORKS_MAJOR_VERSION 5 DVXWORKS_MINOR_VERSION 5 Debug Wno unknown pragmas DRTS_VXWORKS DPtrIntType long DCSREAL_IS_FLOAT DCPU SIMNT c Wp MD Table 9 10 Required Kernel Components for sbc8641Vx653 2 3gcc3 3 29 NCLUDE_ARINC_SCHEDULER_INIT INCLUDE_NETINET_IF_SUBR NCLUDE_ARP_API INCLUDE_NETINET_IGMP Z 2 CLUDE_AUXCLK CLUDE_BOOT_LINE INCLUDE_NETINET_IN INCLUDE_NETINET_IN_CKSUM I I I I I I NCLUDE BOOT LINE INIT INCLUDE NETINET IN PCB NCLUDE BSD SOCKET INCLUDE NETINET IN PROTO INCLUDE BSP MODULES INCLUDE BSP VXWORKS INCLUDE NETINET IP ICMP INCLUDE NETINET IP INPUT INCLUDE BYTENVRAM INCLUDE DEBUG CORE INCLUDE NETINET IP OUTPUT INCLUDE NETINET RADIX INCLUDE DEBUG UTIL INCLUDE NETINET RAW IP INCLUDE END INCLUDE NETINET ROUTE INCLUDE END BOOT INCLUDE EXC SHOW INIT INCLUDE NETINET UDP USRREQ INCLUDE NETINET SYS SOCKET INCLUDE FLASHMEM INCLUDE NETINET UIPC DOM 61 VxWorks Platforms Table 9 10 Required Kernel Components for sbc8641Vx653 2 3gcc3 3
58. Transport APIs link against the additional libraries from Table 8 5 on page 43 Select the files appropriate for your chosen library format Thread Configuration Table 8 6 lists the thread settings for Solaris platforms Table 8 7 lists the thread priority definitions Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Section 19 5 in the RTI Core Libraries and Utilities User s Manual is not available for Solaris platforms Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on Solaris plat forms 44 Solaris Platforms Table 8 6 Thread Settings for Solaris Platforms Table 8 7 Applicable Thread DDS_ThreadSettings_t Platform Specific Setting mask OS default thread type Asynchronous Publisher priority OS default thread priority Asynchronous flushing stack size OS default thread stack size thread cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported Database thread Event thread mask DDS THREAD SETTINGS STDIO priority OS default thread priority 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 task DDS_THREAD_SETTINGS_FLOATING_POINT priority OS default thread priority stack_si
59. Type long DCSREAL IS FLOAT DCPU 4xxFP DTARGET ppc4xxFPLinux2 6gcc4 5 1 DNDEBUG c Wp MD ppc85xxLinux2 6gcc4 3 2 Release fPIC DLINUX g Wall Wno unknown pragmas DRTS_UNIX DPtrIntyType long DCREAL_IS FLOAT DCPU e500 DTARGET ppc85xxLinux2 6gcc4 3 2 DNDEBUG c Wp MD Debug fPIC DLINUX g Wall Wno unknown pragmas DRTS_UNIX DPtrIntyType long DCREAL_IS_FLOAT DCPU e500 DTARGET ppc85xxLinux2 6gcc4 3 2 c Wp MD 22 Linux and Fedora Platforms Table47 Library Creation Details for Linux and Fedora Architectures RTI Architecture Library Format Static amp Dynamic Compiler Flags Used by RTI ppc85xxWRLinux2 6gcc4 3 2 Release mcpu powerpc msoft float fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU PPC32 DTARGET ppc85xxWRLinux2 6gcc4 3 2 DNDEBUG Wp MD Debug powerpc wrs linux gnu gcc mcpu powerpc msoft float PIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU PPC32 DTARGET ppc85xxWRLinux2 6gcc4 3 2 Wp MD x64Linux2 6gcc3 4 5 Release m64 fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL 15 FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc3 4 5 DNDEBUG c Wp MD Debug m64 fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL 15
60. U AMD64 Dynamic DTARGET x64Win64VS2005 DWIN32 D WINDOWS Debug D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN Od ZI MDd EHsc RTC1 D CRT SECURE NO DEPRECATE c 76 Windows Platforms Table 10 8 Library Creation Details for Windows Host Architectures Table 10 9 RTI Library Architecture Format Compiler Flags Used by RTI W3 DPtrIntType long DCSREAL_IS_FLOAT DCPU AMD64 Static DTARGET x64Win64VS2008 DWIN32 D WINDOWS Release D_WIN32_WINNT 0x0501 DWIN32_LEAN_AND_MEAN O2 Zi MT EHsc D_CRT_SECURE_NO_DEPRECATE DNDEBUG W3 DPtrIntType long DCSREAL_IS_FLOAT DCPU AMD64 x64Win64VS2008 Dynamic DTARGET x64Win64VS2008 DWIN32 D WINDOWS Release D_WIN32_WINNT 0x0501 DWIN32 LEAN AND MEAN O2 Zi MD Noe Tikes EHsc D_CRT_SECURE_NO_DEPRECATE DNDEBUG c requires W3 DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 MACHINE X64 Static DTARGET x64Win64VS2008 DWIN32 D WINDOWS option Debug 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 Dynamic DTARGET x64Win64VS2008 DWIN32 D WINDOWS Debug 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 Static DTARGET x64Win64VS2010 DWIN32 D WINDOWS Release D_WIN32_WINNT 0x0501
61. UG c Wp MD Debug mthreads mshared fPIC D POSIX THREADS CALLS D NO INCLUDE WARN g O Wall Wno unknown pragmas DPtrIntType long DCPU I80586 DTARGET V i86Lynx4 0 0gcc3 2 2V c Wp MD ppc7400Lynx4 0 0gcc3 2 2 Release 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 DCPU PPC7400 DTARGET ppc7400Lynx4 0 0gcc3 2 2 DNDEBUG c Wp MD Debug 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 ppc7400Lynx4 2 0gcc3 2 2 Release 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 15 FLOAT DCPU PPC7400 DTARGET ppc7400Lynx4 2 0gcc3 2 2 DNDEBUG c Wp MD Debug 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 2 c Wp MD 28 LynxOS Platforms Table 5 5 Library Creation Details for LynxOS Architectures 5 1 5 2 Library RTI Architecture dee Com
62. VXWORKS MINOR VERSION 3 O Wall Wno unknown pragmas Debug DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PPC604 c Wp MD mhard float mlongcall mregnames mstrict align ansi DTOOL gnu mrtp Static D_PROTOTYPE_5_0 DVXWORKS_MAJOR_VERSION 6 Release DVXWORKS_MINOR_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 Static shared D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 Debu DVXWORKS_MINOR_VERSION 3 O Wall Wno unknown pragmas 8 DRTS_VXWORKS DTOOL_FAMILY gnu DPtrIntType long DCPU PPC32 c Wp MD mcpu 604 mstrict align fno builtin ansi mlongcall mno implicit fp Static or D_WRS_KERNEL D_PROTOTYPE_5_0 DVXWORKS_MAJOR_VERSION 6 Dynamic DVXWORKS_MINOR_VERSION 5 O Wall Wno unknown pragmas Release DRTS_VXWORKS DTOOL gnu DTOOL_FAMILY gnu DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD ppc604Vx6 5gcc3 4 4 mcpu 604 mstrict align fno builtin ansi mlongcall mno implicit fp Static or D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 5 O Wall Wno unknown pragmas Debug DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC604 c Wp MD mhard float mstrict align ansi mregnames mlongcall mrtp D PROTOTYPE 5 0 Static DVXWORKS MAJOR VERSION 26 DVX
63. W 1 Socket Enabled and POSIX Enabled Threads are Required On INTEGRITY platforms Connext internally relies on the POSIX API for many of its system calls As a result any thread calling Connext 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 Additional user threads that call Connext must be spawned from the Initial thread using pthread create Only then is the created thread also POSIX enabled Note that tasks cre ated at build time using the Integrate utility are not POSDX enabled Furthermore threads calling Connext must be socket enabled This can be achieved by calling InitLibSocket before making any Connext 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 INTEGRITY Development Guide for more information Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Section 19 5 in the RTI Core Libraries and Utilities User s Manual is not available for INTEGRITY platforms Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on INTEG RITY platforms Issues with INTEGRITY Systems Delay When Writing to Unreachable Peers On INTEGRITY syste
64. WORKS MINOR VERSION 5 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 Static g DVXWORKS_MAJOR_VERSION 6 DVXWORKS MINOR VERSION 5 O Wall Debug Wno unknown pragmas DRTS_VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC32 c Wp MD 58 VxWorks Platforms 99 Library Creation Details for All VxWorks Architectures RTI Architecture HUAN Compiler Flags Used by RTI mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align ansi Static or D_WRS_KERNEL D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas Release DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC604 DNDEBUG c Wp MD ppc604Vx6 6gcc4 1 2 mcpu 604 fno builtin mlongcall DTOOL gnu mstrict align ansi Static or D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas Debug DRTS VXWORKS DTOOL gnu DTOOL FAMILY gnu DPtrIntType long DCPU PPC604 c Wp MD mhard float mlongcall mregnames mstrict align ansi mrtp D_PROTOTYPE_5_0 Static DVXWORKS_MAJOR_VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Release Wno unknown pragmas DRTS VXWORKS DTOOL gnu
65. alized in bss mcpu 8540 mvthreads mlongcall mstrict align Dynamic mabi no spe msoft float G 0 fvolatile fno builtin O Wall Wno unknown pragmas Release DPtrIntType long DCSREAL_IS_FLOAT DCPU PPC85XX DNDEBUG ppc85xxVxT2 2 3gcc3 3 2 Static or fno zero initialized in bss mcpu 8540 mvthreads mlongcall mstrict align Dynamic mabi no spe msoft float G 0 fvolatile fno builtin g Wall Wno unknown pragmas Debug DPtrIntType long DCSREAL IS FLOAT DCPU PPC85XX ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 DTOOL_FAMILY gnu DTOOL e500v2gnu te500v2 mcpu 8548 Static or mfloat gprs double mspe yes mabi spe D_WRS_KERNEL Dynamic D__PROTOTYPE_5_0 DVXWORKS_MAJOR_VERSION 6 Release DVXWORKS MINOR VERSION O2 fno strict aliasing Wall Wno unknown pragmas DRTS VXWORKS DPtrIntType long ppce500v2Vx6 9gcc4 3 3 DCSREAL IS FLOAT DNDEBUG Wp MD ccppc m32 mstrict align ansi fno builtin mlongcall DCPU PPC32 Static or DTOOL_FAMILY gnu DTOOL e500v2gnu te500v2 mcpu 8548 Dynamic mfloat gprs double mspe yes mabi spe D WRS KERNEL Se 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 60 VxWorks Platforms Table 9 9 Library Creation Details for All VxWorks Architectures RTI Architecture uad Compiler Flags Used by RTI ccppc m
66. application built with the following RTI architecture packages e x6 amp 4Win64VS2008 built with dynamic libraries e i86Win32V52008 built with dynamic libraries The Microsoft Visual C 2008 SP1 Redistribution Package can be downloaded from the following Microsoft website For x86 architectures http www microsoft com downloads details aspx fami lyid A5C84275 3B97 4AB7 A40D 3802B2AF5FC2 amp displaylang en For x64 architectures http www microsoft com downloads details aspx Fami lyID ba9257ca 337f 4b40 8c14 157cfdffee4e amp displaylang en Visual Studio 2010 Service Pack 1 Requirement L You must have Visual Studio 2010 Service Pack 1 or the Microsoft Visual C 2010 SP1 Redistribution Package installed on the machine where you are running an application built with the release libraries of the following RTI architecture packages e i86Win32V52010 built with dynamic libraries e x64Win64VS2010 built with dynamic libraries e i86Win32dotnet4 0 and x64Win64dotnet4 0 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 Redistribution Package can be obtained from the following Microsoft website For x86 architectures http www microsoft com download en details aspx id 5555 For x64 architectures http www microsoft com download en details aspx id 14632 Visual Studio 2012 R
67. aries are located in lt openssl install dir gt lt architecture gt lib where openssl install dir is where you installed OpenSSL such as c rti openssl 0 9 8f 77 Windows Platforms Table 10 Table 10 1 10 Additional Libraries for Using RTI TCP Transport APIs on Windows Systems Library Format RTI TCP Transport Libraries Dynamic Release nddstransporttcp dll Dynamic Debug Static Release nddstransporttcpd dll nddstransporttcpz lib Static Debug nddstransporttcpzd lib a The libraries are located in lt Connext install dir gt XlibX lt architecture gt X where Connext install dir is where you installed Connext such as local rti ndds 5 x y 1 Additional Libraries for using RTI TCP Transport APIs on Windows Systems with TLS Enabled Library Format RTI TLS Libraries Dynamic Release nddstls dll Dynamic Debug nddstlsd dll Static Release nddstlsz dll Static Debug nddstlszd dll OpenSSL Libraries iac bane libeay32 lib a The libraries are located in lt TLS install dir lib architecture where TLS install dir is where you installed RTI TLS Support such as local rti ndds 5 x y 78
68. ases 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 Note Starting with 4 5e support for the TimesTen database has been removed 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 follow ing Linux architectures 4 i86Linux2 6gcc4 1 1 i86Linux2 6gcc4 6 3 LI x64Linux2 6gcc4 1 1 x64Linux2 6gcc4 6 3 For more information on database setup please see the Addendum for Database Setup 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 RTI Core Libraries and Utilities If you choose to use it it must be downloaded and installed separately It is only available on specific architectures See the RTI Secure WAN Trans port Release Notes and RTI Secure WAN Transport Release Notes Installation Guide for details To use the WAN or Secure Transport APIs link against the additional libraries from Table 4 8 on page 24 Select the files appropriate for your chosen library format Libraries Required for Using RTI TCP Transport APIs To use the TCP Transport APIs link against the additional libraries from Table 4 9 on page 24 If you are using RTI TLS Su
69. at must be set at run time for a LynxOS architecture Table 5 5 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 applica tion You may find this information useful if you are involved in any in depth debugging Note The Java API is not supported on LynxOS platforms in Connext 5 1 0 If you would like Java to be supported on LynxOS please contact your RTI account manager Table5 2 Building Instructions for LynxOS Architectures Connext Libraries API Library Format Required RTI Libraries libnddscppz a libnddscz a Static Release libnddscorez a For Connext Messaging also include librticonnextmsgcppz a libnddscppzd a libnddsczd a Static Debug libnddscorezd a C For Connext Messaging also include librticonnextmsgcppzd a libnddscpp so libnddsc so Dynamic Release libnddscore so For Connext Messaging also include librticonnextmsgcpp so libnddscppd so libnddscd so Dynamic Debug libnddscored so For Connext Messaging also include librticonnextmsgcppd so libnddscz a Static Release libnddscorez a For Connext Messaging also include librticonnextmsgcz a libnddsczd a Static Debug libnddscorezd a For Connext Messaging also include librticonnextmsgczd a libnddsc so Dynamic Release libnddscore so For Connext Messaging also include librticonnextmsgc
70. crease 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 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 a k a the GOT for any single library which limits how many symbols the library can export Some Connext libraries in particular libnddsc export a number of symbols that exceed this upper bound Dynamic libraries are available for VxWorks 6 3 and higher systems with RTP mode on Pentimum CPUs 48 VxWorks Platforms 9 4 9 5 9 6 9 6 1 Requirement for Restarting Applications When restarting a VxWorks application you may need to change the applId value In general this is only required if you still have other Connext applications running on other systems that were talking to the restarted application If all the Connext applications are restarted there should be no problem This section explains why this is necessary and how to change the appld All Connext 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 th
71. cribed in Section 19 5 in the RTI Core Libraries and Utilities User s Manual is not available for Windows platforms Table 10 2 Thread Settings for Windows Platforms Applicable Thread DDS ThreadSettings t Platform Specific Setting mask OS default thread type Asynchronous Publisher priority 2 Asynchronous flushing stack size OS default thread stack size thread ReceiverPool threads cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported mask DDS THREAD SETTINGS STDIO priority 3 Database thread stack_size OS default thread stack size cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported 68 Windows Platforms Table 10 Table 10 Table 10 10 8 2 Thread Settings for Windows Platforms Applicable Thread DDS ThreadSettings t Platform Specific Setting nas DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT priority 2 Event fusa stack size OS default thread stack size cpu list CPU core affinity not supported rotation CPU core affinity not supported mask DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS FLOATING POINT priority 2 ReceiverPool threads stack size OS default thread stack size cpu list CPU core affinity not supported rotation CPU core affinity not supported 3 Thread Priority Definitions for Window
72. dows 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 located in the directory NDDSHOME Mib architecture 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 appropriate for your current work Do not mix libraries built for different formats Visual Studio 2005 Service Pack 1 Redistributable Package MFC Security Update Require ment 4 You must have the Microsoft Visual 2005 Service Pack 1 Redistributable Package Security Update installed on the machine where you are running an application built with the release or debug libraries of the following RTI architecture packages e i86Win32V52005 and x64Win64VS2005 built with dynamic libraries e i86Win32jdk and x64Win64jdk e i86Win32dotnet2 0 and x64Win64dotnet2 0 65 Windows Platforms The Microsoft Visual C 2005 Service Pack 1 Redistributable Package MFC Security Update can be obtained from the following Microsoft website http www microsoft com download en details aspx id 26347 Visual Studio 2008 Service Pack 1 Requirement I You must have Visual Studio 2008 Service Pack 1 or the Microsoft Visual C 2008 SP1 Redistribution Package installed on the machine where you are running an
73. e If you choose to use it it must be downloaded and installed separately It is only available on specific architectures See the RTI Secure WAN Trans port Release Notes and RTI Secure WAN Transport Installation Guide for details To use the WAN or Secure Transport APIs add the libraries from Table 10 9 on page 77 to your project files Libraries Required for Using RTI TCP Transport APIs To use the TCP Transport APIs link against the additional libraries from Table 10 10 on page 78 Select the files appropriate for your chosen library format 1 RTI CoreLibrariesAndUtilities GettingStarted DatabaseAddendum pdf 70 Windows Platforms Table 10 5 Building Instructions for Windows Host Architectures Library Reguired i API Format RTI Libraries or Jar Files System Required Compiler Flags Libraries nddscz lib Static nddscorez lib D RTI WIN32 MT Release For Connext Messaging also i include rticonnextmsgcz lib nddsczd lib Static nddscorezd lib D RTL WIN32 MTd Debug For Connext Messaging also netapi32 lib i C include rticonnextmsgczd lib advapi32 lib nddsclib user32 lib Dyn nde A ddscore lib ws2_32 lib D RTI WIN32 Release For Connext Messaging also include rticonnextmsgc lib nddscd lib Dynamic nddscored lib m DD UL VARIABLE Debug For Connext Messaging also MDd include rticonnextmsgcd lib nddscppz lib nddscz l
74. e application 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 providing a unique appld The first approach is to save the appld in NVRAM or the file system and then increment the appld across reboots The second approach is to base the appld on something that is likely to be different across reboots such as a time based register Multicast Support Multicast is supported on VxWorks 5 x and 6 x VxWorks 653 and VxWorks MILS platforms It 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 documentation for more information Multicast is not supported on the following platforms 4 mips32r2sfbeVx6 9gcc4 3 3 L mips32r2sfbeVx6 9gcc4 3 3 rtp 4 simpcVx653 2 3gcc3 3 2 Supported Transports Shared memory Shared memory is supported and enabled by default on all VxWorks 6 x archi tectures It is not supported on VxWorks 5 x VxWorks 653 or VxWorks MILS platforms For instructions on how to run Connext libraries in kernels that are built without shared memory support refer to Section 9 6 1
75. e thread priority definitions Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Section 19 5 in the RTI Core Libraries and Utilities User s Manual is not available for LynxOS platforms Thread Settings for LynxOS Platforms Applicable Thread DDS ThreadSettings t Platform specific Setting mask OS default thread type priority 13 puce ie er ele rius cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported 30 Mac OS Platforms Table 5 6 Thread Settings for LynxOS Platforms Table 5 7 5 6 Table 6 1 Applicable Thread DDS_ThreadSettings_t Platform specific Setting mask DDS THREAD SETTINGS STDIO priority 10 Database thread stack size 16 1024 cpu list CPU core affinity not supported rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO mask DDS THREAD SETTINGS FLOATING P OINT Event thread priority 13 stack_size 4 16 1024 cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported ReceiverPool threads DDS THREAD SETTINGS STDIO mask DDS THREAD SETTINGS FLOATING P OINT priority 29 stack size 4 16 1024 cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported Thread Priority Definitions for LynxOS Platforms Thr
76. ead Priority Definition Operating System Priority THREAD_PRIORITY_DEFAULT 17 THREAD_PRIORITY_HIGH 32 THREAD_PRIORITY_ABOVE_NORMAL 29 THREAD_PRIORITY_NORMAL 17 THREAD_PRIORITY_BELOW_NORMAL 13 THREAD_PRIORITY_LOW 10 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on LynxOS platforms Mac OS Platforms Table 6 1 lists the architectures supported on Mac OS operating systems Mac OS Platforms RTI Architecture Operating System CPU Compiler Abbreviation clang 4 1 x64Darwin12clang4 1 Mac OS X 10 8 x64 Java Platform Standard Edition JDK 1 7 x64Darwin12clang4 1jdk 31 Mac OS Platforms Table 6 2 lists the compiler flags and libraries you will need to link into your application Table 6 3 provides details on the environment variables that must be set at run time for a Mac OS architecture Table 6 4 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 applica tion You may find this information useful if you are involved in any in depth debugging To use rtiddsgen to create files for a Java target By default rtiddsgen uses JRE 1 4 which is distributed with the RTI Core Libraries and Utilities in NDDSHOME jre To use rtiddsgen with Java 1 6 you need Xalan Java 2 7 1 or high
77. edistributable Package Requirement 1 You must have Visual C Redistributable for Visual Studio 2012 Update 3 installed on the machine where you are running a C application built the release libraries of the fol lowing RTI architecture packages i86Win32V52012 built with dynamic libraries x64Win64VS2012 built with dynamic libraries e i86Win32dotnet4 5 and x64Win64dotnet4 5 You can download Visual C Redistributable for Visual Studio 2012 Update 3 from this Microsoft website http www microsoft com en ca download details aspx id 30679 Windows Registry Setting for Better Performance On all Windows systems prior to Windows Vista the following registry setting change will improve performance when sending UDP datagrams of size larger than 1024 bytes 66 Windows Platforms 10 1 10 2 10 3 Under HKEY LOCAL MACHINE SYSTEM CurrentControlSet Services AFD Parameters add the following DWORD Name FastSendDatagramThreshold Value 65536 This will improve the Connext 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 Table 10 7 on page 74 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 10 8 on page 75 This information is provided strict
78. er 1 Download the latest Xalan Java version from http xml apache org xalan j 2 Unpack the Xalan distribution file in a location of your choice 3 Set the XALANHOME environment variable to the Xalan installation directory 4 Set the NDDSJREHOME environment variable to the JRE 1 6 installation directory 5 Run rtiddsgen using the script located in NDDSHOME scripts Table 6 2 Building Instructions for Mac OS Architectures Libra Required API Forms Required RTI Libraries System Libraries Required Compiler Flags libnddscppz a libnddscz a Static Release libnddscorez a For Connext Messaging also include librticonnextmsgcppz a libnddscppzd a libnddsczd a Static Debug libnddscorezd a dynamic lpthread For Connext Messaging also include lc single module librticonnextmsgcppzd a dl Im DRTI UNIX Et libnddscpp dylib lpthread DRTI DARWIN Dynamic libnddsc dylib DRTI DARWIN10 1 libnddscore dylib Release DRTI 64BIT For Connext Messaging also include librticonnextmsgcpp dylib libnddscppd dylib libnddscd dylib Dynamic libnddscored dylib Debug For Connext Messaging also include librticonnextmsgcppd dylib 32 Mac OS Platforms Table 6 2 Table 6 3 Building Instructions for Mac OS Architectures Required Library Required RTI Libraries System Ea o Libraries libnddscz a libnddscorez a Static Release
79. et2 0 64 bit Edition d Visual Studio 2008 SP 1 x64Win64VS2008 Java Platform Standard Edition JDK 1 7 x64Win64jdk Visual Studio 2005 SP 1 C C 8 0 or 9 0 x64Win64dotnet2 0 Windows Server 2008 R2 Visual Studio 2010 x64Win64VS2010 64 bit Edition _ Visual Studio 2010 C CLI Ci 8 0 or 9 0 x64Win64dotnet4 0 Java Platform Standard Edition JDK 1 7 x64Win64jdk Visual Studio 2012 x64Win64VS2012 inden DDIAD x64 Visual Studio 2012 x64Win64dotnet4 5 64 bit Edition Java Platform Standard Edition JDK 1 7 x64Win64jdk Visual Studio 2005 SP 1 i86Win32VS2005 Visual Studio 2005 SP 1 C CLI C 8 0 or 9 0 i86Win32dotnet2 0 Windows Vista 32 bit Edition x86 Visual Studio 2008 SP 1 i86Win32VS2008 Java Platform Standard Edition JDK 1 7 i86Win32jdk Windows Platforms Table 10 1 Supported Windows Architectures Operating System CPU Software Kit RTI Architecture Visual Studio 2005 SP 1 x64Win64VS2005 Visual Studio 2005 SP 1 C CLI C 8 0 or 9 0 x amp 4Win64dotnet2 0 Windows Vista 64 bit Edition x64 Visual Studio 2008 SP1 x64Win64VS2008 Java Platform Standard Edition JDK 1 7 x64Win64jdk Visual Studio 2005 SP 1 i86Win32VS2005 Windows 32 bit Visual Studio 2005 SP 1 C CLI C 8 0 or 9 0 i86Win32dotnet2 0 Professional Edition SP2 is Visual Studio 2008 SP 1 i86Win32VS2008 Java Platform Standard Edition JDK 1 7 i86Win32jdk Visual Studio 2005 SP 1 x64Win64VS200
80. g also include librticonnextmsgcppz a libnddscppzd a libnddsczd a m libnddscorezd a For Connext Messaging also include C librticonnextmsgcppzd a libnddscpp so libnddsc so Dynamic tibnadscore so Release For Connext Messaging also include See either librticonnextmsgcpp so Table 9 10 Required libnddscppd so Kernel Components for libnddscd so sbc8641Vx653 2 3gcc3 3 2 libnddscored so on page 61 DRTI VXWORKS ebu For Connext Messaging also include DRTI_VX653 librticonnextmsgcppd so Table 9 11 Required libnddscz a Kernel Components for Static simpcVx653 2 3gcc3 3 2 on page 62 Release For Connext Messaging also include librticonnextmsgcz a libnddsczd a Static libnddscorezd a Debug For Connext Messaging also include librticonnextmsgczd a C libnddsc so Dynamic libnddscore so Release For Connext Messaging also include librticonnextmsgc so libnddscd so Dynamic libnddscored so Debug For Connext Messaging also include librticonnextmsgcd so a The Connext C C libraries are located in NDDSHOME lib lt architecture gt where NDDSHOME is where Connext is installed such as c rti ndds 5 x y 53 VxWorks Platforms Table 9 8 Building Instructions for VxWorks MILS Architectures Library Required Required AM Format Required RI Litanies Kernel Components Compiler Flags libnddscppz a libnddsc
81. gcc 4 12 For Kernel Modules gt With 32 bit PowerPC ppc604Vx6 8gcc4 1 2jdk 604 a Reguires NI RIO 13 1 release or a patch from NI for NI RIO 13 0 b Some PowerPC cores such as e500v1 and e500v2 are not fully backwards compatible with PPC 604 2 AIX Platforms Table 2 1 lists the architectures supported on the IBM AIX operating system Table 2 1 Supported AIX Target Platforms Operating RTI Architecture System ud Compiler Abbreviation POWERS 32 bit mode IBM XLC for AIX v9 0 p5AIX5 3xlc9 0 POWERS 64 bit mode IBM XLC for AIX v9 0 64p5AIX5 3xlc9 0 IBM xlC_r for AIX v12 1 64p7 AIX7 1xlc12 1 7 1 POWER class 64 bit mode IBM Java 1 7 64p7 AIX7 1xlc12 1jdk Table 2 2 lists the compiler flags and the libraries you will need to link into your application Table 2 3 provides details on the environment variables that must be set at run time for an AIX architecture AIX Platforms Table 2 2 Table 2 4 provides details on how the libraries were built This table is provided strictly for infor mational 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 Building Instructions for AIX Architectures API Library Format Required RTI Libraries Required System Libraries Required Compiler Flags C Static Release libnddscppz a libnddscz a
82. gmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 4 4 c Wp MD x64Linux2 6gcc4 4 3 Release m64 fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 4 3 DNDEBUG c Wp MD Debug m64 fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET V x64Linux2 6gcc4 4 3 V fmessage length 0 c Wp MD 23 Linux and Fedora Platforms Table47 Library Creation Details for Linux and Fedora Architectures Library RTI Architecture ps Compiler Flags Used by RTI Dynamic gcc m64 fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX Release DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 4 5 V DNDEBUG Wp MD x64Linux2 6gcc4 4 5 gcc m64 fPIC DLINUX g Wall Wno unknown pragmas DRTS_UNIX Debug DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 4 5 Wp MD fPIC DLINUX O Wall Wno unknown pragmas DRTS UNIX Release DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET x64Linux2 6gcc4 5 1 DNDEBUG c Wp MD x64Linux2 6gcc4 5 1 fPIC DLINUX g Wall Wno unknown pragmas DRTS UNIX Debug DPtrIntType long DCSREAL IS FLOAT DCPU AMD64 DTARGET V x64Linux2 6gcc4 5 1 V fmessage length 0 c Wp MD m6
83. hread Configuration 6 25 Durable Writer History and Durable Reader State Features sss 8 3 INTEGRITY Platforms CR 8 3 1 Patch Required for INTEGRITY 10 02 Platform sese eene nnne nnns 8 3 2 Support for Request Reply Communication Pattern sees 8 3 3 Diagnostics on INTEGRITY 10 34 Running over IP Backplane on a Dy4 Champ AVII Board sse 10 3 5 Mult NIC Support on INTEGRITY DO enixa DR YB 10 230 MulticastSuppOEtiasesemmenideaemeeibud esent erit E nre IO 10 3 7 Supported Transports eret ertet terme 10 3 8 Out of the box Transport Compatibility with Other Connext Platforms 10 3 9 Using rtiddsping and rtiddsspy on PowerPC INTEGRITY Systems 12 3 10 Monotonic Clock ninnan E EE tenente tenente tenerent 12 Thread CornfiguratiOn iin nete item hne tete e pee eater Ha 12 312 Durable Writer History and Durable Reader State Features 14 3 13 Iss es with INTEGRITY SYSTEMS dividi iu Pd ui e dividunt Gu o Crit 14 4 Linux and Fedora Platforms eee ee eeeee sete terne tett
84. ib nddscorez lib D RTI WIN22 MT For Connext Messaging also include rticonnextmsgcppz lib nddscppzd lib nddsczd lib Done nddscorezd lib D RTI WIN32 MTd For Connext Messaging also netapi32 lib Bu include rticonnextmsgcppzd lib advapi32 lib nddscpp lib user32 lib nddsc lib ws2_32 lib D RTI_WIN32 e nddscore lib D NDDS DLL VARIABLE For Connext Messaging also MD include rticonnextmsgcpp lib nddscppd lib nddscd lib D RTI WIN32 Dl nddscored lib D NDDS DLL VARIABLE For Connext Messaging also MDd include rticonnextmsgcppd lib 71 Windows Platforms Table 10 5 Building Instructions for Windows Host Architectures API Library Format RTI Libraries or Jar Files Required System Libraries Required Compiler Flags CLI Release nddscpp lib nddsc lib nddscore lib nddsdotnet dll or nddsdotnet40 dll Debug nddscppd lib nddscd lib nddscored lib nddsdotnetd dll or nddsdotnet40 dll N A 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 CH Release nddsdotnet dll or nddsdotnet40 dll For Connext Messaging also include rticonnextdotnet dll or rticonnextdotnet40 dll Debug nddsdotnetd dll or nddsdotnet40d dll For Connext Messaging also include rticonnextdotnetd dll or rticonnextdotnet40d dll N A N A
85. igures the schedule policy to SCHED FIFO DDS THREAD SETTINGS PRIORITY ENFORCE N A a See VxWorks manuals for additional information Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on VxWorks platforms Increasing the Receive Socket Buffer Size For Connext applications running on VxWorks 6 7 or higher systems and using UDPv4 we rec ommend 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 correct Wind River defect number WIND00135312 51 VxWorks Platforms Table 9 6 Building Instructions for VxWorks 5 x and 6 x Architectures Library a Reguired Reguired aw Format Required RTL Libraries Kernel Components Compiler Flags libnddscppz a libnddscz a Static libnddscorez a Release For Connext Messaging also include INCLUDE TIMESTAMP librticonnextmsgcppz a libnddscppzd a For VxWorks 6 4 and below libnddsczd a also use ei libnddscorezd a INCLUDE_ZBUF_SOCK ebu INCLUDE_IGMP For Connext Messaging also include a librticonnextmsgcppzd a For VxWorks 6 3 and higher DRTI VXWORKS libnddscpp so libnddsc so iud ee OSIX CLOCKS INCLUDE POSIX CL Dynamic ibn dscore so Release y a Connext
86. ine documentation for details on the shared memory and semaphore keys used by Connext Increasing Available Shared Resources Connext uses System V semaphores to manage shared memory communication If you plan to run multiple Connext applications on the same node at the same time you may need to increase the number of available semaphores 43 Solaris Platforms 8 4 8 5 8 6 8 6 1 8 7 Each Connext application that has shared memory enabled allocates 4 individual semaphores The Solaris system defaults allow only 10 per host which may 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 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 etc system will also work The following values are just an exam ple 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 etc system file 1 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 t
87. ing a Connext application for VxWorks depends on the development platform For more information such as specific compiler flags see the VxWorks Programmer s Guide Table 9 9 on page 55 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 correctly For more information see the VxWorks Programmer s Guide 47 VxWorks Platforms 9 1 Table 9 2 9 2 9 3 Support for Request Reply Communication Pattern RTI Connext Messaging includes support for the Request Reply Communication Pattern for all the platforms described in Table 9 1 on page 46 and all programming languages except as noted below When using C the following platforms do not support the Request Reply Communication Pattern 4 ppc603Vx5 5gcc 4 ppc604Vx5 5gcc When using a Connext Messaging library for C Request Reply for kernel mode you need to perform 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
88. inux Platforms on ARM CPUs RTI Architecture Operating System CPU Compiler Abbreviation Raspbian Wheezy 7 0 3 x kernel ARMv6 Java Platform Standard Edition gcc 4 7 22 armv6vfphLinux3 xgcc4 7 2 JDK 1 7 armv6vfphLinux3 xgcc4 7 2jdk a Reguires Linaro Gnueabihf Cross Compiler Linux and Fedora Platforms Table4 2 Linux Platforms on Cell BE CPUs RTI Architecture Operating System CPU Compiler Abbreviation Fedora 12 2 6 32 kernel y Cell BE gcc 4 5 1 glib 2 9 cell64Linux2 6gcc4 5 1 Available upon request only a Reguires a custom version of gcc 4 5 1 Table 4 3 Linux Platforms on Intel CPUs Operating System CPU Compiler pr robe eri gcc 4 1 2 i86Linux2 6gcc4 1 2 iii Java Platform Standard Edition JDK 1 7 i86Linux2 6gcc4 1 2jdk CentOS 5 4 5 5 2 6 kernel gcc 4 1 2 x64Linux2 6gcc4 1 2 is Java Platform Standard Edition JDK 1 7 x64Linux2 6gcc4 1 2jdk gcc 4 4 5 i86Linux2 6gcc4 4 5 Java Platform Standard Edition JDK 1 7 i86Linux2 6gcc4 4 5jdk CentOS 6 0 6 2 6 4 2 6 kernel gcc 4 4 5 x64Linux2 6gcc4 4 5 Java Platform Standard Edition JDK 1 7 x64Linux2 6gcc4 4 5jdk Fedora 12 2 6 32 kernel x64 gcc 4 4 4 x64Linux2 6gcc4 4 4 i WA x64Linux2 6gcc4 5 1 Red Hat Enterprise Linux 4 0 x86 gcc 3 4 3 i86Linux2 6gcc3 4 3 2 6 Kernel x6
89. iority 1 INTEGRITY 10 0 2 only Database thread stack size 20 1024 cpu list CPU core affinity not supported rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO mask DDS THREAD SETTINGS FLOATING PO INT Event thread priority 80 stack size 4 20 1024 cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO mask DDS THREAD SETTINGS FLOATING PO INT ReceiverPool threads priority 100 stack size 4 20 1024 cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported Thread Priority Definitions for INTEGRITY Platforms Except 10 02 Thread Priority Definition Operating System Priority THREAD PRIORITY DEFAULT 16 THREAD PRIORITY HIGH 120 THREAD PRIORITY ABOVE NORMAL 100 THREAD PRIORITY NORMAL 90 THREAD PRIORITY BELOW NORMAL 80 THREAD PRIORITY LOW 60 Thread Priority Definitions for INTEGRITY 10 02 Platforms Thread Priority Definitions Operating System Priority THREAD PRIORITY DEFAULT 127 THREAD PRIORITY HIGH 127 THREAD PRIORITY ABOVE NORMAL 100 THREAD PRIORITY NORMAL 90 THREAD PRIORITY BELOW NORMAL 80 INTEGRITY Platforms Table3 7 Thread Priority Definitions for INTEGRITY 10 02 Platforms 3 11 1 3 11 2 3 12 3 13 3 13 1 3 13 2 Thread Priority Definitions Operating System Priority THREAD PRIORITY LO
90. it After building any Connext application that uses shared memory you must use the intex utility provided with the INTEGRITY development environment to pack the application with multi ple address spaces one or more to contain the Connext application s and another one to con tain the posix shm manager Connext 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 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 distri bution INTEGRITY Platforms 3 8 3 3 9 3 10 3 11 os dir local applications integrity integrity 10 0 2 2 Build the project 3 Before running your Connext 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 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 INTEG
91. local rti openssl 0 9 8x Table 4 9 Additional Libraries for using RTI TCP Transport APIs on UNIX based Systems Library Format RTI TCP Transport Libraries Dynamic Release libnddstransporttcp so Dynamic Debug libnddstransporttcpd so 24 Linux and Fedora Platforms Table 4 9 Additional Libraries for using RTI TCP Transport APIs on UNIX based Systems Library Format RTI TCP Transport Libraries Static Release libnddstransporttcpz a Static Debug libnddstransporttcpzd a a The libraries are located in lt Connext install dir gt lib lt architecture gt where Connext install dir is where you installed Connext such as local rti ndds 5 x y Table 4 10 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 Release libnddstlsz a Static Debug libnddstlszd a OpenSSL Libraries ARE libcrypto so a The libraries are located in lt TLS install dir lib architecture where lt TLS install dir is where you installed RTI TLS Support such as local rti ndds 5 x y Table 4 11 Thread Settings for Linux and Fedora Platforms Applicable Thread DDS ThreadSettings t Platform Specific Setting mask OS default thread type priority OS default thread pri
92. located in wan install dir lib architecture where wan install dir is where you installed RTI Secure WAN Transport such as local rti ndds 5 x y b These libraries are located lt openssl install dir architecture lib where lt openssl install dir is where you installed OpenSSL such as local rti openssl 0 9 8x 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 documentation for more information Supported Transports Shared memory Supported and enabled by default UDPv4 Supported and enabled by default UDPv6 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 platforms TCP IPv4 Not supported Shared Memory Support To see a list of shared memory resources in use use the ipcs command To clean up shared memory and shared semaphore resources use the ipcrm command The shared memory keys used by Connext are in the range of 0x400000 For example ipcs m grep 0x4 The shared semaphore keys used by Connext are in the range of 0x800000 the shared mutex keys are in the range of 0xb00000 For example ipcs s grep 0x8 ipcs s grep Oxb Please refer to the shared memory transport onl
93. lt Building Instructions for QNX Architectures API Library Format RTI Libraries Required System Libraries Required Compiler Flags C Static Release libnddscppz a libnddscz a libnddscorez a For Connext Messaging also include librticonnextmsgcppz a Static Debug libnddscppzd a libnddsczd a libnddscorezd a For Connext Messaging also include librticonnextmsgcppzd a Dynamic Release libnddscpp so libnddsc so libnddscore so For Connext Messaging also include librticonnextmsgcpp so Dynamic Debug libnddscppd so libnddscd so libnddscored so For Connext Messaging also include librticonnextmsgcppd so Im lsocket DRTI ONX Static Release libnddscz a libnddscorez a For Connext Messaging also include librticonnextmsgcz a Static Debug libnddsczd a libnddscorezd a For Connext Messaging also include librticonnextmsgczd a Dynamic Release libnddsc so libnddscore so For Connext Messaging also include librticonnextmsgc so Dynamic Debug libnddscd so libnddscored so For Connext Messaging also include librticonnextmsgcd so Im lsocket DRTI ONX a The NDDS C C libraries are located in NDDSHOME lib lt architecture gt where NDDSHOME is where Connext is installed such as c rti ndds 5 x y 36 QNX Platforms Table7 3 Running Instructions for QNX Architectures Library
94. ly for informational purposes you do not need to use these parameters to com pile your application You may find this information useful if you are involved in any in depth debugging Table 10 9 on page 77 and Table 10 10 on page 78 list additional libraries required when using the optional RTI Secure WAN Transport and RTI TCP Transport respectively Use Dynamic MFC Library Not Static To avoid communication problems in your Connext application use the dynamic MFC library not the static version If you use the static version your Connext application may stop receiving samples once the Win dows sockets are initialized Visual Studio 2005 Required when Using RTI Debug Libraries for Java or NET APIs The Connext dynamic libraries for Java and NET rely on Microsoft Visual Studio 2005 Service Pack 1 run time libraries These libraries are available with Microsoft Visual Studio 2005 or as part of a redistributable package independent of Visual Studio The redistributable package is available for download from the RTI Customer Portal However while Microsoft includes debug versions of these run time libraries with Visual Stu dio it only includes release versions in the redistributable package This limitation means that if you do not have Visual Studio 2005 installed you cannot use the RTI debug libraries you must use the RTI release libraries If you attempt to use the RTI debug libraries and your system does not have debug ver
95. mic libnddscored so Debug For Connext Messaging also include librticonnextmsgcd so 40 Solaris Platforms Table8 2 Building Instructions for Solaris Architectures API Library RTI Libraries or Jar Files Required System Required Compiler Format Libraries Flags libnddscppz a libnddscz a Static libnddscorez a Release For Connext Messaging also include librticonnextmsgcppz a libnddscppzd a sparc64Sol2 10gcc3 4 2 Be ln Id Insl Isocket Debug libnddscorezd a lgen Iposix4 sparc64Sol2 10gcc3 4 2 For Connext Messaging also include Ipthread Im lc DRTI_UNIX m64 librticonnextmsgcppzd a C libnddscpp so All other architectures a libnddsc so Jdl Insl lgenIO All other architectures libnddscore so Isocket Igen DRTI UNIX m32 elease For Connext Messaging also include Iposix4 Ipthread librticonnextmsgcpp so Im lc libnddscppd so libnddscd so Dynamic tibnadscored so Debug For Connext Messaging also include librticonnextmsgcppd so nddsjava jar Release For Connext Messaging also include rticonnextmsg jar N A N one require nddsjavad jar is Debug For Connext Messaging also include rticonnextmsed jar a The RTI C C libraries are located in NDDSHOME lib lt architecture gt The RTI Java files are located in NDDSHOME class where NDDSHOME is where Connext is installed such as local rti ndd
96. ms if a publishing application s initial peers list includes a nonexistent or simply unreachable host calls to write 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 initial 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 Bug 10768 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 sys tem you may notice the application blocks for 2 seconds at start up Linux and Fedora Platforms 3 13 3 3 13 4 Table 4 1 Compiler Warnings Regarding Unrecognized pragma Directives Building Connext projects for INTEGRITY causes the compiler to produce several warnings about pragma directives not recognized in some Connext 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 include ndds dds c dds c infrastructure h line 945 warning unrecognized pragma
97. munching This step is necessary for properly initialization of static objects and to ensure that the C run time support calls the cor rect constructor destructors in the correct order for all static objects If you need to use the C Request Reply API for kernel mode you need to munch your appli cation and link or load the Connext Messaging library for C request reply in addition to the standard Connext libraries for core C and C RII provides pre munched Connext Messaging libraries for C Request Reply with the exten sion 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 assuming you want to use non debug libraries 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 peformed the munching process Pre Munched Kernel mode C Request Reply Libraries Library Description librticonnextmsgcpp lo Munched Release C Request Reply library librticonnextmsgcppd lo Munched Debug C Request Reply library Increasing the Stack Size Connext applications may require more than the default stack size on VxWorks To prevent stack overrun you can create enable the DomainParticipant in a thread with a larger stack or in
98. n Section 19 5 in the RTI Core Libraries and Utilities User s Manual is not available for AIX platforms INTEGRITY Platforms 2 5 Table 3 1 Table 3 2 3 1 3 2 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on AIX plat forms INTEGRITY Platforms Table 3 1 lists the architectures supported on the INTEGRITY operating system Supported INTEGRITY Target Platforms Operating CPU Compiler IP Stack RTI Architecture Abbreviation System INTEGRITY 5 0 11 PPC 85XX Multi 4 2 4 GHnet2 IP stack ppc85xxInty5 0 11 xes p2020 p4080 based Multi 6 1 GHNet2 v2 p4080Integrity10 0 2 xes p4080 smp INTEGRITY 10 0 2 sqqme core x86 Multi 5 0 6 CHNet IPv4 stack pentiumInty10 0 2 pcx86 a For use with Windows and Solaris hosts as supported by Green Hills Software b Kernel must be built using lip4 or lip46 c Requires patch 6901 iff from Green Hills Software when building a Connext application Patch not required to run the application d Only C and C APIs are supported Table 3 3 lists the compiler flags and the libraries you will need to link into your application Table 3 2 provides details on the environment variables that must be set at run time for an INTEGRITY architecture Table 3 4 provides details on how the libraries were built This table is provided strictly f
99. n 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 Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 7 O Wall Debug Wno unknown pragmas DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM c Wp MD ccpentium m32 march pentium fno builtin ansi DCPU PENTIUM Static or DTOOL FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 Dynamic O DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 8 Wall Release Wno unknown pragmas DRTS_VXWORKS DPtrIntIype long DCSREAL IS FLOAT DNDEBUG Wp MD pentiumVx6 8gcc4 1 2 ccpentium m32 march pentium fno builtin ansi DCPU PENTIUM Static or DTOOL FAMILY gnu DTOOL gnu D WRS KERNEL D PROTOTYPE 5 0 g Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 8 Wall Debug Wno unknown pragmas DRTS_VXWORKS DPtrIntType long DCSREAL_IS_FLOAT Wp MD ccpentium m32 march pentium ansi DCPU PENTIUM DTOOL_FAMILY gnu Static or DTOOL gnu mrtp D__PROTOTYPE_5_0 O Wall Wno unknown pragmas Dynamic DRTS_VXWORKS DVXWORKS_MAJOR_VERSION 6 Release DVXWORKS MINOR VERSION 8 DPtrIntType long DCSREAL_IS_FLOAT DNDEBUG Wp MD pentiumVx6 8gcc4 1 2 rtp ccpentium m32 march pentium ansi DCPU PENTIUM DTOOL FAMILY gnu Static or DTOOL gnu mrtp D__ PROTOTYPE 5 0 g Wall Wno unknown pragmas Dynamic DRTS_VXWORKS DVXWORKS MAJOR VERSION 6 Debug
100. nd providing an implementation that returns ERROR and sets errno to ENOSYS For the function prototype refer to the file sdLibCom mon h in the VxWorks distribution In addition to providing the symbol stubs for sdOpen and sdUnmap we also recommend dis abling the SHMEM transport by using the transport_builtin mask in the QoS configuration Monotonic Clock Support The monotonic clock described in Section 8 6 in the RTI Core Libraries and Utilities User s Manual is supported on VxWorks 6 3 and higher architectures This feature is not supported on VxWorks 653 2 3 or VxWorks MILS platforms Thread Configuration Table 9 3 lists the thread settings for VxWorks platforms Table 9 4 and Table 9 5 list the thread priority definitions and thread kinds respectively Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Section 19 5 in the RTI Core Libraries and Utilities User s Manual is not available for VxWorks platforms Thread Setting for VxWorks Platforms Applies to Kernel Tasks or Real Time Process Threads Applicable Thread DDS ThreadSettings t Platform Specific Setting mask OS default thread type Asynchronous Publisher priority 110 Asynchronous flushing stack size 4 16 1024 thread cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported mask DDS THREAD SETTINGS STDIO priority 120 Database
101. nddscorezd dba For Connext Messaging also include librticonnextmsgcppzd a libnddscz a libnddscorez a For Connext Messaging also include librticonnextmsgcz a Static Debug libnddsczd a libnddscorezd a libnddsczd dba libnddscorezd dba For Connext Messaging also include librticonnextmsgczd a libsocket a libnet a libposix a RII INTY exceptions a The Connext C C libraries are located in NDDSHOME lib architecture where NDDSHOME is where Connext is installed such as local rti ndds 5 x y b Transports other than the default IP transport such as StarFabric may require linking in additional libraries For fur ther details see the online documentation or contact support rti com c 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 Library Creation Details for INTEGRITY Architectures RTI Architecture Library Format Compiler Flags Used by RTI p4080Integrity10 0 2 xes bsp xes p4080 smp prefixed_msgs Static unknown_pragma_silent link_once_templates Release fexceptions O DPtrIntType long DCSREAL_IS_FLOAT DCPU p4080 DNDEBUG p4080 smp bsp xes p4080 smp prefixed_msgs Static unknown_pragma_silent link_once_templates Debug fexceptions G DPtrIntType long DC
102. ng thread beginthreadaffinity aspx When you are done making RTI calls from a given thread you should call Thread EndThread Affinity In any case be sure to consult the RTI API documentation for more information about the thread safety contracts of the operations you use 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 documentation for more information 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 sup port TCP IPv4 Supported on architectures that use Visual Studio This is not a built in transport Monotonic Clock Support The monotonic clock described in Section 8 6 in the RTI Core Libraries and Utilities User s Manual is supported Thread Configuration Table 10 2 lists the thread settings for Windows platforms Table 10 3 and Table 10 4 list the thread priority definitions and thread kinds respectively Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity des
103. nnext 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 Table47 Library Creation Details for Linux and Fedora Architectures Library RTI Architecture porche Compiler Flags Used by RTI atic Dynamic O3 fPIC mminimal toc mcpu cell mtune cell DLINUX Wall Rel Wno unknown pragmas DRTS_UNIX DPtrIntType long eease DCSREAL IS FLOAT DCPU cell DTARGET cell64Linux2 6gcc4 5 1 DNDEBUG c Wp MD cell64Linux2 6gcc4 5 1 O3 fPIC mminimal toc mcpu cell mtune cell DLINUX g Wall Deb Wno unknown pragmas DRTS_UNIX DPtrIntType long ous DCSREAL IS FLOAT DCPU cell DTARGET cell64Linux2 6gcc4 5 1 c Wp MD fPIC DLINUX O Wall Wno unknown pragmas DRIS UNIX Release DPtrIntType long DCSREAL_IS_FLOAT DCPU 180586 DTARGET i86Linux2 6gcc3 4 3 fmessage length 0 i86Linux2 6gcc3 4 3 DNDEBUG c Wp MD fPIC DLINUX g Wall Wno unknown pragmas DRTS_UNIX Debug DPtrIntType long DCSREAL_IS_FLOAT DCPU 180586 DTARGET i86Linux2 6gcc3 4 3 fmessage length 0 c Wp MD fPIC DLINUX O Wall Wno unknown pragmas DRTS_UNIX DPtrIntType long DCSREAL_IS_FLOAT DCPU I80586 DTARGET i86Linux2 6gcc4 1 1 fmessage length 0 i86Linux2 6gcc4 1 1 DNDEBUG c Wp MD Release fPIC DLINUX g Wall Wno unknown pragmas DRTS_UNIX Debug D
104. nu DPtrIntType long DCPU PENTIUM c Wp MD 55 VxWorks Platforms 99 Library Creation Details for All VxWorks Architectures RTI Architecture Library Format Compiler Flags Used by RTI pentiumVx6 7gcc4 1 2 Static or Dynamic Release 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 march pentium fno builtin ansi DTOOL gnu D_WRS_KERNEL Static D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 7 O Wall Wno unknown pragmas Debug DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM c Wp MD march i486 ansi DTOOL gnu mrtp D PROTOTYPE 5 0 Static DVXWORKS MAJOR VERSION 26 DVXWORKS MINOR VERSION 7 Release Wall Wno unknown pragmas DRTS VXWORKS DTOOL_FAMILY gnu DPtrIntType long DCPU PENTIUM DNDEBUG c Wp MD march i486 ansi DTOOL gnu mrtp D PROTOTYPE 5 0 g Static DVXWORKS MAJOR VERSION 26 DVXWORKS MINOR VERSION 7 O Wall Debug Wno unknown pragmas 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 Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 7 Wall Release Wno unknow
105. o builtin ansi DTOOL gnu D WRS KERNEL Static D PROTOTYPE 5 0 DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas Release DRTS VXWORKS DTOOL FAMILY gnu DPtrIntIype long DCPU PENTIUM DNDEBUG c Wp MD pentiumVx6 6gcc4 1 2 E march pentium fno builtin ansi DTOOL gnu D WRS KERNEL Static or D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 6 Dynamic DVXWORKS MINOR VERSION 6 O Wall Wno unknown pragmas Debug DRTS VXWORKS DTOOL FAMILY gnu DPtrIntType long DCPU PENTIUM c Wp MD march i486 ansi DTOOL gnu mrtp D PROTOTYPE 5 0 Static DVXWORKS MAJOR VERSION 26 DVXWORKS MINOR VERSION 6 O Wall Release Wno unknown pragmas DRTS VXWORKS DTOOL_FAMILY gnu DPtrIntType long DCPU PENTIUM DNDEBUG c Wp MD march i486 ansi DTOOL gnu mrtp D PROTOTYPE 5 0 g Static DVXWORKS MAJOR VERSION 26 DVXWORKS MINOR VERSION 6 O Wall Debug Wno unknown pragmas 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 Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Release Wno unknown 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 Dynamic DVXWORKS MAJOR VERSION 6 DVXWORKS MINOR VERSION 6 O Wall Debug Wno unknown pragmas DRTS VXWORKS DTOOL FAMILY g
106. o tn tn tensa tantae 15 41 Multicast Supports ERR RISO RR YR ese i Oe 17 42 Supported Transports sessi eee pet iei eee te HIER FFY FFF 17 43 Monotonic Clock SUpPort c ccccssssssessesesesscecnseseseserseessesenscsessssacastecnssessnesetacacncenssedessesasensscoeescadsesenees 18 AA Thread Configuration tee tnter tere tirer tret et erii 18 45 Durable Writer History and Durable Reader State Features sss 19 4 6 Libraries Required for Using RTI Secure WAN Transport APIs 19 47 Libraries Required for Using RTI TCP Transport APlIs sess 19 LynxOS T 26 Belt c Multicast SUpport sauer nere ipee nene e e ie i NAD 29 52 gt Supported Transports snot e E eei dete eere dene cn ere doe there Ee eres 29 53 Fragmentation Issues 30 54 Monotonic Clock Support rnnt n peter ederet ie nnde e ederet ere eR a 30 5 2 Thread Configurations pee ee ertt ec p d tears 30 5 6 Durable Writer History and Durable Reader State Features sse 31 Mac OS Platforms e aree eere eese ee tee eae ino es et seen 31 6 1 Mu lticast Support ie niee ihe onm de ere e et e a nee ET CY rre i iere ats 34 6 2 Supported Transports sisi red recte ee eee nene WG eee e ee 34 63
107. onnext can run on all four CPUs provided the following hold true 1 Connext applications on CPUs B C and D only exchange data with applications on a dif ferent CPU or off board 1 The IP backplane and associated routing has been properly configured Connext has been tested with the following libraries built into the INTEGRITY kernel debug res load socket itcpip Ibp queue ifbp idb bsl Multi NIC Support on INTEGRITY 5 0 Due to limitations with the API of the InterPeak stack for INTEGRITY 5 0 Connext 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 reconfiguring the kernel This limitation does not affect the InterNiche stack Multicast Support Multicast is supported on all INTEGRITY 5 0 and 10 0 platforms 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 Out of the box Transport Compatibility with Other Connext 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 buffer size for the shared memory transport are dif ferent than those for other platfo
108. or infor mational 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 Running Instructions for INTEGRITY Architectures RTI Architecture Required Environment Variables All INTEGRITY architectures None Patch Required for INTEGRITY 10 02 Platform To run a Connext application on an INTEGRITY 10 0 2 system you must install patch 6901 iff from Green Hills Software For more information please contact your Green Hills Software rep resentative Support for Request Reply Communication Pattern RTI Connext Messaging includes support for the Request Reply Communication Pattern for the platforms described in Table 3 1 and all programming languages except as noted below When using C the following platform does not support the Request Reply Communication Pattern ppc85xxInty5 0 11 xes p2020 1 p4080Integrity10 0 2 xes p4080 smp INTEGRITY Platforms Table 3 3 Table 3 4 Building Instructions for INTEGRITY Architectures API Library Format Required RTI Libraries Required System Libraries Required Compiler Flags C Static Release libnddscppz a libnddscz a libnddscorez a For Connext Messaging also include librticonnextmsgcppz a Static Debug Static Release libnddscppzd a libnddsczd a libnddscorezd a libnddscppzd dba libnddsczd dba lib
109. ority Asynchronous Publisher stack size OS default thread stack size Asynchronous flushing list Empty CPU list Supported on Linux SUSE and thread spec Fedora platforms DDS THREAD SETTINGS CPU NO ROTATION even Supported on Linux SUSE and Fedora platforms mask DDS_THREAD_SETTINGS_STDIO priority OS default thread priority stack_size OS default thread stack size Database thread Empty CPU list Supported on Linux SUSE and cpu list Fedora platforms olds DDS THREAD SETTINGS CPU NO ROTATION Supported on Linux SUSE and Fedora platforms mask DDS_THREAD_SETTINGS_STDIO DDS THREAD SETTINGS FLOATING POINT priority OS default thread priority NOL stack size OS default thread stack size cpu Jist Empty CPU list Supported on Linux SUSE and Fedora platforms cpu rotation DDS THREAD SETTINGS CPU NO ROTATION Supported on Linux SUSE and Fedora platforms 25 LynxOS Platforms Table 4 11 Table 4 12 Thread Priority Definitions for Linux and Fedo Thread Settings for Linux and Fedora Platforms Applicable Thread DDS ThreadSettings t Platform Specific Setting DDS THREAD SETTINGS STDIO Hime DDS THREAD SETTINGS FLOATING POINT priority OS default thread priority ReceiverPool threads stack_size OS default thread stack size cpu list Empty CPU list Supported on Linux SUSE and Fedora platforms cpu_rotation DDS_THREAD_SETTINGS_CPU_NO_ROTATION
110. ory and Durable Reader State features are not supported on QNX plat forms Restarting Applications on QNX Systems Due to a limitation in the POSIX API if a 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 auto matically release the semaphore making it impossible to reuse it by another application The Connext shared memory transport uses a shared mutex to protect access to the shared mem ory 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 domain 39 Solaris Platforms 8 Table 8 1 Table 8 2 Solaris Platforms Table 8 1 lists the architectures supported on Solaris operating systems Supported Solaris Platforms Operating Compiler or System SEU Software Development Kit TATA CHIC x86 gcc 3 3 2 i86Sol2 9gcc3 3 2 Solaris 2 9 UItraSPARC CC 5 4 Forte Dev 7 Sun One Studio 7 sparcSol2 9cc5 4 gcc3 4 2 sparcSol2 10gcc3 4 2 UltraSPARC Java Platform Standard Edition JDK 1 7 sparcSol2 10jdk Solaris 10 UltraSPARC gcc342 sparc64Sol2 10gcc3 4 2
111. otal number of semaphores within any and all groups Each Connext applica tion that has shared memory enabled allocates 4 groups of 1 semaphore each per domain So setting the two values to the same number will work fine as far as Connext is concerned How ever if other applications in the system want to allocate bigger groups you could set sem sys seminfo semmns larger than semsys 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 using them having 100 System V semaphores will allow you to use 25 domain ID participant index combinations for Connext applications You probably will not need to increase the shared memory parameters since the default allows 100 shared memory areas enough for 50 applications Monotonic Clock Support The monotonic clock described in Section 8 6 in the RTI Core Libraries and Utilities User s Manual is supported on all Solaris architectures 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 package If you choose to use it it must be downloaded and installed separately It is only available on specific architectures See the RTI Secure WAN Trans port Release Notes and RTI Secure WAN Transport Release Notes Installation Guide for details To use the WAN or Secure
112. pcs m grep 0x004 The shared semaphore keys used by Connext 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 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 limited by the size of the MTU on this interface which by default is 16384 bytes Since the default message 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 command ifconfig 100 mtu 65535 Note The maximum size of the MTU on the loopback interface is 65535 which will allow RTPS payloads of 65507 bytes For more information on this issue contact LynuxWorks Support about bug 30191 Monotonic Clock Support The monotonic clock described in Section 8 6 in the RTI Core Libraries and Utilities User s Manual is not supported on LynxOS platforms Thread Configuration Table 5 6 lists the thread settings for LynxOS platforms Table 5 7 lists th
113. piler Flags Used by RTI Dynamic mcpu 7400 maltivec mabi altivec fno exceptions mthreads mshared fPIC D_POSIX_THREADS_CALLS Release D__ NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntIype long DCSREAL 15 FLOAT DCPU PPC7400 DTARGET ppc7400Lynx5 0 0gcc3 4 3 DNDEBUG c Wp MD mcpu 7400 maltivec mabi altivec fno exceptions mthreads mshared fPIC D POSIX THREADS CALLS Debug D__ NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntType long DCSREAL 15 FLOAT DCPU PPC7400 DTARGET ppc7400Lynx5 0 0gcc3 4 3 c Wp MD mcpu 750 fno exceptions mthreads mshared fPIC D POSIX THREADS CALLS D NO INCLUDE WARN O Wall Wno unknown pragmas DPtrIntType long DCPU PPC750 DTARGET ppc750Lynx4 0 0gcc3 2 2 DNDEBUG c Wp MD mcpu 750 fno exceptions mthreads mshared fPIC D POSIX THREADS CALLS D NO INCLUDE WARN g O Wall Wno unknown pragmas DPtrIntType long DCPU PPC750 DTARGET ppc750Lynx4 0 0gcc3 2 2 c Wp MD ppc7400Lynx5 0 0gcc3 4 3 Release ppc750Lynx4 0 0gcc3 2 2 Debug 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 multi cast 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
114. pport see Table 4 10 on page 25 Select the files appropriate for your chosen library format 1 RTI CoreLibrariesAndUtilities GettingStarted DatabaseAddendum pdf Linux and Fedora Platforms Table 4 5 Building Instructions for Linux and Fedora Architectures API Library T Md ut Required Required Format Jar Files System Libraries Compiler Flags libnddscppz a libnddscz a Static libnddscorez a Release For Connext Messaging also include librticonnextmsgcz a libnddscppzd a For all Linux2 6gcc3 Sai libnddsczd a architectures atic libnddscorezd a dl Insl Debug ae 64 bit architectures For Connext Messaging also include L usr lib nptl DRTI UNIX m64 librticonnextmsgcppzd a lpthread lrt C libnddscpp so ___ libnddsc so All other Linux y i eid s libnddscore so architectures elease For Connext Messaging also include ldl Insl Im librticonnextmsgcpp so lpthread lrt libnddscppd so libnddscd so Dynamic Iipnddscored so Debug a For Connext Messaging also include librticonnextmsgcppd so libnddscz a Static libnddscorez a Release For Connext Messaging also include librticonnextmsgcz a For all Linux2 6gcc3 libnddsczd a architectures Static libnddscorezd a Idl Insl Im a Debug For Connext Messaging also include L usr lib nptl bee librticonnextmsgczd a lpthread lrt libnddsc so
115. pragma warning pop These warnings do not compromise the final application produced and can be safely ignored Warning when Loading Connext Applications on INTEGRITY Systems When a Connext application compiled with the rtiddsgen generated project files is loaded on an INTEGRITY 5 0 x target the following warning appears Warning Program is linked with libc so POSIX signals and cancellation will not work The Connext libraries do not use the additional features provided by the full POSIX implementa tion therefore the warning can safely be ignored This warning is due to the fact that the rtidds gen generated project files use the Single AddressSpace POSIX library by default not the full POSIX implementation on INTEGRITY POSIX System The Connext libraries only require Sin gle AddressSpace POSIX to function correctly but will still work if you are using the POSIX Sys tem 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 Linux and Fedora Platforms First see the basic instructions for compiling on Linux platforms provided in Section 9 3 in the RTI Core Libraries and Utilities User s Manual The following tables provide supplemental infor mation Table 4 1 through Table 4 4 list the supported Linux and Fedora architectures L
116. re NDDSHOME is where Connext is installed such as local rti ndds 5 x y AIX Platforms b Transports other than the default IP transport such as StarFabric may require linking in additional libraries For fur ther details see the online documentation or contact support rti com c Use g32 if you build 32 bit code or q64 for 64 bit code d The gthreaded option is automatically set if you use one of the compilers that ends with r such as cc r xlc xlC_r See the IBM XLC reference manual for more information Table 2 3 Running Instructions for AIX Architectures Library RTI Architecture pes Required Environment Variables amp Debug 64p7AIX7 1xlc12 1jdk N A LIBPATH NDDSHOME lib lt arch gt LIBPATH EXTSHM ONP All other supported Static EXTSHM ON architectures Dynamic LIBPATH NDDSHOME lib lt arch gt LIBPATH EXTSHM ON a MNDDSHOMEF represents the root directory of your Connext installation LIBPATH represents the value of the LIB PATH variable prior to changing it to support Connext 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 nddsja vad jar the JVM will attempt to load debug versions of the native libraries nddsjava so nddscore so nddsc so b See Notes for Using Shared Memory Section 2 2 1 Table 2 4 Library Creation Detail
117. rms This will cause out of the box compatibility issues that may result in lack of communication For more information on transport incompatibility see Section 2 5 Transport Compatibility in the RTI Core Libraries and Utilities Release Notes The mis INTEGRITY Platforms 3 8 1 3 8 2 match in transport configuration between INTEGRITY and other platforms applies to Connext 5 1 0 and higher To address the compatibility issues you can change the default transport settings of other plat forms to match those of the INTEGRITY platform Alternatively you can update the INTEG RITY kernel parameters as described below so that the INTEGRITY platform will support larger transport settings The directive 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 networking pdf manual provided with the INTEGRITY kernel The default value of GM IP FRAG ENTRY MAX SIZE is 9216 bytes not 16 000 bytes as is stated in the INTEG RITY 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
118. rtp VxWorks 6 5 Any Wind River PPC32 CPU with floating point hardware gcc 3 4 4 For kernel modules ppc604Vx6 5gcc3 4 4 For Real Time Processes ppc604Vx6 5gcc3 4 4_rtp VxWorks 6 6 Pentium gcc 4 1 2 For Kernel Modules pentiumVx6 6gcc4 1 2 For Real Time Processes pentiumVx6 6gcc4 1 2_rtp Any Wind River PPC32 CPU with floating point hardware gcc 4 1 2 For Kernel Modules ppc604Vx6 6gcc4 1 2 For Real Time Processes ppc604Vx6 6gcc4 1 2_rtp PPC 405 gcc 4 1 2 For Kernel Modules ppc405Vx6 6gcc4 1 2 For Real Time Processes ppc405Vx6 6gcc4 1 2 rtp VxWorks 6 7 Pentium gcc 4 1 2 For Kernel Modules pentiumVx6 7gcc4 1 2 For Real Time Processes pentiumVx6 7gcc4 1 2 rtp Any Wind River PPC32 CPU with floating point hardware gcc 4 1 2 For Kernel Modules ppc604Vx6 7gcc4 1 2 For Real Time Processes on non SMP systems ppc604Vx6 7gcc4 1 2 rtp For Real Time Processes on SMP systems ppc604Vx6 7gcc4 1 2_smp PPC 405 gcc 4 1 2 For Kernel Modules ppc405Vx6 7gcc4 1 2 For Real Time Processes ppc405Vx6 7gcc4 1 2 rtp 46 VxWorks Platforms Table 9 1 Supported VxWorks Target Platforms Operating System CPU Compiler RTI Architecture For Kernel Modules pentiumVx6 8gcc4 1 2 Pentium gcc 4 1 2 For Real Time Processes entiumVx6 8gcc4 1 2 r VxWorks 6 8 P 8 ttp For Kernel Modules Any Wind River PPC32 C
119. s Platforms Thread Priority Definition Operating System Priority THREAD PRIORITY DEFAULT THREAD PRIORITY HIGH THREAD PRIORITY ABOVE NORMAL THREAD PRIORITY NORMAL THREAD PRIORITY BELOW NORMAL THREAD PRIORITY LOW 4 Thread Kinds for Windows Platforms Thread Kinds Operating System Configuration DDS THREAD SETTINGS FLOATING POINT DDS THREAD SETTINGS STDIO DDS THREAD SETTINGS REALTIME PRIORITY DDS THREAD SETTINGS PRIORITY ENFORCE N A a See Windows manuals for additional information ODBC Database Compatibility To use the Durable Writer History and Durable Reader State features you must install a rela tional database such as MySQL In principle you can use any database that provides an ODBC driver since ODBC is a standard How ever 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 L MySQL ODBC 5 1 44 Note 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 69 Windows Platforms 10 9 10 10 10 11 The Durable Writer History and Durable Reader State features have been tested with the follow ing architectures i86Win32VS2005 i86Win32VS2008 i86Win32VS2010 x64Win64VS2010 For
120. s for AIX Architectures Library RTI Architecture Format Compiler Flags Used by RTI Static amp Dynamic q32 qlongdouble qalias noansi qpic large qthreaded Release D POSIX C SOURCE 199506L D_EXTENSIONS_ O qflag i i DPtrIntType long DCSREAL IS FLOAT DCPU Power5 p5AIX5 3xlc9 0 DNDEBUG q32 qlongdouble qalias noansi qpic large qthreaded Debug D POSIX C SOURCE 199506L D__EXTENSIONS__ O qflag i i DPtrIntType long DCSREAL IS FLOAT DCPU Power5 g q64 qwarn64 glongdouble qalias noansi qpic large qthreaded D POSIX C SOURCE 199506L D EXTENSIONS O qflag i i DPtrIntType long DCSREAL IS FLOAT DCPU Power5 64p5AIX5 3xlc9 0 DNDEBUG g64 qwarn64 glongdouble qalias noansi qpic large qthreaded Debug D POSIX C SOURCE 199506L D EXTENSIONS O qflag i i DPtrIntType long DCSREAL IS FLOAT DCPU Power5 g q64 gwarn64 glongdouble qalias noansi qpic large qthreaded D POSIX C SOURCE 199506L D EXTENSIONS O qflag i i DPtrIntType long DCSREAL IS FLOAT DCPU Power7 64p7AIX7 1xlc12 1 DNDEBUG q64 qwarn64 glongdouble qalias noansi qpic large qthreaded Debug D POSIX C SOURCE 199506L D EXTENSIONS O qflag i i DPtrIntType long DCSREAL IS FLOAT DCPU Power7 g All supported AIX Release target 1 4 source 1 4 architectures for Java Release Release Debug target 1 4 source 1 4 g a Connext was built using the XIC r compiler See IBM s
121. s ndds 5 x y Table 8 3 Running Instructions for Solaris Architectures Library RTI Architecture Format Environment Variables Release amp Debug LD_LIBRARY_PATH All supported Solaris N A NDDSHOME lib architecture LD LIBRARY PATH a architectures for Java Note For all 64 bit Java architectures 64 jdk use d64 in the com mand line Static None required All supported Solaris LD LIBRARY PATH ti hitect i m architectures Dynamic g NDDSHOME lib architecture 12 LIBRARY PATH a NDDSHOME represents the root directory of your Connext installation LD LIBRARY PATH represents the value of the LD_LIBRARY_PATH variable prior to changing it to support Connext When using nddsjava jar the Java virtual machine JVM will attempt to load release versions of the native libraries When using nddsjavad jar the JVVM will attempt to load debug versions of the native libraries 4 Solaris Platforms Table8 4 Library Creation Details for Solaris Architectures 8 1 RTI Architecture Dey Compiler Flags Used by RTI Format Static D_POSIX_C_SOURCE 199506L D__EXTENSIONS__ DSolaris2 DSVR5 and DSUN4_SOLARIS2 O Wall Wno unknown pragmas fPIC DRTS_UNIX Dynamic DPtrIntType long DCSREAL_IS_FLOAT DCPU i386 Release DTARGET i86So12 9 cc3 3 2 DNDEBUG c Wp MD Wp i86Sol2 9gcc3 3 2 Static D POSIX C SOURC
122. sing the optional RTI Secure WAN Transport and RTI TCP Transport respectively 4 1 Multicast Support Multicast is supported on all Linux and Fedora 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 documentation for more information 4 2 Supported Transports Shared memory Supported and enabled by default To clean up shared memory resources reboot the kernel UDPv4 Supported and enabled by default UDPve Supported for all platforms listed in Table 4 2 through Table 4 4 except SELinux 2 6 32 kernel ppc4xxFPLinux2 6gcc4 5 1 and Raspbian Wheezy 7 0 armv6vfphLinux3 xgcc4 7 2 The UDPv6 transport is not enabled by default and the peers list must be modified to sup port IPv6 Note Traffic Class support is only provided on architectures with gcc 4 1 0 or later that sup port the UDPv6 transport Linux and Fedora Platforms 4 2 1 4 3 4 4 4 4 1 TCP IPv4 Supported on CentOS 5 4 and higher Red Hat Enterprise Linux 5 0 and higher except Red Hat Enterprise Linux 5 2 with Real Time Extensions and Ubuntu Server 10 04 This is not a built in transport Shared Memory Support To see a list of shared memory resources in use please use the ipcs command To clean up shared memory and shared semaphore resources please use the ipcrm command The shared memory keys used by Connext are in the range of
123. sions of the Microsoft run time libraries available your application will fail to start up properly If you start it from a command shell you will see an error about a failure to load the dynamic libraries Fortunately you do not need to use the RTI debug libraries to debug your own code If you experience library loading problems when your Java or NET application starts up in debug mode modify your application project files to use the release versions of the RTI libraries Alter natively you can obtain a no cost version of Visual Studio 2005 directly from Microsoft which will contain the necessary debug libraries NET API Requires Thread Affinity To maintain proper concurrency control NET threads that call a Connext 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 SOL Server does this or you may do so in your own application If you intend to call Connext APIs from explicitly managed threads you must first call Thread BeginThreadA ffinity in each such thread to ensure that it remains attached to a single 1 RTI Connext NET language binding is currently supported for Cf and C CLI 67 Windows Platforms 10 4 10 5 10 6 10 7 10 7 1 operating system thread See http msdn microsoft com en us library system thread i
124. strict align m32 mregnames ansi mlongcall DCPU PPC32 Static or DTOOL_FAMILY gnu DTOOL gnu te500v2 mcpu 8548 mfloat gprs double Dynamic mspe yes mabi spe mrtp D__PROTOTYPE_5_0 O2 fno strict aliasing Wall Release Wno unknown pragmas DRTS_VXWORKS DVXWORKS_MAJOR_VERSION 6 DVXWORKS_MINOR_VERSION 9 DPtrIntType long DCSREAL_IS_FLOAT DNDEBUG Wp MD ppce500v2Vx6 9gcc4 3 3 rtp ccppc mstrict align m32 mregnames ansi mlongcall DCPU PPC32 Static or DTOOL_FAMILY gnu DTOOL gnu te500v2 mcpu 8548 mfloat gprs double Dynamic mspe yes mabi spe mrtp D PROTOTYPE 5 0 g Wall Debu Wno unknown pragmas DRTS_VXWORKS DVXWORKS_MAJOR_VERSION 6 8 DVXWORKS_MINOR_VERSION 9 DPtrIntType long DCSREAL IS FLOAT Wp MD Static or DTOOL_FAMILY gnu DTOOL gnu mlongcall Wall G 0 fno builtin mlongcall Dynamic D_WRS_KERNEL D__PROTOTYPE_5_0 DVXWORKS_MAJOR_VERSION 5 m DVXWORKS MINOR VERSION 5 O Wno unknown pragmas DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU PPC604 DNDEBUG c Wp MD sbc8641Vx653 2 3gcc3 3 2 DTOOL FAMILY gnu DTOOL gnu mlongcall Wall G 0 fno builtin mlongcall Static D WRS KERNEL D PROTOTYPE 5 0 g DVXWORKS MAJOR VERSION 5 Dynamic DVXWORKS MINOR VERSION 5 Wall Wno unknown pragmas Debug DRTS VXWORKS DPtrIntType long DCSREAL IS FLOAT DCPU PPC604 c Wp MD DTOOL_FAMILY gnu DTOOL gnu DCPU SIMNT Wall nostdlib fno defer pop Static or fno builtin mcpu pentium D_WRS_KERNEL D__PRO
125. thread stack size 16 1024 cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported 50 VxWorks Platforms Table9 3 Thread Setting for VxWorks Platforms Applies to Kernel Tasks or Real Time Process Table 9 4 Table 9 5 7 9 9 10 Threads Applicable Thread DDS_ThreadSettings_t Platform Specific Setting DDS_THREAD_SETTINGS_STDIO mask DDS_THREAD_SETTINGS_FLOATING_POINT priority 110 stack size 4 16 1024 cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO uad DDS THREAD SETTINGS FLOATING POINT priority 71 ReceiverPool threads saccis 4161024 cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported Thread Priority Definitions for VxWorks Platform S Thread Priority Definition Operating System Priority THREAD PRIORITY DEFAULT 100 THREAD PRIORITY HIGH 68 THREAD PRIORITY ABOVE NORMAL 71 THREAD PRIORITY NORMAL 100 THREAD PRIORITY BELOW NORMAL 110 THREAD PRIORITY LOW 120 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 calling taskSpawn Kernel mode only DDS THREAD SETTINGS REALTIME PRIORITY Conf
126. ual is not supported on Mac OS platforms Thread Configuration Table 6 5 lists the thread settings for MAC OS platforms Table 6 6 lists the thread priority definitions Support for Controlling CPU Core Affinity for RTI Threads Support for controlling CPU core affinity described in Section 19 5 in the RTI Core Libraries and Utilities User s Manual is not available for Mac OS platforms Table 6 5 Thread Settings for MAC OS Platforms Applicable Thread DDS ThreadSettings t Platform Specific Setting mask OS default thread type Asynchronous Publisher priority OS default thread priority Asynchronous flushing stack size OS default thread stack size thread cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported 34 QNX Platforms Table 6 5 Table 6 6 6 5 Table 7 1 Thread Settings for MAC OS Platforms Applicable Thread DDS ThreadSettings t Platform Specific Setting mask 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 mak DDS_THREAD_SETTINGS_STDIO DDS_THREAD_SETTINGS_FLOATING_POINT priority OS default thread priority Event thread stack_size OS default thread stack size cpu list CPU core affinit
127. ult thread priority deca d stack_size OS default stack size cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported mask 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 38 QNX Platforms Table 7 5 Table 7 6 7 6 7 7 Thread Settings for QNX Platforms Applicable Thread DDS ThreadSettings t Platform Specific Setting DDS THREAD SETTINGS STDIO mask DDS THREAD SETTINGS FLOATING POINT ia priority OS default thread priority 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 mask DDS THREAD SETTINGS FLOATING POINT ReceiverPool threads priority OS default thread priority stack_size OS default thread stack size cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported Thread Priority Definitions for QNX Platforms Thread Priority Definition Operating System Priority THREAD_PRIORITY_DEFAULT 10 THREAD_PRIORITY_HIGH 60 THREAD_PRIORITY_ABOVE_NORMAL 40 THREAD_PRIORITY_NORMAL 10 THREAD_PRIORITY_BELOW_NORMAL 9 THREAD_PRIORITY_LOW Durable Writer History and Durable Reader State Features The Durable Writer Hist
128. with native 64 bit support Java Platform Standard Edition JDK 1 7 sparc64Sol2 10jdk Table 8 2 lists the compiler flags and the libraries you will need to link into your application See also VxWorks Platforms Section 9 Table 8 3 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 8 4 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 applica tion You may find this information useful if you are involved in any in depth debugging Building Instructions for Solaris Architectures API Library RTI Libraries or Jar Files Required System Required Compiler Format Libraries Flags libnddscz a Static libnddscorez a Release For Connext Messaging also include librti t der sparc64Sol2 10gcc3 4 2 141 Insl Isocket tati ibnddscorezd a ik lgen 1 4 sparc64Sol2 10gcc3 4 2 PS For Connext Messaging also include Ipthread Im lc DRTI UNIX m64 librticonnextmsgczd a C palais All other architectures Aj other architectures Dynamic libnddscore so ldl Insl lgenIO DRTI UNIX m32 Release For Connext Messaging also include Isocket Igen librticonnextmsgc so Iposix4 Ipthread Im lc libnddscd so Dyna
129. y not supported cpu rotation CPU core affinity not supported DDS THREAD SETTINGS STDIO mask DDS_THREAD_SETTINGS_FLOATING_POINT priority OS default thread priority ReceiverPool threads stack_size OS default thread stack size cpu_list CPU core affinity not supported cpu_rotation CPU core affinity not supported Thread Priority Definitions for MAC OS 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 Durable Writer History and Durable Reader State Features The Durable Writer History and Durable Reader State features are not supported on Mac OS platforms QNX Platforms Table 7 1 lists the architectures supported on QNX operating systems Supported QNX Platforms Operating System CPU Compiler RTI Architecture QNX Neutrino 6 4 1 x86 4 3 3 with GNU C libraries iSGONX6 4 1gcc_gpp QNX Neutrino 6 5 x86 gcc 4 4 2 with GNU C libraries i86QNX6 5qcc_gpp4 4 2 a For use with Windows Linux or Solaris Host as supported by QNX amp RTI 35 QNX Platforms Table 7 2 Table 7 2 lists the libraries you will need to link into your application Table 7 3 provides details on the environment variables that must be set at run time for a ONX architecture Table 7 4 provides details on how the ONX libraries were bui
130. z a Static libnddscorez a Release For Connext Messaging also include librticonnextmsgcppz a libnddscppzd a libnddsczd a Static libnddscorezd a Debug For Connext Messaging also include librticonnextmsgcppzd a on libnddscpp so libnddsc so Dynamic libnddscore so Release For Connext Messaging also include librticonnextmsgcpp so The MILS 2 1 1 patch that libnddscppd so corrects defect number libnddscd so WIND00343321 must be Dynamic libnddscored so installed for Connext Debug libraries to work on a DRTI VXWORKS For Connext Messaging also include librti d MILS 2 1 1 system This FFF a patch can be obtained libnddscz a through the regular Wind Static libnddscorez a River support channel Release For Connext Messaging also include librticonnextmsgcz a libnddsczd a Static libnddscorezd a Debug For Connext Messaging also include C librticonnextmsgczd a libnddsc so Dynamic libnddscore so Release For Connext Messaging also include librticonnextmsgc so libnddscd so Dynamic libnddscored so Debug For Connext Messaging also include librticonnextmsgcd so a The Connext C C libraries are located in NDDSHOME lib lt architecture gt where NDDSHOME is where Connext is installed such as c rti ndds 5 x y 54 VxWorks Platforms 99 Library Creation Details for All VxWorks Architectures RTI Architecture HUAN Compiler
131. ze OS default thread stack size cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported ReceiverPool threads DDS THREAD SETTINGS STDIO ns DDS THREAD SETTINGS FLOATING POINT priority OS default thread priority stack size OS default thread stack size cpu list CPU core affinity not supported cpu rotation CPU core affinity not supported 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 45 VxWorks Platforms Table 9 1 VxWorks Platforms Table 9 1 lists the architectures supported on VxWorks operating systems You can build a VxWorks application by cross compiling from your development host Supported VxWorks Target Platforms Operating System CPU Compiler RTI Architecture VxWorks 5 5 PPC 608 gcc 2 96 Ppc603Vx5 5gcc PPC 604 gcc 2 96 ppc604Vx5 5gcc PPC 750 gcc 2 96 ppc603Vx5 5gcc PPC 7400 gcc 2 96 ppc603Vx5 5gcc VxWorks 6 3 6 4 Any Wind River PPC32 CPU with floating point hardware gcc 3 4 4 For kernel modules ppc604Vx6 3gcc3 4 4 For Real Time Processes ppc604Vx6 3gcc3 4 4_

Platform Notes - Community RTI Connext Users

Contents

Download Pdf Manuals

Related Search

Related Contents