URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [rtos/] [ecos-2.0/] [doc/] [html/] [user-guide/] [creating-build-tree.html] - Blame information for rev 646

Go to most recent revision | Details | Compare with Previous | View Log


<!-- 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">
<META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="eCos User Guide"
HREF="ecos-user-guide.html"><LINK
REL="UP"
TITLE="Manual Configuration"
HREF="manual-configuration.html"><LINK
REL="PREVIOUS"
TITLE="Manual Configuration"
HREF="manual-configuration.html"><LINK
REL="NEXT"
TITLE="Conflicts and constraints"
HREF="conflicts-and-constraints.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>eCos User Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="manual-configuration.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 28. Manual Configuration</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="conflicts-and-constraints.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="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, <SPAN
CLASS="PRODUCTNAME"
>eCos</SPAN
> is shipped
          with a tool called <B
CLASS="COMMAND"
>ecosconfig</B
> that should
          be used to create a build tree.</P
><P
>Usually <B
CLASS="COMMAND"
>ecosconfig</B
> will be
run inside the build tree itself. If you are creating a new build
tree then typically you will create a new empty directory using
the <B
CLASS="COMMAND"
>mkdir</B
> command, <B
CLASS="COMMAND"
>cd</B
> into
that directory, and then invoke <B
CLASS="COMMAND"
>ecosconfig</B
> to
create a configuration. By default, the configuration is stored
in a file <TT
CLASS="FILENAME"
>ecos.ecc</TT
> in the current
directory. The configuration may be modified by editing this file directly. <B
CLASS="COMMAND"
>ecosconfig</B
> itself
deals with a number of coarse-grained configuration options such
as the target platform and the packages that should be used.</P
><P
>The <B
CLASS="COMMAND"
>ecosconfig</B
> tool is also
used subsequently to generate a build tree for a configuration.
Once a build tree exists, it is possible to run <B
CLASS="COMMAND"
>ecosconfig</B
> again
inside the same build tree. This will be necessary if your wish
to change some of the configuration options.</P
><P
><B
CLASS="COMMAND"
>ecosconfig</B
> does not generate
the top-level directory of the build tree; you must do this
        yourself. </P
><TABLE
BORDER="5"
BGCOLOR="#E0E0F0"
WIDTH="70%"
><TR
><TD
><PRE
CLASS="SCREEN"
>$ mkdir ecos-work
$ cd ecos-work</PRE
></TD
></TR
></TABLE
><P
>The next step is to run <B
CLASS="COMMAND"
>ecosconfig</B
>: </P
><TABLE
BORDER="5"
BGCOLOR="#E0E0F0"
WIDTH="70%"
><TR
><TD
><PRE
CLASS="SCREEN"
>$ ecosconfig &lt;qualifiers&gt; &lt;command&gt;</PRE
></TD
></TR
></TABLE
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2416">ecosconfig qualifiers</H2
><P
>The available command line qualifiers for
            <B
CLASS="COMMAND"
>ecosconfig</B
> are as follows. Multiple
            qualifiers may be used on the command line:
          </P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="OPTION"
>--help</TT
></DT
><DD
><P
>Provides basic usage guidelines for the
              available commands and qualifiers.</P
></DD
><DT
><TT
CLASS="OPTION"
>--config=&lt;file&gt;</TT
></DT
><DD
><P
>Specifies an <SPAN
CLASS="PRODUCTNAME"
>eCos</SPAN
> configuration save file for
                  use by the tool. By default, the file
                  <TT
CLASS="FILENAME"
>ecos.ecc</TT
> in the
                  current directory is used. Developers may prefer to
                  use a common location for all their <SPAN
CLASS="PRODUCTNAME"
>eCos</SPAN
>
                  configurations rather than keep the configuration
                  information in the base of the build tree.</P
></DD
><DT
><TT
CLASS="OPTION"
>--prefix=&lt;dir&gt;</TT
></DT
><DD
><P
>Specifies an alternative location for the
                  install tree. By default, the install tree resides
                  inside the <TT
CLASS="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
><TT
CLASS="OPTION"
>--srcdir=&lt;dir&gt;</TT
></DT
><DD
><P
>Specifies the location of the component
                  repository. By default, the tool uses the location
                  specified in the
                  <TT
CLASS="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
><TT
CLASS="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 <SPAN
CLASS="PRODUCTNAME"
>eCos</SPAN
> configuration save file
                  manually.</P
></DD
><DT
><TT
CLASS="OPTION"
>--ignore-errors</TT
>, <TT
CLASS="OPTION"
>-i</TT
></DT
><DD
><P
>By default, ecosconfig will exit with an error code if the current
configuration contains any conflicts, and it is not possible to
generate or update a build tree for such configurations. This
qualifier causes ecosconfig to ignore such problems, and hence it is
possible to generate a build tree even if there are still
conflicts. Of course, there are no guarantees that the resulting
system will actually do anything.</P
></DD
><DT
><TT
CLASS="OPTION"
>--verbose</TT
>, <TT
CLASS="OPTION"
>-v</TT
></DT
><DD
><P
>Display more information.</P
></DD
><DT
><TT
CLASS="OPTION"
>--quiet</TT
>, <TT
CLASS="OPTION"
>-q</TT
></DT
><DD
><P
>Display less information.</P
></DD
></DL
></DIV
><P
>The <TT
CLASS="OPTION"
>--config</TT
>, <TT
CLASS="OPTION"
>--prefix</TT
> and
<TT
CLASS="OPTION"
>--srcdir</TT
> qualifiers can also be written with two arguments,
for example:</P
><TABLE
BORDER="5"
BGCOLOR="#E0E0F0"
WIDTH="70%"
><TR
><TD
><PRE
CLASS="SCREEN"
>ecosconfig --srcdir <TT
CLASS="REPLACEABLE"
><I
>&lt;dir&gt;</I
></TT
> ...</PRE
></TD
></TR
></TABLE
><P
>This simplifies filename completion with some shells.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2480">ecosconfig commands</H2
><P
>The available commands for
            <B
CLASS="COMMAND"
>ecosconfig</B
> are as
            follows:</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><B
CLASS="COMMAND"
>list</B
></DT
><DD
><P
>Lists the available packages, targets and
                  templates as installed in the <SPAN
CLASS="PRODUCTNAME"
>eCos</SPAN
> repository.
                  Aliases and package versions are also
                  reported.</P
></DD
><DT
><B
CLASS="COMMAND"
>new &lt;target&gt; [&lt;template&gt; [&lt;version&gt;]]</B
></DT
><DD
><P
>Creates a new <SPAN
CLASS="PRODUCTNAME"
>eCos</SPAN
> configuration for
                  the specified target hardware and saves it. A
                  software template may also be specified. By default,
                  the template named &#8216;default&#8217; is used. If
                  the template version is not specified, the latest
                  version is used.</P
></DD
><DT
><B
CLASS="COMMAND"
>target &lt;target&gt;</B
></DT
><DD
><P
>Changes the target hardware selection
                  for the <SPAN
CLASS="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
><B
CLASS="COMMAND"
>template &lt;template&gt; [&lt;version&gt;]</B
></DT
><DD
><P
>Changes the template selection for the <SPAN
CLASS="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
><B
CLASS="COMMAND"
>remove &lt;packages&gt;</B
></DT
><DD
><P
>Removes the specified packages from the <SPAN
CLASS="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
><B
CLASS="COMMAND"
>add &lt;packages&gt;</B
></DT
><DD
><P
>Adds the specified packages to the <SPAN
CLASS="PRODUCTNAME"
>eCos</SPAN
> configuration. This
command will be used typically when the template on which a
configuration is based does not contain all the packages which are
required.For example, add-on packages provided by third parties will
not be known to the standard templates, so they will have to be added
explicitly. </P
></DD
><DT
><B
CLASS="COMMAND"
>version &lt;version&gt; &lt;packages&gt;</B
></DT
><DD
><P
>Selects the specified version of a
                  number of packages in the <SPAN
