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.define-proc.html"><LINK
29 HREF="ref.display.html"></HEAD
40 SUMMARY="Header navigation table"
52 > Component Writer's Guide</TH
60 HREF="ref.define-proc.html"
74 HREF="ref.display.html"
85 NAME="REF.DESCRIPTION"><SPAN
99 > -- Provide a textual description for an option.</DIV
101 CLASS="REFSYNOPSISDIV"
113 >cdl_option <name> {
114 description <text>
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 >At present there is no way of providing any sort of formatting mark-up
162 in a description. It is possible that future versions of the
163 configuration tools will provide some control over the way the
164 description text gets rendered.</P
180 CLASS="PROGRAMLISTING"
181 >cdl_option CYGDBG_INFRA_DEBUG_TRACE_MESSAGE {
182 display "Use trace text"
185 All trace calls within eCos contain a text message
186 which should give some information about the circumstances.
187 These text messages will end up being embedded in the
188 application image and hence there is a significant penalty
189 in terms of image size.
190 It is possible to suppress the use of these messages by
191 disabling this option.
192 This results in smaller code size, but there is less
193 human-readable information available in the trace output,
194 possibly only filenames and line numbers."
209 HREF="ref.display.html"
228 SUMMARY="Footer navigation table"
239 HREF="ref.define-proc.html"
248 HREF="cdl-guide.html"
257 HREF="ref.display.html"
276 HREF="reference.html"