QNX

“Note: This article applies to Connext DDS Professional 4.x and above” The QNX operating system provides in its SDK a front-end that calls a GCC named “qcc”. In the end, qcc will call the compiler, set the correct flags and link libraries based on the parameters that you use. The SDK provides the C ...
1044 reads — 0 comments
When you link your application with the RTI Connext DDS libraries, you can choose whether to use dynamic or static linking. But what is the best approach if you want to use the DDS Secure plug-in? There are some situations that you need to be aware of and avoid. This article describes the possible ...
1471 reads — 0 comments
Note: Applies to Connext DDS 5.x and above Sending TypeCode/TypeObject on the wire provides convenience over specifying the type via XML configuration, but has the disadvantage that more data must be sent during endpoint discovery. This can cause network congestion problems when the TypeCode/ ...
1417 reads — 0 comments
Note: Applies to RTI Connext 5.2.0 and above. The following error: PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2. This class ID does not match the class ID 16777216 of the same transport in the local participant ...
9900 reads — 7 comments
Note: Applies to RTI Connext 4.x and above. The following error: [D0004|CREATE Participant|D0004|ENABLE] NDDS_Transport_Shmem_is_segment_compatible:incompatible shared memory protocol detected. Current version 1.0 not compatible with 2.0. is caused when two applications, one using RTI Connext DDS 4 ...
3982 reads — 0 comments
Note: Applies to RTI Connext 4.x and above If you have an RTI Connext application running on a QNX machine and it is unable to communicate with other applications running on the same machine started by another user, or if your application fails to start (with an error related to shared memory), ...
3246 reads — 0 comments
Subscribe to RSS - QNX