Message mapping for IDL (IDL code)
For each Message, ACS generates an IDL file that contains a struct declaration for the Message. ACS generates code similar to this:
//=========================================
/// @file Package1_Message1_msg.idl
//=========================================
#ifndef MESSAGE1_MSG_IDL
#define MESSAGE1_MSG_IDL
#pragma ndds typesupport "Message1_msgSupport.h"
struct Message1_msg
{}; //@top-level true
#endif
/// @file Package1_Message1_msg.idl
//=========================================
#ifndef MESSAGE1_MSG_IDL
#define MESSAGE1_MSG_IDL
#pragma ndds typesupport "Message1_msgSupport.h"
struct Message1_msg
{}; //@top-level true
#endif
ACS uses Messages for generating the content of a Deployment Plan's Component Deployment Plan (CDP) file.
The generation of a Message in an IDL file is derived from the items it owns and properties of the Component.
Child items:• If the Message owns Attributes, ACS generates attribute declarations. For Attribute mapping information, see Attribute mapping for IDL (IDL code).
Properties:• If the Description property has a value, ACS generates the Description as a comment at the beginning of the IDL file.
• ACS generates the Name property as the name of the struct in the code.
 | ACS may modify the struct name that is added to the code to make it valid for IDL. You can specify the exact struct name to add to the code through the CODE_GENERATION_NAME property of a Message. Tell me more... |
Other properties are ignored.
Tag Definitions:Not applicable.