Download VxWorks

VxWorks 5.5
BSP Developer’s Guide
E.1.1 Component Properties
Component
NAME
232
component {
// required for all components
name
// readable name (e.g., "foo manager").
// should be in all lower case.
SYNOPSIS
desc
// one-line description
MODULES
m1 m2 ..
//
//
//
//
//
//
//
//
//
//
//
object modules making up the service.
used to generate dependency
information.
it is important to keep this list
small,since the tool’s dependency
engine assumes that the component is
included if *any* of the modules are
dragged in by dependency. It may make
sense to split a large number of
modules into several distinct
components.
CONFIGLETTES
1 s2 ..
//
//
//
//
//
source files in the component that are
#included in the master configuration
file.
file paths are assumed to be relative
to $(WIND_BASE)/target/config/comps/src
BSP_STUBS
s1 s2 ..
//
//
//
//
//
//
//
//
source file stubs that should be copied
into the BSP and customized for the
component to work.
file paths are assumed to be relative
to $(WIND_BASE)/target/config/comps/src
(BSP_STUBS are supported for Tornado 2.2
only; they are not supported in earlier
Tornado 2.x releases)
HDR_FILES
h1 h1 ..
//
//
//
//
header files that need to be included
to use this component. Typically
contains prototypes for the
initialization routine.
CFG_PARAMS
p1 p2 ..
//
//
//
//
configuration parameters, typically
macros defined in config[All].h, that
can change the way a component works.
see Parameters, below, for more info.
INIT_RTN
init(..)
// one-line initialization routine.
// if it needs to be more than one line,
// put the code in a CONFIGLETTE.
LINK_SYMS
s1 s2 ..
//
//
//
//
//
reference these symbols in order to drag
in the component from the archive.
this tells the code generator how to
drag in components that don’t need to
be initialized.