BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
In Tornado 2.x, a code generator outputs the system configuration files, basing
them only on those components selected for configuration by the user. The overall
configuration of a project is the list of included components and their properties.
Details of how the project facility and code generator work can be found in the
Tornado User’s Guide: Projects.
In the past, you thought of components as the code and parameters included in the
system by making modifications to the configuration files (config.h or
configAll.h), as follows:
#define INCLUDE_FOO
For Tornado 2.x, you describe a component by defining its properties in a CDF, as
follows:
Component INCLUDE_FOO { // Define a component called INCLUDE_FOO.
NAME
Foo example component
SYNOPSIS This is just an example component
... // other properties
}
Component properties fall into one of the following four categories:
■
■
■
Code. This can be a combination or subset of object code (modules) and source
code (configlettes and stubs) used in the build of a project.
Configuration Information. CDL provides a rich set of properties to be used to
describe a component. These can be specified, altered, added, or eliminated.
Parameters are configurable properties expressed as data types. These are
typically preprocessor macros used within a component’s configuration code.
There is a separate CDL object used to define parameters.
Integration Information. These properties control how a component is
integrated into an executable “system image,” for example, an initialization
routine and a description of when in the initialization sequence that routine
should be called.
Integration properties also define dependencies among components, replacing
the #ifdef/#endif statements that proliferated in previous versions of
Tornado.
114