BSP Developer's Guide

E
Component Language
}
// default is none - in which case the user
// must define a value to use the component.
// for parameters of type "exists," the
// value is TRUE if the macro should be
// defined, or FALSE if undefined.
E.1.3 Folder Properties
The project facility component hierarchy uses folders to group components
logically. Instead of presenting all components in a flat list, as in configAll.h, the
project facility presents them hierarchically. For example, top-level folders might
organize components under headings such as network, drivers, OS, and
application.
Folder folder {
NAME name // readable name (e.g., "foo libraries").
SYNOPSIS desc // one-line description
CHILDREN i1 i2 .. // containers and components
// that belong to this container.
}
DEFAULTS i1 i2 .. // default CHILDREN.
// if the folder represents a complex
// subsystem (such as the WDB agent),
// this is used to suggest to the user
// which components in the folder are
// considered "default." That way the user
// can add the whole subsystem at once,
// and a reasonable set of subcomponents
// will be chosen.
E
E.1.4 Selection Properties
Selection selection {
NAME name // readable name (for example , "foo
// communication path")
SYNOPSIS desc // one-line description
COUNT min-max // range of allowed subcomponents.
// 1-1 means exactly one.
// 1- means one or more.
CHILDREN i1 i2 .. // components from which to select
DEFAULTS i1 i2 .. // default CHILDREN.
235