BSP Developer's Guide

10
Product Packaging
Vendor-Supplied Shared Files
Some files can appear to be target-specific when in fact they are shared by multiple
BSPs. These shared files include those described above as “generic” and
“architecture-specific,” as well as files included on the Device Driver Object
product.
The following directories are distributed with the Tornado architecture product
and the Tornado driver component product:
target/config/all
target/src/config
target/src/drv/antyhing
target/h/drv/anything
target/h/make
target/h/tool/anything
Under no circumstances may these directories and files be altered and shipped by
third-party developers. Although BSP developers are encouraged to create generic
device drivers, they must not place the source code in the target/src/drv and
target/h/drv directories; all existing Wind River drivers must not be modified. If an
end user were to install a Wind River BSP or a new VxWorks version after
installing a third-party BSP with altered shared files, the third-party changes
would be overwritten by the Wind River files.
Typically, BSPs can be written so that all target-specific files reside in
target/config/bspname, and target reference pages in docs/vxworks/bsp/bspName.
In the few cases where this is not possible, the BSP must include altered versions
of the shared files. However, the shared files themselves must not be altered;
instead, a copy of the needed file is modified and placed in an appropriate location
(for example, target/config/bspname). Then the BSP make files are updated to point
to the developer’s version; see the makefile mechanisms described in the Tornado
User’s Guide, 2.2.
The BSP developer can use the CONFIG_ALL makefile variable to direct the BSP
make files to search for modified versions of the target/config/all files. First, the
developer should make copies of the Wind River versions of these files and place
them in the BSP bspname directory, modifying them as necessary. (Note that this
mechanism only works for traditional command-line building and does not have
any effect on project configuration or building.)
By customizing the VxWorks build, the BSP developer can create target-specific
versions of shared files without conflicting with other BSPs.
Beginning with Tornado 2.0, each architecture CD-ROM contains a “Driver
Objects/Headers” product. This product contains all the compiled Ethernet and
10
199