BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
SCSI drivers for that architecture, and their headers. Also included are all the
unprotected Wind River drivers in source form. It is expected that customers will
be able to download updated driver products from the Web.
10.2.1 BSP Media
Beginning with Tornado 1.0.1, all Wind River products have been packaged onto
CD-ROM media using a new combined UNIX/Windows SETUP utility. Both
UNIX and Windows users begin the installation process with the SETUP
command. All users are then presented with a consistent graphical user interface
that guides them through the product and license manager installations.
For more information, see the Tornado SETUP SDK Developer’s Guide (available
from WindSurf).
10.3 Component Packaging
Component packaging is a problem area. Wind River delivers the parts of its
components in their traditional locations:
– Source code modules are usually found in the target/src or target/config
directories.
– Headers are found in target/h; object modules are delivered in
target/lib/objARCH.
– Component description files are in target/config/comps/vxWorks.
– Component configlettes (source fragments) are in target/config/comps/src.
Third parties are not limited to this arrangement, and the location of component
elements can be fully described in the component description file. It is
recommended that third parties place their component source and object elements
in a directory, such as target/config/vendor_name. The location of the component
description file (CDF) depends on where in the system the components should be
integrated.
To integrate the new component into the full system, the CDF should be located in
target/config/comps/vxWorks. If it is a BSP-specific component, the file should be
located in the BSP directory. If it is specific to a single project, it should be located
200