BSP Developer's Guide

6
Components
The component object includes the greatest number of properties. The more
commonly used properties are described below; definitions for the rest can be
found in E.1.1 Component Properties, p.232:
NAME
A readable name, the one that appears next to the component icon in the
project facility component hierarchy.
SYNOPSIS
A brief description of the component.
The next four properties are all related to the configuring of code in a project:
MODULES
Object files associated with the component.
CONFIGLETTES
Common configuration source files having source code that typically makes
use of parameters associated with the component.
BSP_STUBS
Generic configuration source files that are copied into the BSP directory upon
first use. The user can then make BSP-specific alterations to the copied files
without affecting other BSPs. Note that a modified stub file is shared by all
projects using the same BSP as a base.
6
NOTE: Source code can come in the form of a BSP stub. BSP stubs are supported
in Tornado 2.2; however, stubs are not supported for earlier releases of Tornado 2.x.
HDR_FILES
Header files associated with your configlette code or initialization routine.
These are header files that must be included in order for your configlette or
initialization routine to compile.
ARCHIVE
The archive file in which to find object modules stored other than in the
standard location.
The following property provides configuration information:
CFG_PARAMS
A list of configuration parameters associated with the component, typically a
list of macros. Each must be described separately by its own parameter object.
The next group of properties control integration of the component into the system
image. There is initialization information and dependency information, such as
121