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 >Creating the Build Tree</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="Manual Configuration"
26 HREF="manual-configuration.html"><LINK
28 TITLE="Conflicts and constraints"
29 HREF="conflicts-and-constraints.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="manual-configuration.html"
65 >Chapter 28. Manual Configuration</TD
71 HREF="conflicts-and-constraints.html"
85 NAME="CREATING-BUILD-TREE">Creating the Build Tree</H1
87 >Generating a build tree is a non-trivial operation and
88 should not be attempted manually. Instead, <SPAN
96 be used to create a build tree.</P
102 run inside the build tree itself. If you are creating a new build
103 tree then typically you will create a new empty directory using
111 that directory, and then invoke <B
115 create a configuration. By default, the configuration is stored
120 directory. The configuration may be modified by editing this file directly. <B
124 deals with a number of coarse-grained configuration options such
125 as the target platform and the packages that should be used.</P
131 used subsequently to generate a build tree for a configuration.
132 Once a build tree exists, it is possible to run <B
136 inside the same build tree. This will be necessary if your wish
137 to change some of the configuration options.</P
143 the top-level directory of the build tree; you must do this
159 >The next step is to run <B
171 >$ ecosconfig <qualifiers> <command></PRE
180 NAME="AEN2416">ecosconfig qualifiers</H2
182 >The available command line qualifiers for
186 > are as follows. Multiple
187 qualifiers may be used on the command line:
201 >Provides basic usage guidelines for the
202 available commands and qualifiers.</P
207 >--config=<file></TT
214 > configuration save file for
215 use by the tool. By default, the file
220 current directory is used. Developers may prefer to
221 use a common location for all their <SPAN
225 configurations rather than keep the configuration
226 information in the base of the build tree.</P
231 >--prefix=<dir></TT
235 >Specifies an alternative location for the
236 install tree. By default, the install tree resides
241 directory in the build tree. Developers may prefer
242 to locate the build tree in a temporary file
243 hierarchy but keep the install tree in a more
244 permanent location.</P
249 >--srcdir=<dir></TT
253 >Specifies the location of the component
254 repository. By default, the tool uses the location
262 environment variable. Developers may prefer to use
263 of this qualifier if they are working with more than
273 >Disables the implicit resolution of conflicts
274 while manipulating the configuration data.
275 developers may prefer to resolve conflicts by
279 > configuration save file
292 >By default, ecosconfig will exit with an error code if the current
293 configuration contains any conflicts, and it is not possible to
294 generate or update a build tree for such configurations. This
295 qualifier causes ecosconfig to ignore such problems, and hence it is
296 possible to generate a build tree even if there are still
297 conflicts. Of course, there are no guarantees that the resulting
298 system will actually do anything.</P
310 >Display more information.</P
322 >Display less information.</P
337 > qualifiers can also be written with two arguments,
347 >ecosconfig --srcdir <TT
357 >This simplifies filename completion with some shells.</P
364 NAME="AEN2480">ecosconfig commands</H2
366 >The available commands for
384 >Lists the available packages, targets and
385 templates as installed in the <SPAN
389 Aliases and package versions are also
395 >new <target> [<template> [<version>]]</B
403 the specified target hardware and saves it. A
404 software template may also be specified. By default,
405 the template named ‘default’ is used. If
406 the template version is not specified, the latest
412 >target <target></B
416 >Changes the target hardware selection
420 > configuration. This has the effect of
421 unloading packages supporting the target selected
422 previously and loading the packages which support
423 the new hardware. This command will be used
424 typically when switching between a simulator and
430 >template <template> [<version>]</B
434 >Changes the template selection for the <SPAN
438 configuration. This has the effect of unloading
439 packages specified by the template selected
440 previously and loading the packages specified by the
441 new template. By default, the latest version of the
442 specified template is used.</P
447 >remove <packages></B
451 >Removes the specified packages from the <SPAN
455 configuration. This command will be used typically
456 when the template on which a configuration is based
457 contains packages which are not required.</P
462 >add <packages></B
466 >Adds the specified packages to the <SPAN
469 > configuration. This
470 command will be used typically when the template on which a
471 configuration is based does not contain all the packages which are
472 required.For example, add-on packages provided by third parties will
473 not be known to the standard templates, so they will have to be added
479 >version <version> <packages></B
483 >Selects the specified version of a
484 number of packages in the <SPAN
488 default, the most recent version of each package is
489 used. This command will be used typically when an
490 older version of a package is required.</P
499 >Presents the following information
500 concerning the current configuration:</P
507 >the selected target hardware</P
511 >the selected template</P
515 >additional packages</P
523 >the selected version of packages
524 where this is not the most recent
529 >conflicts in the current configuration</P
540 >Resolves conflicts identified in the
544 > configuration by invoking an inference
545 capability. Resolved conflicts are reported, but not
546 all conflicts may be resolvable. This command will
547 be used typically following manual editing of the
553 >export <file></B
557 >Exports a minimal <SPAN
561 save file with the specified name. This file
562 contains only those options which do not have their
563 default value. Such files are used typically to
564 transfer option values from one configuration to
570 >import <file></B
574 >Imports a minimal <SPAN
578 save file with the specified name. The values of
579 those options specified in the file are applied to
580 the current configuration.</P
589 >Generates a build tree based on the current <SPAN
593 configuration. This command will be used typically
594 just before building <SPAN
597 >.Normally a build tree can
598 only be generated if if the configuration has no unresolved
602 > can be used to override
614 SUMMARY="Footer navigation table"
625 HREF="manual-configuration.html"
634 HREF="ecos-user-guide.html"
643 HREF="conflicts-and-constraints.html"
653 >Manual Configuration</TD
659 HREF="manual-configuration.html"
667 >Conflicts and constraints</TD