📄 creating-build-tree.html
字号:
<!-- Copyright (C) 2003 Red Hat, Inc. --><!-- This material may be distributed only subject to the terms --><!-- and conditions set forth in the Open Publication License, v1.0 --><!-- or later (the latest version is presently available at --><!-- http://www.opencontent.org/openpub/). --><!-- Distribution of the work or derivative of the work in any --><!-- standard (paper) book form is prohibited unless prior --><!-- permission is obtained from the copyright holder. --><HTML><HEAD><TITLE>Creating the Build Tree</TITLE><meta name="MSSmartTagsPreventParsing" content="TRUE"><METANAME="GENERATOR"CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+"><LINKREL="HOME"TITLE="eCos User Guide"HREF="ecos-user-guide.html"><LINKREL="UP"TITLE="Manual Configuration"HREF="manual-configuration.html"><LINKREL="PREVIOUS"TITLE="Manual Configuration"HREF="manual-configuration.html"><LINKREL="NEXT"TITLE="Conflicts and constraints"HREF="conflicts-and-constraints.html"></HEAD><BODYCLASS="SECT1"BGCOLOR="#FFFFFF"TEXT="#000000"LINK="#0000FF"VLINK="#840084"ALINK="#0000FF"><DIVCLASS="NAVHEADER"><TABLESUMMARY="Header navigation table"WIDTH="100%"BORDER="0"CELLPADDING="0"CELLSPACING="0"><TR><THCOLSPAN="3"ALIGN="center">eCos User Guide</TH></TR><TR><TDWIDTH="10%"ALIGN="left"VALIGN="bottom"><AHREF="manual-configuration.html"ACCESSKEY="P">Prev</A></TD><TDWIDTH="80%"ALIGN="center"VALIGN="bottom">Chapter 28. Manual Configuration</TD><TDWIDTH="10%"ALIGN="right"VALIGN="bottom"><AHREF="conflicts-and-constraints.html"ACCESSKEY="N">Next</A></TD></TR></TABLE><HRALIGN="LEFT"WIDTH="100%"></DIV><DIVCLASS="SECT1"><H1CLASS="SECT1"><ANAME="CREATING-BUILD-TREE">Creating the Build Tree</H1><P>Generating a build tree is a non-trivial operation and should not be attempted manually. Instead, <SPANCLASS="PRODUCTNAME">eCos</SPAN> is shipped with a tool called <BCLASS="COMMAND">ecosconfig</B> that should be used to create a build tree.</P><P>Usually <BCLASS="COMMAND">ecosconfig</B> will berun inside the build tree itself. If you are creating a new buildtree then typically you will create a new empty directory usingthe <BCLASS="COMMAND">mkdir</B> command, <BCLASS="COMMAND">cd</B> intothat directory, and then invoke <BCLASS="COMMAND">ecosconfig</B> tocreate a configuration. By default, the configuration is storedin a file <TTCLASS="FILENAME">ecos.ecc</TT> in the currentdirectory. The configuration may be modified by editing this file directly. <BCLASS="COMMAND">ecosconfig</B> itselfdeals with a number of coarse-grained configuration options suchas the target platform and the packages that should be used.</P><P>The <BCLASS="COMMAND">ecosconfig</B> tool is alsoused subsequently to generate a build tree for a configuration.Once a build tree exists, it is possible to run <BCLASS="COMMAND">ecosconfig</B> againinside the same build tree. This will be necessary if your wishto change some of the configuration options.</P><P><BCLASS="COMMAND">ecosconfig</B> does not generatethe top-level directory of the build tree; you must do this yourself. </P><TABLEBORDER="5"BGCOLOR="#E0E0F0"WIDTH="70%"><TR><TD><PRECLASS="SCREEN">$ mkdir ecos-work$ cd ecos-work</PRE></TD></TR></TABLE><P>The next step is to run <BCLASS="COMMAND">ecosconfig</B>: </P><TABLEBORDER="5"BGCOLOR="#E0E0F0"WIDTH="70%"><TR><TD><PRECLASS="SCREEN">$ ecosconfig <qualifiers> <command></PRE></TD></TR></TABLE><DIVCLASS="SECT2"><H2CLASS="SECT2"><ANAME="AEN2416">ecosconfig qualifiers</H2><P>The available command line qualifiers for <BCLASS="COMMAND">ecosconfig</B> are as follows. Multiple qualifiers may be used on the command line: </P><P></P><DIVCLASS="VARIABLELIST"><DL><DT><TTCLASS="OPTION">--help</TT></DT><DD><P>Provides basic usage guidelines for the available commands and qualifiers.</P></DD><DT><TTCLASS="OPTION">--config=<file></TT></DT><DD><P>Specifies an <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration save file for use by the tool. By default, the file <TTCLASS="FILENAME">ecos.ecc</TT> in the current directory is used. Developers may prefer to use a common location for all their <SPANCLASS="PRODUCTNAME">eCos</SPAN> configurations rather than keep the configuration information in the base of the build tree.</P></DD><DT><TTCLASS="OPTION">--prefix=<dir></TT></DT><DD><P>Specifies an alternative location for the install tree. By default, the install tree resides inside the <TTCLASS="FILENAME">install</TT> directory in the build tree. Developers may prefer to locate the build tree in a temporary file hierarchy but keep the install tree in a more permanent location.</P></DD><DT><TTCLASS="OPTION">--srcdir=<dir></TT></DT><DD><P>Specifies the location of the component repository. By default, the tool uses the location specified in the <TTCLASS="REPLACEABLE"><I>ECOS_REPOSITORY</I></TT> environment variable. Developers may prefer to use of this qualifier if they are working with more than one repository.</P></DD><DT><TTCLASS="OPTION">--no-resolve</TT></DT><DD><P>Disables the implicit resolution of conflicts while manipulating the configuration data. developers may prefer to resolve conflicts by editing the <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration save file manually.</P></DD><DT><TTCLASS="OPTION">--ignore-errors</TT>, <TTCLASS="OPTION">-i</TT></DT><DD><P>By default, ecosconfig will exit with an error code if the currentconfiguration contains any conflicts, and it is not possible togenerate or update a build tree for such configurations. Thisqualifier causes ecosconfig to ignore such problems, and hence it ispossible to generate a build tree even if there are stillconflicts. Of course, there are no guarantees that the resultingsystem will actually do anything.</P></DD><DT><TTCLASS="OPTION">--verbose</TT>, <TTCLASS="OPTION">-v</TT></DT><DD><P>Display more information.</P></DD><DT><TTCLASS="OPTION">--quiet</TT>, <TTCLASS="OPTION">-q</TT></DT><DD><P>Display less information.</P></DD></DL></DIV><P>The <TTCLASS="OPTION">--config</TT>, <TTCLASS="OPTION">--prefix</TT> and<TTCLASS="OPTION">--srcdir</TT> qualifiers can also be written with two arguments,for example:</P><TABLEBORDER="5"BGCOLOR="#E0E0F0"WIDTH="70%"><TR><TD><PRECLASS="SCREEN">ecosconfig --srcdir <TTCLASS="REPLACEABLE"><I><dir></I></TT> ...</PRE></TD></TR></TABLE><P>This simplifies filename completion with some shells.</P></DIV><DIVCLASS="SECT2"><H2CLASS="SECT2"><ANAME="AEN2480">ecosconfig commands</H2><P>The available commands for <BCLASS="COMMAND">ecosconfig</B> are as follows:</P><P></P><DIVCLASS="VARIABLELIST"><DL><DT><BCLASS="COMMAND">list</B></DT><DD><P>Lists the available packages, targets and templates as installed in the <SPANCLASS="PRODUCTNAME">eCos</SPAN> repository. Aliases and package versions are also reported.</P></DD><DT><BCLASS="COMMAND">new <target> [<template> [<version>]]</B></DT><DD><P>Creates a new <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration for the specified target hardware and saves it. A software template may also be specified. By default, the template named ‘default’ is used. If the template version is not specified, the latest version is used.</P></DD><DT><BCLASS="COMMAND">target <target></B></DT><DD><P>Changes the target hardware selection for the <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration. This has the effect of unloading packages supporting the target selected previously and loading the packages which support the new hardware. This command will be used typically when switching between a simulator and real hardware.</P></DD><DT><BCLASS="COMMAND">template <template> [<version>]</B></DT><DD><P>Changes the template selection for the <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration. This has the effect of unloading packages specified by the template selected previously and loading the packages specified by the new template. By default, the latest version of the specified template is used.</P></DD><DT><BCLASS="COMMAND">remove <packages></B></DT><DD><P>Removes the specified packages from the <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration. This command will be used typically when the template on which a configuration is based contains packages which are not required.</P></DD><DT><BCLASS="COMMAND">add <packages></B></DT><DD><P>Adds the specified packages to the <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration. Thiscommand will be used typically when the template on which aconfiguration is based does not contain all the packages which arerequired.For example, add-on packages provided by third parties willnot be known to the standard templates, so they will have to be addedexplicitly. </P></DD><DT><BCLASS="COMMAND">version <version> <packages></B></DT><DD><P>Selects the specified version of a number of packages in the <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration. By default, the most recent version of each package is used. This command will be used typically when an older version of a package is required.</P></DD><DT><BCLASS="COMMAND">check</B></DT><DD><P>Presents the following information concerning the current configuration:</P><P></P><OLTYPE="1"><LI><P>the selected target hardware</P></LI><LI><P>the selected template</P></LI><LI><P>additional packages</P></LI><LI><P>removed packages</P></LI><LI><P>the selected version of packages where this is not the most recent version</P></LI><LI><P>conflicts in the current configuration</P></LI></OL></DD><DT><BCLASS="COMMAND">resolve</B></DT><DD><P>Resolves conflicts identified in the current <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration by invoking an inference capability. Resolved conflicts are reported, but not all conflicts may be resolvable. This command will be used typically following manual editing of the configuration.</P></DD><DT><BCLASS="COMMAND">export <file></B></DT><DD><P>Exports a minimal <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration save file with the specified name. This file contains only those options which do not have their default value. Such files are used typically to transfer option values from one configuration to another.</P></DD><DT><BCLASS="COMMAND">import <file></B></DT><DD><P>Imports a minimal <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration save file with the specified name. The values of those options specified in the file are applied to the current configuration.</P></DD><DT><BCLASS="COMMAND">tree</B></DT><DD><P>Generates a build tree based on the current <SPANCLASS="PRODUCTNAME">eCos</SPAN> configuration. This command will be used typically just before building <SPANCLASS="PRODUCTNAME">eCos</SPAN>.Normally a build tree canonly be generated if if the configuration has no unresolvedconflicts, but <TTCLASS="OPTION">--ignore-errors</TT> can be used to overridethis.</P></DD></DL></DIV></DIV></DIV><DIVCLASS="NAVFOOTER"><HRALIGN="LEFT"WIDTH="100%"><TABLESUMMARY="Footer navigation table"WIDTH="100%"BORDER="0"CELLPADDING="0"CELLSPACING="0"><TR><TDWIDTH="33%"ALIGN="left"VALIGN="top"><AHREF="manual-configuration.html"ACCESSKEY="P">Prev</A></TD><TDWIDTH="34%"ALIGN="center"VALIGN="top"><AHREF="ecos-user-guide.html"ACCESSKEY="H">Home</A></TD><TDWIDTH="33%"ALIGN="right"VALIGN="top"><AHREF="conflicts-and-constraints.html"ACCESSKEY="N">Next</A></TD></TR><TR><TDWIDTH="33%"ALIGN="left"VALIGN="top">Manual Configuration</TD><TDWIDTH="34%"ALIGN="center"VALIGN="top"><AHREF="manual-configuration.html"ACCESSKEY="U">Up</A></TD><TDWIDTH="33%"ALIGN="right"VALIGN="top">Conflicts and constraints</TD></TR></TABLE></DIV></BODY></HTML>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -