config-tool.sgml

eCos操作系统源码

<LISTITEM>
<PARA>Save the contents of the window to a
		  file</PARA>
</LISTITEM>
<LISTITEM>
<PARA>Clear the contents of the
		  window</PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT3>
<SECT3>
<TITLE>Properties Window</TITLE>
<PARA>This window displays the CDL properties of the item
	      currently selected in the configuration window. The same
	      information may be displayed by right-clicking the item
	      and selecting &ldquo;properties&rdquo;.</PARA>
<PARA>	      <GRAPHIC ENTITYREF="graphic9"></GRAPHIC></PARA>
<PARA>Two properties may be double-clicked as
	    follows:</PARA>
<ITEMIZEDLIST>
<LISTITEM>
<PARA><EMPHASIS>URL</EMPHASIS> &ndash;
		  double-clicking on a URL property causes the
		  referenced HTML page to be displayed. This has the
		  same effect as right-clicking on the item and
		  choosing &ldquo;Visit
		  Documentation&rdquo;.</PARA>
</LISTITEM>
<LISTITEM>
<PARA><EMPHASIS>File</EMPHASIS> &ndash;
		  double-clicking on a File property in a saved
		  configuration causes the File to be displayed. The
		  viewer used for this purpose may be changed using
		  the <EMPHASIS>View-&gt;Settings</EMPHASIS> menu
		  item. Note that this operation is only possible when
		  the current configuration is saved, in order to
		  avoid the possibility of changing the source
		  repository.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT3>
<SECT3>
<TITLE>Short Description Window</TITLE>
<PARA>This window displays a short description of the item
	      currently selected in the configuration window. More
	      extensive documentation may be available by
	      right-clicking on the item and choosing &ldquo;Visit
	      Documentation&rdquo;.</PARA>
</SECT3>
</SECT2>
</SECT1>
</CHAPTER>