CLASS="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
><B
CLASS="COMMAND"
>check</B
></DT
><DD
><P
>Presents the following information
                  concerning the current configuration:</P
><P
></P
><OL
TYPE="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
><B
CLASS="COMMAND"
>resolve</B
></DT
><DD
><P
>Resolves conflicts identified in the
                  current <SPAN
CLASS="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
><B
CLASS="COMMAND"
>export &lt;file&gt;</B
></DT
><DD
><P
>Exports a minimal <SPAN
CLASS="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
><B
CLASS="COMMAND"
>import &lt;file&gt;</B
></DT
><DD
><P
>Imports a minimal <SPAN
CLASS="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
><B
CLASS="COMMAND"
>tree</B
></DT
><DD
><P
>Generates a build tree based on the current <SPAN
CLASS="PRODUCTNAME"
>eCos</SPAN
>
                  configuration. This command will be used typically
                  just before building <SPAN
CLASS="PRODUCTNAME"
>eCos</SPAN
>.Normally a build tree can
only be generated if if the configuration has no unresolved
conflicts, but <TT
CLASS="OPTION"
>--ignore-errors</TT
> can be used to override
this.</P
></DD
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="manual-configuration.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="ecos-user-guide.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="conflicts-and-constraints.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Manual Configuration</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="manual-configuration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Conflicts and constraints</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

