BSP Developer's Guide

6
Components
Folder FOLDER_ANSI {
NAME
ANSI C components (libc)
SYNOPSIS ANSI libraries
CHILDREN INCLUDE_ANSI_ASSERT \
INCLUDE_ANSI_CTYPE \
INCLUDE_ANSI_LOCALE \
INCLUDE_ANSI_MATH \
INCLUDE_ANSI_STDIO \
INCLUDE_ANSI_STDLIB \
INCLUDE_ANSI_STRING \
INCLUDE_ANSI_TIME \
INCLUDE_ANSI_STDIO_EXTRA
DEFAULTS INCLUDE_ANSI_ASSERT INCLUDE_ANSI_CTYPE \
INCLUDE_ANSI_MATH INCLUDE_ANSI_STDIO \
INCLUDE_ANSI_STDLIB INCLUDE_ANSI_STRING \
INCLUDE_ANSI_TIME
}
6
Folders offer greater flexibility in grouping components than the pre-Tornado 2.0
method. Previously, #ifdef statements meant that all of the specified #defines were
included simultaneously. Now, folders allow groups to include more than just a
default set of components that are included together (as defined in Tornado 2.x by
the DEFAULTS property of the folder object); components can be added and
removed from the configuration individually (as defined by the CHILDREN
property of the folder object).
Folder information largely affects user presentation. It is not related to
initialization group hierarchy, and thereby the startup sequence, which depend
solely on a component’s initialization group. Folders can contain one or more
components, selections, and other folders; they do not have parameter or
initialization group objects associated with them.
The following properties describe a folder:
NAME
A readable name, the one that appears next to the folder icon in the project
facility component hierarchy.
SYNOPSIS
A brief description of the folder.
CHILDREN
Components, folders, and selections belonging to this folder are called children.
DEFAULTS
The default component(s) that would be included if the folder were “added”
without any overrides. Folder groupings can affect configuration when a
folder is added, because components specified by a folder’s DEFAULTS
property are added all at once.
117