<!-- }}} -->  
<!-- {{{ Updating and Configuration     -->

<CHAPTER id="config-tool-updating-configuration">
<TITLE>Updating the Configuration</TITLE>
<SECT1 id="config-tool-adding-removing-packages">
<TITLE>Adding and Removing Packages</TITLE>
<PARA>To add or remove packages from the configuration, select
	  <EMPHASIS>Build</EMPHASIS>-&gt;<EMPHASIS>Packages</EMPHASIS>.<!--<conditionaltext>--> 
	    The following dialog box will be displayed:</PARA>
<FIGURE>
<TITLE>Packages dialog box</TITLE>
<GRAPHIC ENTITYREF="graphic14"></GRAPHIC>
</FIGURE>
<PARA>The left-hand list shows those packages that are available to
	  be loaded. The right-hand list shows those that are
	  currently loaded. In order to transfer packages from one
	  list to another (that is, to load or unload packages)
	  double-click the selection or click the
	  <EMPHASIS>Add</EMPHASIS> or <EMPHASIS>Remove</EMPHASIS>
	  buttons.</PARA>

<PARA>The version drop-down list displays the versions of the
	  selected packages. When loading packages, this control may
	  be used to load versions other than the most recent
	  (current). Note that if more than one package is selected,
	  the version drop-down list will display only the versions
	  common to all the selected packages.</PARA>

<PARA>The window under the version displays a brief
	  description of the selected package. If more than one
	  package is selected, this window will be blank.</PARA>

<PARA>
	Under the description window there is a <EMPHASIS>Keywords</EMPHASIS>
control into which you can type a string to be matched against
package names, macro names and descriptions. The lists are updated
a second or so after typing has stopped.
If you type several separate words,
all of these words must be associated with a given package
for that package to be displayed. If you select
the <EMPHASIS>Match exactly</EMPHASIS> checkbox, then the string
is taken to be a complete fragment and matched against the beginning
of a name, macro name or descriptions. All matches are done
case-insensitively.</PARA>

<PARA>
If you check <EMPHASIS>Omit hardware packages</EMPHASIS>, only
non-hardware packages will be shown.
</PARA>

</SECT1>
<SECT1 id="config-tool-platform-selection">
<TITLE>Platform Selection</TITLE>
<PARA>To add, modify or remove entries in the list of
	  platforms used for running tests, select
	  <EMPHASIS>Tools-&gt;Platforms</EMPHASIS>. The following
	  dialog will be displayed:</PARA>
<FIGURE>
<TITLE>Platforms dialog box</TITLE>
<GRAPHIC ENTITYREF="graphic15"></GRAPHIC>
</FIGURE>
<PARA>You may add, modify or remove platform entries as you
	  wish, but in order to run tests, a platform must be defined
	  to correspond to the currently loaded hardware template. The
	  information associated with each platform name is used to
	  run tests.</PARA>
<PARA>To modify a platform, click the
	  <EMPHASIS>Modify</EMPHASIS> button with the appropriate
	  platform selected, or double-click on an entry in the list.
	  A dialog will be displayed that allows you to change the
	  command prefix, platform type and arguments for
	  <EMPHASIS>GDB</EMPHASIS>. </PARA>
<FIGURE>
<TITLE>Platform Modify dialog box</TITLE>
<GRAPHIC ENTITYREF="graphic16"></GRAPHIC>
</FIGURE>
<PARA>To add a new platform, click the
	  <EMPHASIS>Add</EMPHASIS> button. A similar dialog will be
	  displayed that allows you to define a new platform. To
	  remove a platform, click the <EMPHASIS>Delete</EMPHASIS>
	  button or press the <EMPHASIS>DEL</EMPHASIS> key with the
	  appropriate platform selected.</PARA>

<PARA>The command prefix is used when running tests in order
	  to determine the names of the executables (such as gdb) to
	  be used. For example, if the gdb executable name is
	  &ldquo;arm-elf-gdb.exe&rdquo; the prefix should be set to
	  &ldquo;arm-elf&rdquo;.</PARA>
<PARA>The platform type indicates the capabilities of the platform
- whether it is hardware or a simulator, and whether breakpoints
are supported.</PARA>
<PARA>The arguments for the <EMPHASIS>GDB</EMPHASIS> field allow
additional arguments to be passed to gdb when it is used to run
a test.  This is typically used in the case of simulators linked
to gdb in order to define memory layout.</PARA>
</SECT1>
<SECT1 id="config-tool-using-templates">
<TITLE>Using Templates</TITLE>
<PARA>To load a configuration based on a template, select
	  <EMPHASIS>Build</EMPHASIS>-&gt;<EMPHASIS>Templates</EMPHASIS>.<!--<conditionaltext>--></PARA>
<PARA>The following dialog box will be displayed:</PARA>
<FIGURE>
<TITLE>Templates dialog box</TITLE>
<GRAPHIC ENTITYREF="graphic18"></GRAPHIC>
</FIGURE>
<PARA>Change the hardware template, the packages template, or
	  both. To select a hardware template, choose from the first
	  drop-list. To choose a packages template, choose from the
	  second. Brief descriptions of each kind of template are
	  provided in the corresponding edit boxes.</PARA>
<SECT2 id="resolving-conflicts">
<TITLE>Resolving conflicts</TITLE>
<PARA>During the process of configuring <productname>eCos</productname> it is possible
	    that conflicts will be created. For more details of the
	    meaning of conflicts, see <xref linkend="cdl-concepts">.</PARA>
<PARA>The Conflicts Window displays all conflicts in the
	    current configuration. Additionally, a window in the
	    status bar displays a count of the conflicts. Because the
	    resolution of conflicts can be time-consuming, a mechanism
	    exists whereby conflicts can be resolved
	    automatically.</PARA>
<PARA>You can choose to have a conflicts resolution dialog
	    box displayed by means of the <EMPHASIS>View-&gt;Settings...
	      <!--<conditionaltext>--></EMPHASIS>menu item, on the <EMPHASIS>Conflict Resolution</EMPHASIS>
tab of the dialog.</PARA>
<FIGURE>
<TITLE>Options</TITLE>
<GRAPHIC ENTITYREF="graphic19"></GRAPHIC>
</FIGURE>
<PARA>You can choose to have conflicts checked under the
	    following circumstances:</PARA>
<ITEMIZEDLIST>
<LISTITEM>
<PARA>After any item is changed (in other words,
		as soon as the conflict is created)</PARA>
</LISTITEM>
<LISTITEM>
<PARA>Before saving the configuration (including
		building)</PARA>
</LISTITEM>
<LISTITEM>
<PARA>Never</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>The method you chose depends on how much you need
		your configuration to be free of conflicts. You may
		want to avoid having to clean up all the conflicts at
		once, or you may want to keep the configuration
		consistent at all times. If you have major changes to
		implement, which may resolve the conflicts, then you
		might want to wait until after you have completed
		these changes before you check for conflicts.</PARA>
<!-- <label>NOTE</label> -->
<NOTE>
<PARA>If you choose to check conflicts after any item
	      is changed, only newly arising conflicts are displayed.
	      If you choose to check for conflicts before saving the
	      configuration, the complete set is
	      displayed.</PARA>
</NOTE>
</SECT2>
<SECT2>
<TITLE>Automatic resolution</TITLE>
<PARA>If you check the &ldquo;Automatically suggest
	    fixes&rdquo; check box, a conflicts resolution dialog box
	    will be displayed whenever new conflicts are created. The
	    same dialog box may be displayed at any stage by means of
	    the <EMPHASIS>Tools-&gt;Resolve Conflicts</EMPHASIS>
	    <EMPHASIS><!--<conditionaltext>--></EMPHASIS>menu item.
	    </PARA>
<PARA>The conflicts resolution dialog box contains two major windows. </PARA>
<FIGURE>
<TITLE>Resolve conflicts window</TITLE>
<GRAPHIC ENTITYREF="graphic20"></GRAPHIC>
</FIGURE>
<PARA>The upper contains the set of conflicts to be addressed; the
format of the data being as that of the Conflicts Window. The lower
window contains a set of proposed resolutions &ndash; each entry
is a suggested configuration item value change that as a whole may
be expected to lead to the currently selected conflict being resolved. </PARA>
<PARA>Note that there is no guarantee:</PARA>
<ITEMIZEDLIST>
<LISTITEM>
<PARA>that automatic resolutions will be determinable for every
conflict.</PARA>
</LISTITEM>
<LISTITEM>
<PARA>	that the resolutions for separate conflicts will be independent.
In other words, the resolution of one conflict may serve to prevent
the resolution of another.</PARA>
</LISTITEM>
<LISTITEM>
<PARA>	that the resolution conflicts will not create further
conflicts.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>The above warnings are, however, conservative. In practice
(so long as the number and extent of conflicts are limited) automatic
conflict resolution may be used to good effect to correct problems
without undue amounts of programmer intervention.</PARA>
<PARA>In order to select the conflicts to be applied, select or
clear the check boxes against the resolutions for each proposed
resolution. By default all resolutions are selected; you can return
to the default state (in other words, cause all check boxes for
each conflict to again become checked) by pressing the &ldquo;Reset&rdquo; button.
Note that multiple selection may be used in the resolutions control
to allow ranges of check boxes to be toggled in one gesture.</PARA>
<PARA>When you are happy to apply the selected resolutions for each
conflict displayed, click <EMPHASIS>Apply</EMPHASIS>; this will
apply the resolutions. Alternatively you may cancel from the dialog
box without any resolutions being applied.</PARA>
</SECT2>
</SECT1>
</CHAPTER>

<!-- }}} -->  
<!-- {{{ Searching                      -->

<CHAPTER id="config-tool-searching">
<TITLE>Searching</TITLE>
<PARA>Select <EMPHASIS>Edit </EMPHASIS>--&gt; <EMPHASIS>Find</EMPHASIS>.
You will be presented with a Find dialog box:</PARA>
<FIGURE>
<TITLE>Find dialog box</TITLE>
<GRAPHIC ENTITYREF="graphic21"></GRAPHIC>
</FIGURE>
<PARA>Using this dialog box you can search for an exact text string
in any one of three ways, as specified by your selection in the &ldquo;Search
in&rdquo; drop-list:</PARA>
<ITEMIZEDLIST>
<LISTITEM>
<PARA>Macro names - the search is for a text match within
configuration item macro names</PARA>
</LISTITEM>
<LISTITEM>
<PARA>			Item names - the search is for a text match within
configuration item descriptive names</PARA>
</LISTITEM>
<LISTITEM>
<PARA>			Short descriptions - the search is for a text match
within configuration item short descriptions</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>Note that to invoke <EMPHASIS>Find</EMPHASIS> you can also
click the <EMPHASIS>Find</EMPHASIS> icon on the toolbar. </PARA>
</CHAPTER>

<!-- }}} -->  
<!-- {{{ Building                       -->

<CHAPTER id="config-tool-building">
<TITLE>Building</TITLE>
<PARA>When you have configured <productname>eCos</productname>, you may build the configuration.</PARA>
<PARA><!--<conditionaltext>-->On the <EMPHASIS>Build</EMPHASIS> menu, click:</PARA>
<ITEMIZEDLIST>
<LISTITEM>
<PARA>			
<EMPHASIS>Library</EMPHASIS>
 (or click the Build Library icon on the toolbar) &ndash; this
causes the <productname>eCos</productname> configuration to be built. The result of a successful
build will be (among other things) a library against which user
code can be linked</PARA>
</LISTITEM>
<LISTITEM>
<PARA>			
<EMPHASIS>Tests</EMPHASIS>
 &ndash; this causes the <productname>eCos</productname> configuration to be built, and
additionally builds the relevant test cases linked against the <productname>eCos</productname> library</PARA>
</LISTITEM>
<LISTITEM>
<PARA>			
<EMPHASIS>Clean</EMPHASIS>
 &ndash; this removes all intermediate files, thus causing a
subsequent build/library or build/tests operation
to cause recompilation of all relevant files.</PARA>
</LISTITEM>
<LISTITEM>
<PARA>			
<EMPHASIS>Stop</EMPHASIS>
 &ndash; this causes a currently executing build (any of the
above steps) to be interrupted</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>Build options may be displayed by using the <EMPHASIS>Build-&gt;Options</EMPHASIS> menu
item. This displays a dialog box containing a drop-list control
and two windows. The drop-list control allows you to select the
type of build option to be displayed (for example &ldquo;LDFLAGS&rdquo; are
the options applied at link-time. The left-hand window is a tree
view of the packages loaded in the current configuration. The right-hand
window is a list of the build options that will be used for the
currently selected package.</PARA>
<PARA>Note that this dialog box currently affords only read-only
access to the build options. In order to change build options you
must edit the relevant string configuration item.</PARA>
<PARA>A single level of inheritance is supported: each package&rsquo;s
build options are combined with the global options (these are to
be found in the &ldquo;Global build options&rdquo; folder
in the configuration view).</PARA>
<PARA><GRAPHIC ENTITYREF="graphic22"></GRAPHIC></PARA>
<SECT1 id="config-tool-selecting-build-tools">
<TITLE>Selecting Build Tools</TITLE>
<PARA>Normally the installation process will supply the information
required for the <productname>eCos</productname><APPLICATION>Configuration Tool</APPLICATION> to
locate the build tools (compiler, linker, etc.) necessary
to perform a build. However if this information is not registered,
or it is necessary to specify the location manually (for example,
when a new toolchain installation has been made), select <EMPHASIS>Tools</EMPHASIS>-&gt;<EMPHASIS>Paths</EMPHASIS>-&gt;<EMPHASIS>Build
Tools</EMPHASIS>. The following dialog box will be displayed:</PARA>
<FIGURE>
<TITLE>Build tools</TITLE>
<GRAPHIC ENTITYREF="graphic23"></GRAPHIC>
</FIGURE>
<PARA>This dialog box allows you to locate the folder containing
the build tools. </PARA>
</SECT1>
<SECT1 id="config-tool-selecting-user-tools">
<TITLE>Selecting User Tools</TITLE>
<PARA>Normally the installation process will supply the information
required for the <productname>eCos</productname><APPLICATION>Configuration Tool</APPLICATION> to
locate the user tools (cat, ls, etc.) necessary to perform
a build. However if this information is not registered, or it is
necessary to specify the location manually (for example, when a
new toolchain installation has been made), select <EMPHASIS>Tools</EMPHASIS>-&gt;<EMPHASIS>Paths</EMPHASIS>-&gt;<EMPHASIS>User
Tools</EMPHASIS>. The following dialog box will be displayed:</PARA>
<FIGURE>
<TITLE>User tools</TITLE>
<GRAPHIC ENTITYREF="graphic24"></GRAPHIC>