Lines Matching refs:component

37 one main component per each subdirectory. Each such directory contains
38 an ``LLVMBuild.txt`` which contains the component definitions.
40 The component descriptions for the project as a whole are automatically
42 source directory structure to find all of the component description
76 *components*. Every component is typically grouped into its own
77 subdirectory. Generally, a component is organized around a coherent
92   component libraries. Most LLVM tools are small and are primarily
96 that define the component. See the `LLVMBuild Format Reference`_ section
126 properties. An typical component description file for a library
127 component would look typically look like the following example:
140 Each file may define exactly one common component, named ``common``. The
141 common component may define the following properties:
148 Each file may define multiple components. Each component is described by a
149 section who name starts with ``component``. The remainder of the section
159 Every component is defined by the properties in the section. The exact
160 list of properties that are allowed depends on the component type.
162 by the component type.
164 Every component must define the following properties:
168    The type of the component. Supported component types are detailed
174    The name of the component. Names are required to be unique across the
179    The name of the logical parent of the component. Components are
183    will be the main component of the parent directory.
185    Components may reference the root pseudo component using ``$ROOT`` to
194    produce some tool or source code required for building the component.
201 The following section lists the available component types, as well as
202 the properties which are associated with that component.
215    from the source code in the component directory.
222       not given, the name is derived from the component name itself.
228       used. That is, the link time dependencies for this component. When
235       this component is also part of. This allows nesting groups of
268    The name of the component should always be the name of the target.
292    built from the source code in the component directory and linked.
303          The values should be the component names, which may not always