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.display.html"><LINK
29 HREF="ref.flavor.html"></HEAD
40 SUMMARY="Header navigation table"
52 > Component Writer's Guide</TH
60 HREF="ref.display.html"
74 HREF="ref.flavor.html"
99 > -- The location of online-documentation for a configuration option.</DIV
101 CLASS="REFSYNOPSISDIV"
113 >cdl_option <name> {
129 >Users can only be expected to manipulate configuration options
130 sensibly if they are given sufficient information about these options.
131 There are three properties which serve to explain an option in plain
135 > property gives a textual alias for an option,
136 which is usually more comprehensible than something like
139 >CYGPKG_LIBC_TIME_ZONES</TT
144 gives a longer description, typically a paragraph or so; the <SPAN
148 property specifies the location of additional on-line documentation
149 related to a configuration option. In the context of a graphical tool
153 > string will be the primary way for users to identify
154 configuration options; the <SPAN
157 > paragraph will be visible
158 whenever the option is selected; the on-line documentation will only
159 be accessed when the user explicitly requests it.</P
161 >The documentation may be an absolute URL, but more generally the
162 on-line documentation will be shipped with the package and can be
163 accessed via a relative URL. If the package follows the <A
164 HREF="package.html#PACKAGE.HIERARCHY"
165 >directory layout conventions</A
167 the configuration tools will search for the specified html file
172 of the package, then relative to the package directory itself. The URL
176 > character to specify an anchor
197 >At the time of writing the <SPAN
200 > packages in the standard
201 distribution do not conform to the directory layout conventions when
202 it comes to the documentation. Instead of organizing the documentation
203 on a per-package basis and placing it in the corresponding
207 > sub-directories, all the
208 documentation is kept in a central location. This should get addressed
209 in a future release of the system. Third party component writers
210 should follow the layout conventions.</P
230 CLASS="PROGRAMLISTING"
231 >cdl_package CYGPKG_KERNEL {
232 display "eCos kernel"
233 doc ref/ecos-ref.4.html
234 include_dir cyg/kernel
236 This package contains the core functionality of the eCos
237 kernel. It relies on functionality provided by various HAL
238 packages and by the eCos infrastructure. In turn the eCos
239 kernel provides support for other packages such as the device
240 drivers and the uITRON compatibility layer."
256 HREF="ref.description.html"
263 HREF="ref.display.html"
275 SUMMARY="Footer navigation table"
286 HREF="ref.display.html"
295 HREF="cdl-guide.html"
304 HREF="ref.flavor.html"
323 HREF="reference.html"