BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
into a component description file. The following steps taken to create the
component INCLUDE_FOO are a suggested order only; the sequence is not
mandatory. Nor is there meant to be any suggestion you use all of the properties
and object classes described.
Step 1:
Name and Provide a Synopsis
To create your new component, first name it and provide a synopsis of its utility.
Component INCLUDE_FOO {
NAME
foo component
SYNOPSIS this is just an example component
...
In the imaginary component INCLUDE_FOO, the NAME property is foo
component. SYNOPSIS informs the user that “this is just an example component.”
NAME and SYNOPSIS affect user presentation only; they have no bearing on
initialization sequence or dependencies.
Step 2:
Describe the Code-Related Elements
Next, describe your component’s code portions by defining any modules and
source configlettes that should be configured in during the build.
NOTE: BSP stubs are supported for Tornado 2.2 however, they cannot be defined
for earlier Tornado 2.x releases.
If your imaginary component INCLUDE_FOO has an object module associated
with it, use the MODULES property to specify it. You can specify any number of
modules this way. In the following example, fooLib.o and fooShow.o are listed:
...
MODULES
HDR_FILES
ARCHIVE
CONFIGLETTES
...
fooLib.o fooShow.o
foo.h
fooLib.a
fooConfig.c
Tornado 2.x offers visibility into component dependencies by graphically
presenting component relationships in the Include Components and Exclude
Components windows of the project facility (see Figure 6-4).
128