BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
6.3.1 CDF Conventions
Follow these conventions when working with component description files:
■
■
■
■
■
■
■
All component names are of the form INCLUDE_FOO.
All folders names are of the form FOLDER_FOO.
All selection names are of the form SELECT_FOO.
Parameter names should not match the format of any other object type, but are
otherwise unrestricted. For example, you can use FOO_XXX, but not
INCLUDE_FOO.
All initGroup names should be of the form initFoo. However, Wind River
initGroups use the form usrFoo (for backwards compatibility.)
All component description files have a .cdf suffix.
All .cdf file names begin with two decimal digits, that is, 00xxxx.cdf. These first
two digits control the order in which .cdf files are read within a directory.
6.3.2 CDF Precedence and Paths
The component description files are read at two points:
■
when a project is created
■
after component description files are changed and the project build occurs
The order in which CDFs are read is important to the user. If two files describe the
same property of the same component, the one read last overrides all earlier ones.
The intent is to allow component description files to have some precedence level.
Files read later have higher precedence than those read earlier.
Precedence is established in two complementary ways:
– CDF files reside in certain directories, and those directories are read in a
specified order.
– Within one of these directories, CDFs are read in alphanumeric order.
The project facility sources all .cdf files in any of the following directories. These
directories are read in the order in which they’re presented:
(1) comps/vxWorks
Contains all generic VxWorks components.
126