BSP Developer's Guide

E
Component Language
REQUIRES r1 r2 .. // other components required. Note:
// dependencies are automatically calculated
// based on a components MODULES and
// LINK_SYMS. For example, because nfsLib.o
// calls rpcLib.o, the tool is able to
// figure out that INCLUDE_NFS requires
// INCLUDE_RPC. One only needs to list
// requirements that cannot be detected from
// MODULE dependencies. Typically only needed
// for components that don’t have associated
// MODULES (e.g., ones with just
// configlettes).
EXCLUDES e1 e1 .. // other components that cannot
// coexist with this component
HELP h1 h2 .. // reference pages associated with the
// component.
// The default is the MODULES and INIT_RTN
// of the component. For example, if the
// component has MODULE fooLib.o, then the
// manual page for fooLib is automatically
// associated with the component (if the
// manual page exists). Similary for the
// components INIT_RTN. If there are any
// other relevant manual pages, they can
// be specified here.
MACRO_NEST expr // This is for Wind River internal use only.
// It is used to tell the bsp2prj script
// how to create a project corresponding
// to a given BSP.
// The "bsp2prj" script assumes that if
// a BSP has macro INCLUDE_FOO defined,
// the corresponding component INCLUDE_FOO
// should be included in the project.
// That is not always the case. For example,
// The INCLUDE_AOUT component should only
// be included if both INCLUDE_AOUT *and*
// INCLUDE_LOADER are defined.
// So for the INCLUDE_AOUT component, we set
// MACRO_NEST = INCLUDE_LOADER.
// SImilarly all WDB subcomponents have
// MACRO_NEST = INCLUDE_WDB.
E
ARCHIVE a1 // archive in which to find the MODULES.
// default is lib$(CPU)$(TOOL)vx.a.
// file path is assumed to be relative
// to $(WIND_BASE)/target/lib.
// any archive listed here is
// automatically added to the VxWorks
// link-line when the component is
// included.
// Note: the tool only analyzes archives
// associated with included components.
233