1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="The eCos Component Writer's Guide"
20 HREF="cdl-guide.html"><LINK
22 TITLE="CDL Language Specification"
23 HREF="reference.html"><LINK
26 HREF="ref.requires.html"><LINK
28 TITLE="Templates, Targets and Other Topics"
29 HREF="advanced.html"></HEAD
40 SUMMARY="Header navigation table"
52 > Component Writer's Guide</TH
60 HREF="ref.requires.html"
85 NAME="REF.SCRIPT"><SPAN
99 > -- Include additional configuration information from another
102 CLASS="REFSYNOPSISDIV"
114 >cdl_component <name> {
115 script <filename>
130 >It is possible to define all the configuration options and
131 sub-components for a given package in a single CDL script, either by
132 nesting them in the appropriate command bodies, by extensive use of
136 > property, or by some combination of these two. However
137 for large packages this is inconvenient and it is better to split the
138 raw configuration data over several different files. The <SPAN
142 property can be used to achieve this. It takes a single filename as
143 argument. If the package follows the <A
144 HREF="package.html#PACKAGE.HIERARCHY"
145 >directory layout conventions</A
147 the configuration tools will look for the specified file in the
151 > sub-directory of the
152 package, otherwise it will look for the file relative to the package's
153 top-level directory.</P
158 > property can only occur in the body of a <TT
161 >command, and only one <SPAN
164 > property per body is allowed.</P
180 CLASS="PROGRAMLISTING"
181 >cdl_component CYGPKG_UITRON_TASKS {
185 uITRON Tasks are the basic blocks of multi-tasking
186 in the uITRON world; they are threads or lightweight
187 processes, sharing the address space and the CPU.
188 They communicate using the primitives outlined above.
189 Each has a stack, an entry point (a C or C++ function),
190 and (where appropriate) a scheduling priority."
207 HREF="ref.cdl-component.html"
214 HREF="ref.parent.html"
226 SUMMARY="Footer navigation table"
237 HREF="ref.requires.html"
246 HREF="cdl-guide.html"
274 HREF="reference.html"
282 >Templates, Targets and Other Topics</TD