BSP Developer's Guide

6
Components
Figure 6-4
Include Components Window
6
The project facility automatically analyzes object module dependencies in order to
calculate component dependencies; for example, if fooLib.o has an unresolved
global for logMsg( ), an automatic dependency upon the component
INCLUDE_LOGGING is detected. For components not shipped in object module
format, CDL supports the explicit listing of component dependencies. If the source
portion contains a call to logMsg( ), the project facility does not detect the
dependency; instead, an explicit dependency upon INCLUDE_LOGGING should
be declared using the REQUIRES property. See Step 6.
If your module is not located in the standard path, use the ARCHIVE property to
specify the archive name, for example, /path/fooLib.a. (For additional instructions
concerning the use of ARCHIVE, see Step 10.)
NOTE: Third parties should create their own archives; do not modify Wind River
archives.
Use the HDR_FILES property to specify any .h files associated with the component,
like foo.h. These files are emitted in prjConfig.c, providing the initialization
routine with a declaration.
If there is source code that should be compiled as part of the component, put it in
a .c file and specify the file name in the CONFIGLETTES property, for example,
fooConfig.c. Component parameters should be referenced in the configlette or in
the initialization routine; otherwise they have no effect.
129