Line No.	Rev	Author	Line
1	28	unneback	`<!-- 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. -->`
9			`<HTML`
10			`><HEAD`
11			`><TITLE`
12			`>Creating the Build Tree</TITLE`
13			`><meta name="MSSmartTagsPreventParsing" content="TRUE">`
14			`<META`
15			`NAME="GENERATOR"`
16			`CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+`
17			`"><LINK`
18			`REL="HOME"`
19			`TITLE="eCos User Guide"`
20			`HREF="ecos-user-guide.html"><LINK`
21			`REL="UP"`
22			`TITLE="Manual Configuration"`
23			`HREF="manual-configuration.html"><LINK`
24			`REL="PREVIOUS"`
25			`TITLE="Manual Configuration"`
26			`HREF="manual-configuration.html"><LINK`
27			`REL="NEXT"`
28			`TITLE="Conflicts and constraints"`
29			`HREF="conflicts-and-constraints.html"></HEAD`
30			`><BODY`
31			`CLASS="SECT1"`
32			`BGCOLOR="#FFFFFF"`
33			`TEXT="#000000"`
34			`LINK="#0000FF"`
35			`VLINK="#840084"`
36			`ALINK="#0000FF"`
37			`><DIV`
38			`CLASS="NAVHEADER"`
39			`><TABLE`
40			`SUMMARY="Header navigation table"`
41			`WIDTH="100%"`
42			`BORDER="0"`
43			`CELLPADDING="0"`
44			`CELLSPACING="0"`
45			`><TR`
46			`><TH`
47			`COLSPAN="3"`
48			`ALIGN="center"`
49			`>eCos User Guide</TH`
50			`></TR`
51			`><TR`
52			`><TD`
53			`WIDTH="10%"`
54			`ALIGN="left"`
55			`VALIGN="bottom"`
56			`><A`
57			`HREF="manual-configuration.html"`
58			`ACCESSKEY="P"`
59			`>Prev</A`
60			`></TD`
61			`><TD`
62			`WIDTH="80%"`
63			`ALIGN="center"`
64			`VALIGN="bottom"`
65			`>Chapter 28. Manual Configuration</TD`
66			`><TD`
67			`WIDTH="10%"`
68			`ALIGN="right"`
69			`VALIGN="bottom"`
70			`><A`
71			`HREF="conflicts-and-constraints.html"`
72			`ACCESSKEY="N"`
73			`>Next</A`
74			`></TD`
75			`></TR`
76			`></TABLE`
77			`><HR`
78			`ALIGN="LEFT"`
79			`WIDTH="100%"></DIV`
80			`><DIV`
81			`CLASS="SECT1"`
82			`><H1`
83			`CLASS="SECT1"`
84			`><A`
85			`NAME="CREATING-BUILD-TREE">Creating the Build Tree</H1`
86			`><P`
87			`>Generating a build tree is a non-trivial operation and`
88			`should not be attempted manually. Instead, <SPAN`
89			`CLASS="PRODUCTNAME"`
90			`>eCos</SPAN`
91			`> is shipped`
92			`with a tool called <B`
93			`CLASS="COMMAND"`
94			`>ecosconfig</B`
95			`> that should`
96			`be used to create a build tree.</P`
97			`><P`
98			`>Usually <B`
99			`CLASS="COMMAND"`
100			`>ecosconfig</B`
101			`> will be`
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`
104			`the <B`
105			`CLASS="COMMAND"`
106			`>mkdir</B`
107			`> command, <B`
108			`CLASS="COMMAND"`
109			`>cd</B`
110			`> into`
111			`that directory, and then invoke <B`
112			`CLASS="COMMAND"`
113			`>ecosconfig</B`
114			`> to`
115			`create a configuration. By default, the configuration is stored`
116			`in a file <TT`
117			`CLASS="FILENAME"`
118			`>ecos.ecc</TT`
119			`> in the current`
120			`directory. The configuration may be modified by editing this file directly. <B`
121			`CLASS="COMMAND"`
122			`>ecosconfig</B`
123			`> itself`
124			`deals with a number of coarse-grained configuration options such`
125			`as the target platform and the packages that should be used.</P`
126			`><P`
127			`>The <B`
128			`CLASS="COMMAND"`
129			`>ecosconfig</B`
130			`> tool is also`
131			`used subsequently to generate a build tree for a configuration.`
132			`Once a build tree exists, it is possible to run <B`
133			`CLASS="COMMAND"`
134			`>ecosconfig</B`
135			`> again`
136			`inside the same build tree. This will be necessary if your wish`
137			`to change some of the configuration options.</P`
138			`><P`
139			`><B`
140			`CLASS="COMMAND"`
141			`>ecosconfig</B`
142			`> does not generate`
143			`the top-level directory of the build tree; you must do this`
144			`yourself. </P`
145			`><TABLE`
146			`BORDER="5"`
147			`BGCOLOR="#E0E0F0"`
148			`WIDTH="70%"`
149			`><TR`
150			`><TD`
151			`><PRE`
152			`CLASS="SCREEN"`
153			`>$ mkdir ecos-work`
154			`$ cd ecos-work</PRE`
155			`></TD`
156			`></TR`
157			`></TABLE`
158			`><P`
159			`>The next step is to run <B`
160			`CLASS="COMMAND"`
161			`>ecosconfig</B`
162			`>: </P`
163			`><TABLE`
164			`BORDER="5"`
165			`BGCOLOR="#E0E0F0"`
166			`WIDTH="70%"`
167			`><TR`
168			`><TD`
169			`><PRE`
170			`CLASS="SCREEN"`
171			`>$ ecosconfig <qualifiers> <command></PRE`
172			`></TD`
173			`></TR`
174			`></TABLE`
175			`><DIV`
176			`CLASS="SECT2"`
177			`><H2`
178			`CLASS="SECT2"`
179			`><A`
180			`NAME="AEN2416">ecosconfig qualifiers</H2`
181			`><P`
182			`>The available command line qualifiers for`
183			`<B`
184			`CLASS="COMMAND"`
185			`>ecosconfig</B`
186			`> are as follows. Multiple`
187			`qualifiers may be used on the command line:`
188			`</P`
189			`><P`
190			`></P`
191			`><DIV`
192			`CLASS="VARIABLELIST"`
193			`><DL`
194			`><DT`
195			`><TT`
196			`CLASS="OPTION"`
197			`>--help</TT`
198			`></DT`
199			`><DD`
200			`><P`
201			`>Provides basic usage guidelines for the`
202			`available commands and qualifiers.</P`
203			`></DD`
204			`><DT`
205			`><TT`
206			`CLASS="OPTION"`
207			`>--config=<file></TT`
208			`></DT`
209			`><DD`
210			`><P`
211			`>Specifies an <SPAN`
212			`CLASS="PRODUCTNAME"`
213			`>eCos</SPAN`
214			`> configuration save file for`
215			`use by the tool. By default, the file`
216			`<TT`
217			`CLASS="FILENAME"`
218			`>ecos.ecc</TT`
219			`> in the`
220			`current directory is used. Developers may prefer to`
221			`use a common location for all their <SPAN`
222			`CLASS="PRODUCTNAME"`
223			`>eCos</SPAN`
224			`>`
225			`configurations rather than keep the configuration`
226			`information in the base of the build tree.</P`
227			`></DD`
228			`><DT`
229			`><TT`
230			`CLASS="OPTION"`
231			`>--prefix=<dir></TT`
232			`></DT`
233			`><DD`
234			`><P`
235			`>Specifies an alternative location for the`
236			`install tree. By default, the install tree resides`
237			`inside the <TT`
238			`CLASS="FILENAME"`
239			`>install</TT`
240			`>`
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`
245			`></DD`
246			`><DT`
247			`><TT`
248			`CLASS="OPTION"`
249			`>--srcdir=<dir></TT`
250			`></DT`
251			`><DD`
252			`><P`
253			`>Specifies the location of the component`
254			`repository. By default, the tool uses the location`
255			`specified in the`
256			`<TT`
257			`CLASS="REPLACEABLE"`
258			`><I`
259			`>ECOS_REPOSITORY</I`
260			`></TT`
261			`>`
262			`environment variable. Developers may prefer to use`
263			`of this qualifier if they are working with more than`
264			`one repository.</P`
265			`></DD`
266			`><DT`
267			`><TT`
268			`CLASS="OPTION"`
269			`>--no-resolve</TT`
270			`></DT`
271			`><DD`
272			`><P`
273			`>Disables the implicit resolution of conflicts`
274			`while manipulating the configuration data.`
275			`developers may prefer to resolve conflicts by`
276			`editing the <SPAN`
277			`CLASS="PRODUCTNAME"`
278			`>eCos</SPAN`
279			`> configuration save file`
280			`manually.</P`
281			`></DD`
282			`><DT`
283			`><TT`
284			`CLASS="OPTION"`
285			`>--ignore-errors</TT`
286			`>, <TT`
287			`CLASS="OPTION"`
288			`>-i</TT`
289			`></DT`
290			`><DD`
291			`><P`
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`
299			`></DD`
300			`><DT`
301			`><TT`
302			`CLASS="OPTION"`
303			`>--verbose</TT`
304			`>, <TT`
305			`CLASS="OPTION"`
306			`>-v</TT`
307			`></DT`
308			`><DD`
309			`><P`
310			`>Display more information.</P`
311			`></DD`
312			`><DT`
313			`><TT`
314			`CLASS="OPTION"`
315			`>--quiet</TT`
316			`>, <TT`
317			`CLASS="OPTION"`
318			`>-q</TT`
319			`></DT`
320			`><DD`
321			`><P`
322			`>Display less information.</P`
323			`></DD`
324			`></DL`
325			`></DIV`
326			`><P`
327			`>The <TT`
328			`CLASS="OPTION"`
329			`>--config</TT`
330			`>, <TT`
331			`CLASS="OPTION"`
332			`>--prefix</TT`
333			`> and`
334			`<TT`
335			`CLASS="OPTION"`
336			`>--srcdir</TT`
337			`> qualifiers can also be written with two arguments,`
338			`for example:</P`
339			`><TABLE`
340			`BORDER="5"`
341			`BGCOLOR="#E0E0F0"`
342			`WIDTH="70%"`
343			`><TR`
344			`><TD`
345			`><PRE`
346			`CLASS="SCREEN"`
347			`>ecosconfig --srcdir <TT`
348			`CLASS="REPLACEABLE"`
349			`><I`
350			`><dir></I`
351			`></TT`
352			`> ...</PRE`
353			`></TD`
354			`></TR`
355			`></TABLE`
356			`><P`
357			`>This simplifies filename completion with some shells.</P`
358			`></DIV`
359			`><DIV`
360			`CLASS="SECT2"`
361			`><H2`
362			`CLASS="SECT2"`
363			`><A`
364			`NAME="AEN2480">ecosconfig commands</H2`
365			`><P`
366			`>The available commands for`
367			`<B`
368			`CLASS="COMMAND"`
369			`>ecosconfig</B`
370			`> are as`
371			`follows:</P`
372			`><P`
373			`></P`
374			`><DIV`
375			`CLASS="VARIABLELIST"`
376			`><DL`
377			`><DT`
378			`><B`
379			`CLASS="COMMAND"`
380			`>list</B`
381			`></DT`
382			`><DD`
383			`><P`
384			`>Lists the available packages, targets and`
385			`templates as installed in the <SPAN`
386			`CLASS="PRODUCTNAME"`
387			`>eCos</SPAN`
388			`> repository.`
389			`Aliases and package versions are also`
390			`reported.</P`
391			`></DD`
392			`><DT`
393			`><B`
394			`CLASS="COMMAND"`
395			`>new <target> [<template> [<version>]]</B`
396			`></DT`
397			`><DD`
398			`><P`
399			`>Creates a new <SPAN`
400			`CLASS="PRODUCTNAME"`
401			`>eCos</SPAN`
402			`> configuration for`
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`
407			`version is used.</P`
408			`></DD`
409			`><DT`
410			`><B`
411			`CLASS="COMMAND"`
412			`>target <target></B`
413			`></DT`
414			`><DD`
415			`><P`
416			`>Changes the target hardware selection`
417			`for the <SPAN`
418			`CLASS="PRODUCTNAME"`
419			`>eCos</SPAN`
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`
425			`real hardware.</P`
426			`></DD`
427			`><DT`
428			`><B`
429			`CLASS="COMMAND"`
430			`>template <template> [<version>]</B`
431			`></DT`
432			`><DD`
433			`><P`
434			`>Changes the template selection for the <SPAN`
435			`CLASS="PRODUCTNAME"`
436			`>eCos</SPAN`
437			`>`
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`
443			`></DD`
444			`><DT`
445			`><B`
446			`CLASS="COMMAND"`
447			`>remove <packages></B`
448			`></DT`
449			`><DD`
450			`><P`
451			`>Removes the specified packages from the <SPAN`
452			`CLASS="PRODUCTNAME"`
453			`>eCos</SPAN`
454			`>`
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`
458			`></DD`
459			`><DT`
460			`><B`
461			`CLASS="COMMAND"`
462			`>add <packages></B`
463			`></DT`
464			`><DD`
465			`><P`
466			`>Adds the specified packages to the <SPAN`
467			`CLASS="PRODUCTNAME"`
468			`>eCos</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`
474			`explicitly. </P`
475			`></DD`
476			`><DT`
477			`><B`
478			`CLASS="COMMAND"`
479			`>version <version> <packages></B`
480			`></DT`
481			`><DD`
482			`><P`
483			`>Selects the specified version of a`
484			`number of packages in the <SPAN`
485			`CLASS="PRODUCTNAME"`
486			`>eCos</SPAN`
487			`> configuration. By`
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`
491			`></DD`
492			`><DT`
493			`><B`
494			`CLASS="COMMAND"`
495			`>check</B`
496			`></DT`
497			`><DD`
498			`><P`
499			`>Presents the following information`
500			`concerning the current configuration:</P`

Browse

Tools

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [rtos/] [ecos-2.0/] [doc/] [html/] [user-guide/] [creating-build-tree.html] - Blame information for rev 646