Getting Started Example - Part 3

If you inspect the Scope of various components, you will notice that for RTOS based configurations, code is generated for the entire model. But for the OORTX, which does not support active classes, the package active is disabled:

Scope for Blinky with RTOS

Scope for Blinky with OORTX

The name of a component is free to choose, but it is a good idea to use the same name as the configured RTOS, so a user of this model immediately recognizes for which environment a component is meant. The RXF is released for multiple environments; the property RXF::DeployerFolders::RTOS on the active configuration shows all supported environments.

A Deployer is used to deploy Rhapsody generated source files from your model, generated configuration files and RXF source files to your IDE project, where you can build an executable or library.
If you select the Properties tab of a component, you can select the RTOS and IDE details easily in the RXF perspective:



Results in:

The IDEProject must be set to the IDE project file where you build your executable or library.
You do not need to tell the Deployer which kind of IDE project is selected. The Deployer recognizes the IDE project by the suffix and content of the IDE project file and internally selects the correct IDE exporter.
The Deployer tab is described in detail in a dedicated section.

Please continue to the next Part 4