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. -->
12 >Fine-grained Configuration</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos User Guide"
20 HREF="ecos-user-guide.html"><LINK
22 TITLE="Manual Configuration"
23 HREF="manual-configuration.html"><LINK
25 TITLE="Coarse-grained Configuration"
26 HREF="coarse-grained-configuration.html"><LINK
28 TITLE="Editing an eCos Savefile"
29 HREF="editing-an-ecos-savefile.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="coarse-grained-configuration.html"
65 >Chapter 28. Manual Configuration</TD
71 HREF="editing-an-ecos-savefile.html"
85 NAME="FINE-GRAINED-CONFIGURATION">Fine-grained Configuration</H1
91 coarse-grained control over the configuration: the hardware,
92 the template and the packages that should be built. Unlike
93 the Configuration Tool,
98 any facilities for manipulating finer-grained configuration options such as how many
99 priority levels the scheduler should support. There are
100 hundreds of these options, and manipulating them by means of
101 command line arguments would not be sensible. </P
103 >In the current system fine-grained configuration options may
104 be manipulated by manual editing of the configuration file. When
105 a file has been edited in this way, the <B
109 should be used to check the configuration for any conflicts which
110 may have been introduced:</P
119 >$ ecosconfig check</PRE
128 all conflicts and will also rewrite the configuration file, propagating
129 any changes which affect other options. The user may choose to resolve
130 the conflicts either by re-editing the configuration file manually
131 or by invoking the inference engine using the <B
143 >$ ecosconfig resolve</PRE
152 list all conflicts which can be resolved and save the resulting changes
153 to the configuration.</P
155 >It is necessary to regenerate the build tree and header files
156 following any changes to the configuration before rebuilding <SPAN
168 >$ ecosconfig tree</PRE
173 >All the configuration options and their descriptions are listed
179 > Reference Manual</I
187 SUMMARY="Footer navigation table"
198 HREF="coarse-grained-configuration.html"
207 HREF="ecos-user-guide.html"
216 HREF="editing-an-ecos-savefile.html"
226 >Coarse-grained Configuration</TD
232 HREF="manual-configuration.html"