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 >Building the System</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="Conflicts and constraints"
26 HREF="conflicts-and-constraints.html"><LINK
29 HREF="ecos-packages.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="conflicts-and-constraints.html"
65 >Chapter 28. Manual Configuration</TD
71 HREF="ecos-packages.html"
85 NAME="BUILDING-THE-SYSTEM">Building the System</H1
87 >Once a build tree has been generated with
94 > is straightforward:</P
108 >The build tree contains the subdirectories, makefiles,
109 and everything else that is needed to generate the default
110 configuration for the selected architecture and platform.
111 The only requirement is that the tools needed for that
112 architecture, for example
117 are available using the standard search path. If this is not
122 fail with an error message. If you have a multiprocessor
123 system then it may be more efficient to use:</P
148 number of processors on your system.</P
154 has completed, the install tree will contain the header
155 files and the target library that are needed for application
158 >It is also possible to build the system’s test cases
159 for the current configuration:</P
173 >The resulting test executables will end up in a
177 > subdirectory of the
180 >If disk space is scarce then it is possible to make the copy
181 of the install tree for application development purposes, and then
196 >The build tree will now use up a minimum of disk space — the
197 bulk of what is left consists of configuration header files that
198 you may have edited and hence should not be deleted automatically.
199 However, it is possible to rebuild the system at any time without
209 >Under exceptional circumstances it may be necessary to run <B
213 > for other reasons, such as when a new release
214 of the toolchain is installed. The toolchain includes a number of
215 header files which are closely tied to the compiler, for example <TT
219 and these header files are not and should not be duplicated by <SPAN
223 The makefiles perform header file dependency analysis, so that when
224 a header file is changed all affected sources will be rebuilt during
228 >. This is very useful
229 when the configuration header files are changed, but it also means
230 that a build tree containing information about the locations of
231 header files must be rebuilt. If a new version of the toolchain
232 is installed and the old version is removed then this location information
233 is no longer accurate, and <B
237 complain that certain dependencies cannot be satisfied. Under such circumstances
238 it is necessary to do a <B
248 SUMMARY="Footer navigation table"
259 HREF="conflicts-and-constraints.html"
268 HREF="ecos-user-guide.html"
277 HREF="ecos-packages.html"
287 >Conflicts and constraints</TD
293 HREF="manual-configuration.html"