3 <!-- =============================================================== -->
5 <!-- config-tool.sgml -->
7 <!-- eCos User Guide -->
9 <!-- =============================================================== -->
10 <!-- ####COPYRIGHTBEGIN#### -->
12 <!-- =============================================================== -->
13 <!-- Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002 Red Hat, Inc. -->
14 <!-- This material may be distributed only subject to the terms -->
15 <!-- and conditions set forth in the Open Publication License, v1.0 -->
16 <!-- or later (the latest version is presently available at -->
17 <!-- http://www.opencontent.org/openpub/) -->
18 <!-- Distribution of the work or derivative of the work in any -->
19 <!-- standard (paper) book form is prohibited unless prior -->
20 <!-- permission obtained from the copyright holder -->
21 <!-- =============================================================== -->
23 <!-- ####COPYRIGHTEND#### -->
24 <!-- =============================================================== -->
25 <!-- #####DESCRIPTIONBEGIN#### -->
27 <!-- ####DESCRIPTIONEND#### -->
28 <!-- =============================================================== -->
32 <part ID="THE-ECOS-CONFIGURATION-TOOL">
33 <TITLE>The eCos Configuration Tool</TITLE>
35 <!-- {{{ Getting Started -->
37 <CHAPTER id="config-tool-getting-started">
38 <TITLE>Getting Started</TITLE>
40 <!-- ====================================================================== -->
42 <SECT1 id="config-tool-getting-started-intro">
43 <TITLE>Introduction</TITLE>
45 <PARA> The <productname>eCos</productname> <application>Configuration Tool</application> is used
46 to tailor <productname>eCos</productname> at source level, prior to compilation or
47 assembly, and provides a configuration file and a set of
48 files used to build user applications. The sources and other
49 files used for building a configuration are provided in a
50 <EMPHASIS>component repository</EMPHASIS>, which is loaded
51 when the <productname>eCos</productname> <APPLICATION>Configuration Tool</APPLICATION>
52 is invoked. The component repository includes a set of files
53 defining the structure of relationships between the
54 <application>Configuration Tool</application> and other components, and is written in a
55 <FIRSTTERM>Component Definition Language</FIRSTTERM> (<ACRONYM>CDL</ACRONYM>).
56 For a description of the concepts underlying component
57 configuration, see <xref linkend="cdl-concepts">.</PARA>
60 <!-- ====================================================================== -->
62 <SECT1 id="config-tool-invoking">
63 <TITLE>Invoking the <productname>eCos</productname> <application>Configuration Tool</application></TITLE>
66 <TITLE>On Linux</TITLE>
68 <PARA>Add the <productname>eCos</productname> <application>Configuration Tool</application> install directory to your PATH, for example:</PARA>
71 export PATH=/opt/ecos/ecos<replaceable>&Version;</replaceable>/bin:$PATH
74 <PARA>You may run configtool with zero, one or two arguments. You can specify the <productname>eCos</productname> repository
75 location, and/or an <productname>eCos</productname> save file (extension .ecc) on the command line. The ordering of these
76 two arguments is not significant. For example:</PARA>
79 configtool /opt/ecos/ecos<replaceable>&Version;</replaceable>/packages myfile.ecc
82 <PARA>The <application>Configuration Tool</application> will be displayed (see <xref linkend="figure-configuration-tool">).</PARA>
86 <TITLE>On Windows</TITLE>
88 <PARA>There are two ways in which to invoke the <productname>eCos</productname> <application>Configuration Tool</application>:</PARA>
91 <PARA> from the desktop explorer or program set up at installation
93 <EMPHASIS>Start</EMPHASIS>
95 <EMPHASIS>Programs</EMPHASIS>
97 <EMPHASIS>eCos</EMPHASIS>
99 <EMPHASIS>Configuration Tool</EMPHASIS>
103 <PARA>type (at a command prompt or in the
104 <EMPHASIS>Start</EMPHASIS>
106 <EMPHASIS>Run</EMPHASIS>
107 item): <foldername>\ConfigTool.exe where <foldername> is
108 the full path of the directory in which you installed the <productname>eCos</productname>
109 <application>Configuration Tool</application>.</PARA>
112 XXXXX Change location of configtool in line with installation
120 <application>Configuration Tool</application>
121 will be displayed (see <xref linkend="figure-configuration-tool">).</PARA>
126 You may run configtool with zero, one or two arguments. You can specify the <productname>eCos</productname> repository
127 location, and/or an <productname>eCos</productname> save file (extension .ecc) on the command line. The ordering of these
128 two arguments is not significant. For example:</PARA>
131 configtool "c:\Program Files\eCos\packages" myfile.ecc
136 XXXXX Change location of eCos in line with installation instructions. XXXXX
140 <PARA>If you invoke the configuration tool from the command line with
141 <EMPHASIS>--help</EMPHASIS>, you will see this output:</PARA>
144 Usage: eCos Configuration Tool [-h] [-e] [-v] [-c] [input file 1] [input file 2]
145 -h --help displays help on the command line parameters
146 -e --edit-only edit save file only
147 -v --version print version
148 -c --compile-help compile online help only
151 <PARA>This summarizes valid parameters and switches. Switches are shown with
152 both short form and long form.</PARA>
154 <PARA><EMPHASIS>--help</EMPHASIS> shows valid options and parameters, as above.</PARA>
156 <PARA><EMPHASIS>--edit-only</EMPHASIS> runs the <application>Configuration Tool</application> in a mode that
157 suppresses creation of a build tree, in case you only want to create and edit save files.</PARA>
159 <PARA><EMPHASIS>--version</EMPHASIS> shows version and build date information, and exits.</PARA>
161 <PARA><EMPHASIS>--compile-help</EMPHASIS> compiles help contents files from the HTML documentation
162 files that the tool finds in the <productname>eCos</productname> repository, and exits.</PARA>
164 <FIGURE id="figure-configuration-tool">
165 <TITLE><application>Configuration Tool</application></TITLE>
166 <GRAPHIC ENTITYREF="graphic1"></GRAPHIC>
171 <!-- ====================================================================== -->
174 <SECT1 id="config-tool-component-repository">
175 <TITLE>The Component Repository</TITLE>
176 <PARA>When you invoke the <productname>eCos</productname> <application>Configuration Tool</application>, it accesses the Component
177 Repository, a read-only location of configuration
178 information. For an explanation of “Component
179 Repository” see <xref linkend="cdl-concepts">.</PARA>
180 <PARA>The <productname>eCos</productname> <application>Configuration Tool</application> will look
181 for a component repository using (in descending order of preference):</PARA>
184 <PARA>A location specified on the command line
188 <PARA>The component repository most recently used by the
192 <PARA>An <productname>eCos</productname> distribution under <filename>/opt/ecos</filename> (under
193 Linux) or a default location set by the installation procedure (under
197 <PARA>User input</PARA>
200 <PARA>The final case above will normally only occur if the previous
201 repository has been moved or (under Windows) installation information stored in
202 the Windows registry has been modified; it will result in a dialog box
203 being displayed that allows you to specify the repository location:</PARA>
205 <TITLE>Repository relocation dialog box</TITLE>
206 <GRAPHIC ENTITYREF="graphic2"></GRAPHIC>
208 <PARA>Note that in order to use the <productname>eCos</productname> <application>Configuration Tool</application> you are obliged to provide a
209 valid repository location. </PARA>
210 <PARA>In the rare event that you subsequently wish to change
211 the component location, select
212 <EMPHASIS>Build</EMPHASIS>-><EMPHASIS>Repository</EMPHASIS>
213 and the above dialog box will then be displayed.</PARA>
214 <PARA>You can check the location of the current repository, the current save file
215 path, and the current hardware template and default package,
216 by selecting <EMPHASIS>Help</EMPHASIS>-><EMPHASIS>Repository Information...</EMPHASIS>.
217 A summary will be displayed.</PARA>
220 <!-- ====================================================================== -->
223 <SECT1 ID="config-tool-documents">
224 <TITLE><productname>eCos</productname> <application>Configuration Tool</application> Documents</TITLE>
226 <TITLE>Configuration Save File</TITLE>
227 <PARA><productname>eCos</productname> configuration settings and other information
228 (such as disabled conflicts) that are set using the
229 <productname>eCos</productname> <application>Configuration Tool</application> are saved to
230 a file between sessions. By default, when the
231 <productname>eCos</productname> <application>Configuration Tool</application> is first
232 invoked, it reads and displays information from the
233 Component Registry and displays the information in an
234 untitled blank document. You can perform the following
235 operations on a document:</PARA>
237 <TITLE>Save the currently active document</TITLE>
238 <PARA>Use the “<EMPHASIS>File->Save</EMPHASIS>” menu
239 item or click the <EMPHASIS>Save Document</EMPHASIS> icon on the
240 toolbar; if the current document is unnamed, you will be prompted
241 to supply a name for the configuration save file.</PARA>
243 <TITLE>Save As dialog box</TITLE>
244 <GRAPHIC ENTITYREF="graphic3"></GRAPHIC>
248 <TITLE>Open an existing document</TITLE>
249 <PARA>Select <EMPHASIS>File</EMPHASIS>-><EMPHASIS>Open</EMPHASIS>,
250 or click the <EMPHASIS>Open Document</EMPHASIS> icon on the toolbar.
251 You will be prompted to supply a name for the configuration save
254 <TITLE>Open dialog box</TITLE>
255 <GRAPHIC ENTITYREF="graphic4"></GRAPHIC>
259 <TITLE>Open a document you have used recently</TITLE>
260 <PARA>Click its name at the bottom of the
261 <EMPHASIS>File</EMPHASIS> menu. </PARA>
262 <PARA>Documents may also be opened by:</PARA>
265 <PARA>double-clicking a Configuration Save File in the desktop
266 explorer (Windows only);</PARA>
269 <PARA>invoking the <productname>eCos</productname>
270 <application>Configuration Tool</application>
271 with the name of a Configuration File as command-line argument,
272 or by creating a shortcut to the <productname>eCos</productname> <application>Configuration Tool</application> with such an argument
273 (under Windows or a suitable Linux desktop environment).</PARA>
278 <TITLE>Create a new blank document based on the Component
280 <PARA>Select <EMPHASIS>File</EMPHASIS>-><EMPHASIS>New</EMPHASIS>,
281 or click the <EMPHASIS>New Document</EMPHASIS> icon on the toolbar.</PARA>
284 <TITLE>Save to a different file name</TITLE>
285 <PARA>Select <EMPHASIS>File</EMPHASIS>-><EMPHASIS>Save
286 As</EMPHASIS>. You will be prompted to supply a new
287 name for the configuration save file.</PARA>
291 <TITLE>Build and Install Trees</TITLE>
292 <PARA>The location of the build and install trees are
293 derived from the <productname>eCos</productname> save file name as illustrated in the
294 following example:</PARA>
295 <PARA>Save file name = “c:\My
296 eCos\config1.ecc”</PARA>
297 <PARA>Install tree folder = “c:\My
298 eCos\config1_install”</PARA>
299 <PARA>Build tree folder = “c:\My
300 eCos\config1_build”</PARA>
301 <PARA>These names are automatically generated from the name
302 of the save file.</PARA>
303 <PARA>See also <xref linkend="cdl-concepts">.</PARA>
309 <!-- {{{ Getting Help -->
311 <CHAPTER id="config-tool-getting-help">
312 <TITLE>Getting Help</TITLE>
314 <PARA>The <productname>eCos</productname> <application>Configuration Tool</application> contains
315 several methods for accessing online help.</PARA>
317 <!-- ================================================== -->
319 <SECT1 id="config-tool-context-help-dialogs">
321 <TITLE>Context-sensitive Help for Dialogs</TITLE>
322 <PARA>Most dialogs displayed by the <productname>eCos</productname> <application>Configuration Tool</application> are supplied
323 with context-sensitive help. You can then get help relating
324 to any control within the current dialog box by</PARA>
328 <PARA>Right-clicking the control (or pressing
329 <EMPHASIS>F1</EMPHASIS>
331 <PARA>A “What’s This?” popup menu will
332 be displayed. Click the menu to display a brief description of the
333 function of the selected control.</PARA>
336 <PARA>Clicking the question mark icon in the dialog
337 caption bar (Windows) or the question mark button on the dialog (Linux).</PARA>
338 <PARA>A question mark cursor will be displayed. Click on
339 any control to display a brief description of its
343 <PARA>Some dialogs may have a <EMPHASIS>Help</EMPHASIS>
344 button. You can press this to display a more general
345 description of the function of the dialog box as a whole.
346 This help will be in HTML form; for more information, see
350 <!-- ================================================== -->
352 <SECT1 id="config-tool-context-help-otherwin">
353 <TITLE>Context-sensitive Help for Other Windows</TITLE>
354 <PARA>In the <EMPHASIS>Help</EMPHASIS> menu, click
355 <EMPHASIS>Help On...</EMPHASIS>
358 <EMPHASIS>F1</EMPHASIS>)
360 and then click on a window (or click on the arrow/question mark button
361 on the toolbar, then click on a window). A small popup window page describing the
362 window will be displayed. The same thing can be achieved by right-clicking
363 on a window and clicking on <EMPHASIS>What's This?</EMPHASIS>.
365 This help will normally be in HTML format; for more
366 information, see <xref linkend="methods-of-displaying-html-help">.
370 <SECT1 id="config-tool-context-help-config-items">
371 <TITLE>Context-sensitive Help for Configuration Items</TITLE>
372 <PARA>In the configuration window, right-click on a configuration
373 item (or use <EMPHASIS>Shift+F10</EMPHASIS>). A context
374 menu will be displayed; select <EMPHASIS>Visit Documentation</EMPHASIS>
375 to display the page in the <productname>eCos</productname> documentation that most closely
376 corresponds to the selected item.</PARA>
379 <SECT1 id="methods-of-displaying-html-help">
380 <TITLE>Methods of Displaying HTML Help</TITLE>
386 Using the internal help system. This will show an internal viewer similar to Microsoft HTML Help, with a contents
387 hierarchy on the left and HTML pages on the right; see <xref linkend="figure-help-viewer">. The index is regenerated for each repository. If the documentation in
388 the repository has changed but the contents does not reflect this, please use the Tools Regenerate Help Index menu
395 Using the default HTML browser. On Unix, you will need a .mailcap entry similar to this:
400 text/html; netscape -no-about-splash %s
407 Using the specified browser.
414 <FIGURE id="figure-help-viewer">
415 <TITLE>HTML Help viewer</TITLE>
416 <GRAPHIC ENTITYREF="graphic5"></GRAPHIC>
418 <PARA>If you wish, you may choose to have <EMPHASIS>HTML Help</EMPHASIS> displayed
419 in a browser of your choice. To do this, select <EMPHASIS>View</EMPHASIS>-><EMPHASIS>Settings</EMPHASIS> and
420 use the controls in the View Documentation group to select the replacement browser.
421 Note that the Navigation facilities of the built-in <EMPHASIS>HTML
422 Help</EMPHASIS> system will be unavailable if you choose this method
423 of displaying help.</PARA>
428 <!-- {{{ Customization -->
430 <CHAPTER id="config-tool-customization">
431 <TITLE>Customization</TITLE>
432 <PARA>The following visual aspects of the <productname>eCos</productname> <application>Configuration Tool</application> can be changed to suit
433 individual preferences. These aspects are saved on a per-user
434 basis, so that when the <productname>eCos</productname> <application>Configuration Tool</application> is next invoked by the same
435 user, the appearance will be as set in the previous
437 <SECT1 id="config-tool-window-placement">
438 <TITLE>Window Placement</TITLE>
439 <PARA>The relative sizes of all windows in the <productname>eCos</productname> <application>Configuration Tool</application> may be adjusted by dragging
440 the splitter bars that separate the windows. The chosen
441 sizes will be used the next time the <productname>eCos</productname> <application>Configuration Tool</application> is invoked by the current
443 <PARA>All windows except the <EMPHASIS>Configuration
444 Window</EMPHASIS> may be shown or hidden by using the
445 commands under the <EMPHASIS>View</EMPHASIS> menu (for
446 example, <EMPHASIS>View->Output</EMPHASIS>) or the
447 corresponding keyboard accelerators
448 (<EMPHASIS>Alt+1</EMPHASIS> to
449 <EMPHASIS>Alt+4</EMPHASIS>).
452 conflicts window is hidden.
455 <PARA>Your chosen set of windows (and their relative sizes) will
456 be preserved between invocations of the <productname>eCos</productname> <application>Configuration
457 Tool</application>.</PARA>
460 <SECT1 id="config-tool-toolbars">
461 <TITLE>Toolbars</TITLE>
463 <EMPHASIS>View</EMPHASIS>-><EMPHASIS>Toolbars</EMPHASIS>:
464 each of the standard and Memory Layout toolbars may be
465 hidden or shown.</PARA>
468 <SECT1 id="config-tool-settings">
469 <TITLE>Settings</TITLE>
470 <PARA>To change other visual aspects, select
471 <EMPHASIS>View</EMPHASIS>-><EMPHASIS>Settings</EMPHASIS>
472 and then select the <EMPHASIS>Display</EMPHASIS> and
473 <EMPHASIS>View</EMPHASIS> tabs depending on the settings
475 The options are as follows:
480 <TITLE>Settings: Display tab</TITLE>
483 <TITLE>Settings dialog, Display tab</TITLE>
484 <GRAPHIC ENTITYREF="graphic32"></GRAPHIC>
488 <TITLE>Labels</TITLE>
490 <PARA>In the configuration window, you can choose to have
491 either <EMPHASIS>descriptive names</EMPHASIS> (the
492 default) or <EMPHASIS>macro names</EMPHASIS> displayed as
493 tree item labels. Descriptive names are generally more
494 comprehensible, but macro names are used in some contexts
495 such as conflict resolution and may be directly related to
496 the source code of the configuration. Note that it is
497 possible to search for an item in the configuration view
499 <EMPHASIS>Find</EMPHASIS>-><EMPHASIS>Edit</EMPHASIS>
500 (see <xref linkend="config-tool-searching">). Both
501 descriptive names and macro names can be searched.</PARA>
505 <TITLE>Integer Items</TITLE>
506 <PARA>You can choose to have integer items in the
507 Configuration Window displayed in decimal or hexadecimal
515 Change the font for a particular window by selecting the window name using the drop-down list,
516 then clicking on <EMPHASIS>Change Font</EMPHASIS> to select a font for that
517 window. The changes will be applied when the press <EMPHASIS>OK</EMPHASIS> to dismiss the Settings dialog.
518 If you never make font changes, then the windows will take
519 the default setting determined by your current Windows or Unix environment.
524 <TITLE>Miscellaneous</TITLE>
527 If the <EMPHASIS>Splash Screen</EMPHASIS> checkbox is checked, a <EMPHASIS>splash</EMPHASIS>
528 window will appear as the application is loading. Uncheck this to eliminate the splash screen.
535 <TITLE>Settings: Viewers tab</TITLE>
538 <TITLE>Settings dialog, Viewers tab</TITLE>
539 <GRAPHIC ENTITYREF="graphic6"></GRAPHIC>
543 <TITLE>View header files</TITLE>
545 <PARA>You can change the viewer used to display header files.</PARA>
549 <TITLE>View documentation</TITLE>
551 <PARA>You can change the viewer used to display HTML files.
552 See <xref linkend="methods-of-displaying-html-help">.
565 <!-- {{{ Screen Layout -->
567 <CHAPTER id="config-tool-screen-layout">
568 <TITLE>Screen Layout</TITLE>
569 <PARA>The following windows are available within the
570 <productname>eCos</productname> <application> Configuration
575 <PARA> Configuration Window</PARA>
578 <PARA> Properties Window</PARA>
581 <PARA> Short Description</PARA>
584 <PARA> Conflicts</PARA>
591 <PARA>The layout of the windows may be adjusted to suit your
592 preferences: see <xref linkend="config-tool-settings">.</PARA>
594 <SECT1 id="config-tool-configuration-window">
595 <TITLE>Configuration Window</TITLE>
596 <PARA>This is the principal window used to configure <productname>eCos</productname>. It
597 takes the form of a tree-based representation of the
598 configuration items within the currently loaded <productname>eCos</productname>
600 <PARA>In the case of items whose values may be changed,
601 controls are available to set the item values. These either
602 take the form of check boxes or radio buttons within the
603 tree itself or cells to the right of the thin vertical
604 splitter bar. Controls in the tree may be used in the usual
605 way; cells, however, must first be activated.</PARA>
606 <PARA>To activate a cell, simply click on it: it will assume a sunken
607 appearance and data can then be edited in the cell. To terminate
608 in-cell editing, click elsewhere in the configuration window or
609 press <EMPHASIS>ENTER</EMPHASIS>. To discard the partial results
610 of in-cell editing and revert to the previous value, press <EMPHASIS>ESCAPE</EMPHASIS>.
611 <!-- Not yet implemented
612 Note that an asterisk appears against configuration items which have changed since the configuration
616 <PARA><GRAPHIC ENTITYREF="graphic7"></GRAPHIC></PARA>
617 <PARA>Cells come in three varieties, according to the type of
618 data they accept:</PARA>
620 <TITLE>Cell types</TITLE>
624 <ENTRY>Cell Type</ENTRY>
625 <ENTRY><PARA>Data Accepted</PARA></ENTRY>
630 <ENTRY>Integer</ENTRY>
631 <ENTRY>Decimal or hexadecimal values</ENTRY>
634 <ENTRY>Floating Point</ENTRY>
635 <ENTRY>Floating point values</ENTRY>
638 <ENTRY>String</ENTRY>
645 <cell><normal>Integer</normal></cell><cell><normal>Decimal or hexadecimal
646 values</normal></cell></row>
648 <cell><normal>Floating Point</normal></cell><cell><normal>Floating
649 point values</normal></cell></row>
651 <cell><normal>String</normal></cell><cell><normal>Any</normal></cell></row>
654 <PARA>In the case of string cells, you can double-click the cell
655 to display a dialog box containing a larger region in which to edit
656 the string value. This is useful in the case of long strings, or
657 those spanning multiple lines.</PARA>
659 <TITLE>Disabled items</TITLE>
660 <PARA>Some items will appear disabled. In this case the item
661 label and any associated controls and cells will be
662 grayed. It is not be possible to change the values of
663 disabled items.</PARA>
665 <TITLE>Right-Clicking</TITLE>
666 <PARA>You can right-click on an item in the configuration
667 window item to display a pop-up menu which (depending on
668 the type of the item selected) allows you to:</PARA>
671 <PARA> <EMPHASIS>Properties</EMPHASIS> –
672 information relating to the currently selected item
673 is displayed. The information is equivalent to that
674 displayed in the Properties
678 <PARA> <EMPHASIS>Restore Defaults</EMPHASIS> -
679 the default value of the currently selected item is
683 <PARA><EMPHASIS>Visit Documentation</EMPHASIS>
684 - causes the HTML page most closely relating to the
685 currently selected item to be displayed. This has
686 the same effect as double-clicking the URL property
687 in the Properties Window.</PARA>
690 <PARA> <EMPHASIS>View Header File</EMPHASIS>
691 – this causes the file containing the items to
692 be displayed. This is equivalent to double-clicking
693 on the File property in the Properties Window. The
694 viewer used for this purpose may be changed using
695 the <EMPHASIS>View->Settings</EMPHASIS> menu item
696 (see <xref linkend="config-tool-settings">).
697 Note that this operation is only possible when the
698 current configuration is saved, in order to avoid
699 the possibility of changing the source
703 <PARA><EMPHASIS>Unload Package</EMPHASIS> -
704 this is equivalent to using the
705 <EMPHASIS>Build->Packages</EMPHASIS> menu item to
706 select and unload the package in
713 <TITLE>Conflicts Window</TITLE>
714 <PARA>This window exists to display any configuration item
715 conflicts. Conflicts are the result of failures to meet
716 the requirements between configuration items expressed in
717 the CDL. See <xref linkend="cdl-conflicts"> <!--in “CDL
718 Concepts” on page 45 -->.<GRAPHIC ENTITYREF="graphic8"></GRAPHIC></PARA>
719 <PARA>The window comprises three columns:</PARA>
722 <PARA> <EMPHASIS>Item</EMPHASIS></PARA>
723 <PARA>This is the macro name of the first item involved
724 in the conflict.</PARA>
728 <EMPHASIS>Conflict</EMPHASIS></PARA>
729 <PARA>This is a description of the conflict type. The currently
730 supported types are “unresolved”, “illegal
731 value”, “evaluation exception”, “goal
732 unsatisfied” and “bad data”.</PARA>
736 <EMPHASIS>Property</EMPHASIS></PARA>
737 <PARA>This contains a description of the configuration
738 item’s property that caused the conflict.</PARA>
739 <PARA>Within the conflicts window you can right-click on
740 any item to display a context menu which allows you to
741 choose from one of the following options:</PARA>
745 <PARA>To locate the item involved in the
746 conflict, double-click in the first or third column, or
747 right-click over the item and choose <EMPHASIS>Locate</EMPHASIS>
751 <PARA>You can use the <EMPHASIS>Tools->Resolve Conflicts</EMPHASIS> menu
752 item, or right-click over the item and select <EMPHASIS>Resolve</EMPHASIS> from the popup menu,
753 to resolve conflicts — <xref linkend="resolving-conflicts">.</PARA>
755 <TITLE>Output Window</TITLE>
756 <PARA>This window displays any output generated by
757 execution of external tools and any error messages that
758 are not suitable for display in other forms (for
759 example, as message boxes).</PARA>
760 <PARA>Within the output window you can right-click to display a
761 context menu which allows you to:</PARA>
764 <PARA>Save the contents of the window to a
768 <PARA>Clear the contents of the
774 <TITLE>Properties Window</TITLE>
775 <PARA>This window displays the CDL properties of the item
776 currently selected in the configuration window. The same
777 information may be displayed by right-clicking the item
778 and selecting “properties”.</PARA>
779 <PARA> <GRAPHIC ENTITYREF="graphic9"></GRAPHIC></PARA>
780 <PARA>Two properties may be double-clicked as
784 <PARA><EMPHASIS>URL</EMPHASIS> –
785 double-clicking on a URL property causes the
786 referenced HTML page to be displayed. This has the
787 same effect as right-clicking on the item and
788 choosing “Visit
789 Documentation”.</PARA>
792 <PARA><EMPHASIS>File</EMPHASIS> –
793 double-clicking on a File property in a saved
794 configuration causes the File to be displayed. The
795 viewer used for this purpose may be changed using
796 the <EMPHASIS>View->Settings</EMPHASIS> menu
797 item. Note that this operation is only possible when
798 the current configuration is saved, in order to
799 avoid the possibility of changing the source
805 <TITLE>Short Description Window</TITLE>
806 <PARA>This window displays a short description of the item
807 currently selected in the configuration window. More
808 extensive documentation may be available by
809 right-clicking on the item and choosing “Visit
810 Documentation”.</PARA>
817 <!-- {{{ Updating and Configuration -->
819 <CHAPTER id="config-tool-updating-configuration">
820 <TITLE>Updating the Configuration</TITLE>
821 <SECT1 id="config-tool-adding-removing-packages">
822 <TITLE>Adding and Removing Packages</TITLE>
823 <PARA>To add or remove packages from the configuration, select
824 <EMPHASIS>Build</EMPHASIS>-><EMPHASIS>Packages</EMPHASIS>.<!--<conditionaltext>-->
825 The following dialog box will be displayed:</PARA>
827 <TITLE>Packages dialog box</TITLE>
828 <GRAPHIC ENTITYREF="graphic14"></GRAPHIC>
830 <PARA>The left-hand list shows those packages that are available to
831 be loaded. The right-hand list shows those that are
832 currently loaded. In order to transfer packages from one
833 list to another (that is, to load or unload packages)
834 double-click the selection or click the
835 <EMPHASIS>Add</EMPHASIS> or <EMPHASIS>Remove</EMPHASIS>
838 <PARA>The version drop-down list displays the versions of the
839 selected packages. When loading packages, this control may
840 be used to load versions other than the most recent
841 (current). Note that if more than one package is selected,
842 the version drop-down list will display only the versions
843 common to all the selected packages.</PARA>
845 <PARA>The window under the version displays a brief
846 description of the selected package. If more than one
847 package is selected, this window will be blank.</PARA>
850 Under the description window there is a <EMPHASIS>Keywords</EMPHASIS>
851 control into which you can type a string to be matched against
852 package names, macro names and descriptions. The lists are updated
853 a second or so after typing has stopped.
854 If you type several separate words,
855 all of these words must be associated with a given package
856 for that package to be displayed. If you select
857 the <EMPHASIS>Match exactly</EMPHASIS> checkbox, then the string
858 is taken to be a complete fragment and matched against the beginning
859 of a name, macro name or descriptions. All matches are done
860 case-insensitively.</PARA>
863 If you check <EMPHASIS>Omit hardware packages</EMPHASIS>, only
864 non-hardware packages will be shown.
868 <SECT1 id="config-tool-platform-selection">
869 <TITLE>Platform Selection</TITLE>
870 <PARA>To add, modify or remove entries in the list of
871 platforms used for running tests, select
872 <EMPHASIS>Tools->Platforms</EMPHASIS>. The following
873 dialog will be displayed:</PARA>
875 <TITLE>Platforms dialog box</TITLE>
876 <GRAPHIC ENTITYREF="graphic15"></GRAPHIC>
878 <PARA>You may add, modify or remove platform entries as you
879 wish, but in order to run tests, a platform must be defined
880 to correspond to the currently loaded hardware template. The
881 information associated with each platform name is used to
883 <PARA>To modify a platform, click the
884 <EMPHASIS>Modify</EMPHASIS> button with the appropriate
885 platform selected, or double-click on an entry in the list.
886 A dialog will be displayed that allows you to change the
887 command prefix, platform type and arguments for
888 <EMPHASIS>GDB</EMPHASIS>. </PARA>
890 <TITLE>Platform Modify dialog box</TITLE>
891 <GRAPHIC ENTITYREF="graphic16"></GRAPHIC>
893 <PARA>To add a new platform, click the
894 <EMPHASIS>Add</EMPHASIS> button. A similar dialog will be
895 displayed that allows you to define a new platform. To
896 remove a platform, click the <EMPHASIS>Delete</EMPHASIS>
897 button or press the <EMPHASIS>DEL</EMPHASIS> key with the
898 appropriate platform selected.</PARA>
900 <PARA>The command prefix is used when running tests in order
901 to determine the names of the executables (such as gdb) to
902 be used. For example, if the gdb executable name is
903 “arm-elf-gdb.exe” the prefix should be set to
904 “arm-elf”.</PARA>
905 <PARA>The platform type indicates the capabilities of the platform
906 - whether it is hardware or a simulator, and whether breakpoints
907 are supported.</PARA>
908 <PARA>The arguments for the <EMPHASIS>GDB</EMPHASIS> field allow
909 additional arguments to be passed to gdb when it is used to run
910 a test. This is typically used in the case of simulators linked
911 to gdb in order to define memory layout.</PARA>
913 <SECT1 id="config-tool-using-templates">
914 <TITLE>Using Templates</TITLE>
915 <PARA>To load a configuration based on a template, select
916 <EMPHASIS>Build</EMPHASIS>-><EMPHASIS>Templates</EMPHASIS>.<!--<conditionaltext>--></PARA>
917 <PARA>The following dialog box will be displayed:</PARA>
919 <TITLE>Templates dialog box</TITLE>
920 <GRAPHIC ENTITYREF="graphic18"></GRAPHIC>
922 <PARA>Change the hardware template, the packages template, or
923 both. To select a hardware template, choose from the first
924 drop-list. To choose a packages template, choose from the
925 second. Brief descriptions of each kind of template are
926 provided in the corresponding edit boxes.</PARA>
927 <SECT2 id="resolving-conflicts">
928 <TITLE>Resolving conflicts</TITLE>
929 <PARA>During the process of configuring <productname>eCos</productname> it is possible
930 that conflicts will be created. For more details of the
931 meaning of conflicts, see <xref linkend="cdl-concepts">.</PARA>
932 <PARA>The Conflicts Window displays all conflicts in the
933 current configuration. Additionally, a window in the
934 status bar displays a count of the conflicts. Because the
935 resolution of conflicts can be time-consuming, a mechanism
936 exists whereby conflicts can be resolved
937 automatically.</PARA>
938 <PARA>You can choose to have a conflicts resolution dialog
939 box displayed by means of the <EMPHASIS>View->Settings...
940 <!--<conditionaltext>--></EMPHASIS>menu item, on the <EMPHASIS>Conflict Resolution</EMPHASIS>
941 tab of the dialog.</PARA>
943 <TITLE>Options</TITLE>
944 <GRAPHIC ENTITYREF="graphic19"></GRAPHIC>
946 <PARA>You can choose to have conflicts checked under the
947 following circumstances:</PARA>
950 <PARA>After any item is changed (in other words,
951 as soon as the conflict is created)</PARA>
954 <PARA>Before saving the configuration (including
961 <PARA>The method you chose depends on how much you need
962 your configuration to be free of conflicts. You may
963 want to avoid having to clean up all the conflicts at
964 once, or you may want to keep the configuration
965 consistent at all times. If you have major changes to
966 implement, which may resolve the conflicts, then you
967 might want to wait until after you have completed
968 these changes before you check for conflicts.</PARA>
969 <!-- <label>NOTE</label> -->
971 <PARA>If you choose to check conflicts after any item
972 is changed, only newly arising conflicts are displayed.
973 If you choose to check for conflicts before saving the
974 configuration, the complete set is
979 <TITLE>Automatic resolution</TITLE>
980 <PARA>If you check the “Automatically suggest
981 fixes” check box, a conflicts resolution dialog box
982 will be displayed whenever new conflicts are created. The
983 same dialog box may be displayed at any stage by means of
984 the <EMPHASIS>Tools->Resolve Conflicts</EMPHASIS>
985 <EMPHASIS><!--<conditionaltext>--></EMPHASIS>menu item.
987 <PARA>The conflicts resolution dialog box contains two major windows. </PARA>
989 <TITLE>Resolve conflicts window</TITLE>
990 <GRAPHIC ENTITYREF="graphic20"></GRAPHIC>
992 <PARA>The upper contains the set of conflicts to be addressed; the
993 format of the data being as that of the Conflicts Window. The lower
994 window contains a set of proposed resolutions – each entry
995 is a suggested configuration item value change that as a whole may
996 be expected to lead to the currently selected conflict being resolved. </PARA>
997 <PARA>Note that there is no guarantee:</PARA>
1000 <PARA>that automatic resolutions will be determinable for every
1004 <PARA> that the resolutions for separate conflicts will be independent.
1005 In other words, the resolution of one conflict may serve to prevent
1006 the resolution of another.</PARA>
1009 <PARA> that the resolution conflicts will not create further
1013 <PARA>The above warnings are, however, conservative. In practice
1014 (so long as the number and extent of conflicts are limited) automatic
1015 conflict resolution may be used to good effect to correct problems
1016 without undue amounts of programmer intervention.</PARA>
1017 <PARA>In order to select the conflicts to be applied, select or
1018 clear the check boxes against the resolutions for each proposed
1019 resolution. By default all resolutions are selected; you can return
1020 to the default state (in other words, cause all check boxes for
1021 each conflict to again become checked) by pressing the “Reset” button.
1022 Note that multiple selection may be used in the resolutions control
1023 to allow ranges of check boxes to be toggled in one gesture.</PARA>
1024 <PARA>When you are happy to apply the selected resolutions for each
1025 conflict displayed, click <EMPHASIS>Apply</EMPHASIS>; this will
1026 apply the resolutions. Alternatively you may cancel from the dialog
1027 box without any resolutions being applied.</PARA>
1033 <!-- {{{ Searching -->
1035 <CHAPTER id="config-tool-searching">
1036 <TITLE>Searching</TITLE>
1037 <PARA>Select <EMPHASIS>Edit </EMPHASIS>--> <EMPHASIS>Find</EMPHASIS>.
1038 You will be presented with a Find dialog box:</PARA>
1040 <TITLE>Find dialog box</TITLE>
1041 <GRAPHIC ENTITYREF="graphic21"></GRAPHIC>
1043 <PARA>Using this dialog box you can search for an exact text string
1044 in any one of three ways, as specified by your selection in the “Search
1045 in” drop-list:</PARA>
1048 <PARA>Macro names - the search is for a text match within
1049 configuration item macro names</PARA>
1052 <PARA> Item names - the search is for a text match within
1053 configuration item descriptive names</PARA>
1056 <PARA> Short descriptions - the search is for a text match
1057 within configuration item short descriptions</PARA>
1060 <PARA>Note that to invoke <EMPHASIS>Find</EMPHASIS> you can also
1061 click the <EMPHASIS>Find</EMPHASIS> icon on the toolbar. </PARA>
1065 <!-- {{{ Building -->
1067 <CHAPTER id="config-tool-building">
1068 <TITLE>Building</TITLE>
1069 <PARA>When you have configured <productname>eCos</productname>, you may build the configuration.</PARA>
1070 <PARA><!--<conditionaltext>-->On the <EMPHASIS>Build</EMPHASIS> menu, click:</PARA>
1074 <EMPHASIS>Library</EMPHASIS>
1075 (or click the Build Library icon on the toolbar) – this
1076 causes the <productname>eCos</productname> configuration to be built. The result of a successful
1077 build will be (among other things) a library against which user
1078 code can be linked</PARA>
1082 <EMPHASIS>Tests</EMPHASIS>
1083 – this causes the <productname>eCos</productname> configuration to be built, and
1084 additionally builds the relevant test cases linked against the <productname>eCos</productname> library</PARA>
1088 <EMPHASIS>Clean</EMPHASIS>
1089 – this removes all intermediate files, thus causing a
1090 subsequent build/library or build/tests operation
1091 to cause recompilation of all relevant files.</PARA>
1095 <EMPHASIS>Stop</EMPHASIS>
1096 – this causes a currently executing build (any of the
1097 above steps) to be interrupted</PARA>
1100 <PARA>Build options may be displayed by using the <EMPHASIS>Build->Options</EMPHASIS> menu
1101 item. This displays a dialog box containing a drop-list control
1102 and two windows. The drop-list control allows you to select the
1103 type of build option to be displayed (for example “LDFLAGS” are
1104 the options applied at link-time. The left-hand window is a tree
1105 view of the packages loaded in the current configuration. The right-hand
1106 window is a list of the build options that will be used for the
1107 currently selected package.</PARA>
1108 <PARA>Note that this dialog box currently affords only read-only
1109 access to the build options. In order to change build options you
1110 must edit the relevant string configuration item.</PARA>
1111 <PARA>A single level of inheritance is supported: each package’s
1112 build options are combined with the global options (these are to
1113 be found in the “Global build options” folder
1114 in the configuration view).</PARA>
1115 <PARA><GRAPHIC ENTITYREF="graphic22"></GRAPHIC></PARA>
1116 <SECT1 id="config-tool-selecting-build-tools">
1117 <TITLE>Selecting Build Tools</TITLE>
1118 <PARA>Normally the installation process will supply the information
1119 required for the <productname>eCos</productname><APPLICATION>Configuration Tool</APPLICATION> to
1120 locate the build tools (compiler, linker, etc.) necessary
1121 to perform a build. However if this information is not registered,
1122 or it is necessary to specify the location manually (for example,
1123 when a new toolchain installation has been made), select <EMPHASIS>Tools</EMPHASIS>-><EMPHASIS>Paths</EMPHASIS>-><EMPHASIS>Build
1124 Tools</EMPHASIS>. The following dialog box will be displayed:</PARA>
1126 <TITLE>Build tools</TITLE>
1127 <GRAPHIC ENTITYREF="graphic23"></GRAPHIC>
1129 <PARA>This dialog box allows you to locate the folder containing
1130 the build tools. </PARA>
1132 <SECT1 id="config-tool-selecting-user-tools">
1133 <TITLE>Selecting User Tools</TITLE>
1134 <PARA>Normally the installation process will supply the information
1135 required for the <productname>eCos</productname><APPLICATION>Configuration Tool</APPLICATION> to
1136 locate the user tools (cat, ls, etc.) necessary to perform
1137 a build. However if this information is not registered, or it is
1138 necessary to specify the location manually (for example, when a
1139 new toolchain installation has been made), select <EMPHASIS>Tools</EMPHASIS>-><EMPHASIS>Paths</EMPHASIS>-><EMPHASIS>User
1140 Tools</EMPHASIS>. The following dialog box will be displayed:</PARA>
1142 <TITLE>User tools</TITLE>
1143 <GRAPHIC ENTITYREF="graphic24"></GRAPHIC>
1149 <!-- {{{ Execution -->
1151 <CHAPTER id="config-tool-test-execution"><!--<conditionaltext>-->
1152 <TITLE>Execution</TITLE>
1153 <PARA>Test executables that have been linked using the Build/Tests
1154 operation against the current configuration can be executed by selecting <!--<conditionaltext>--><EMPHASIS>Tools</EMPHASIS>-><EMPHASIS>Run
1155 Tests<!--<conditionaltext>--></EMPHASIS>.</PARA>
1156 <PARA>When tests are run, the <application>Configuration Tool</application> looks
1157 for a platform name corresponding to the currently loaded hardware template.
1158 If no such platform is found, a dialog will be displayed for you
1159 to define one; this dialog is similar to that displayed by the <EMPHASIS>Add</EMPHASIS> function
1160 in the <EMPHASIS>Tools->Platforms</EMPHASIS> dialog, but
1161 in this case the platform name cannot be changed.</PARA>
1162 <PARA>When a test run is invoked, a property sheet is displayed,
1163 comprising three tabs: <EMPHASIS>Executables</EMPHASIS>, <EMPHASIS>Output</EMPHASIS> and <EMPHASIS>Summary</EMPHASIS>.</PARA>
1164 <PARA>Note that the property sheet is resizable.</PARA>
1165 <PARA>Three buttons appear on the property sheet itself: <EMPHASIS>Run/Stop</EMPHASIS>, <EMPHASIS>Close</EMPHASIS> and <EMPHASIS>Properties</EMPHASIS>.</PARA>
1166 <PARA>The <EMPHASIS>Run</EMPHASIS> button is used to initiate a
1167 test run. Those tests selected on the <EMPHASIS>Executables</EMPHASIS> tab
1168 are run, and the output recorded on the <EMPHASIS>Output</EMPHASIS> and <EMPHASIS>Summary</EMPHASIS> tabs.
1169 During the course of a run, the <EMPHASIS>Run</EMPHASIS> button
1170 changes to “Stop”. The button may be used to interrupt
1171 a test run at any point.</PARA>
1172 <SECT1 id="config-tool-test-properties">
1173 <TITLE>Properties</TITLE>
1174 <PARA>The <EMPHASIS>Properties</EMPHASIS> button is used to change
1175 the connectivity properties for the test run.</PARA>
1177 <TITLE>Properties dialog box</TITLE>
1178 <GRAPHIC ENTITYREF="graphic25"></GRAPHIC>
1181 <TITLE>Download Timeout</TITLE>
1182 <PARA> This group of controls serves to set the maximum time that
1183 is allowed for downloading a test to the target board. If
1184 the time is exceeded, the test will be deemed to have
1185 failed for reason of “Download Timeout” and
1186 the execution of that particular test will be abandoned.
1187 This option only applies to tests run on hardware, not to
1188 those executed in a simulator. Times are in units of
1189 elapsed seconds.</PARA>
1190 <PARA>Three options are available using the drop-down
1194 <PARA>Calculated from file size - an estimate of the maximum
1195 time required for download is made using the (stripped) executable
1196 size and the currently used baud rate</PARA>
1199 <PARA> Specified - a user-specified value may be entered in
1200 the adjacent edit box</PARA>
1203 <PARA> None - no maximum download time is to be applied.</PARA>
1208 <TITLE>Run time Timeout</TITLE>
1209 <PARA>This group of controls serves to set the maximum time
1210 that is allowed for executing a test on the target board
1211 or in a simulator. If the time is exceeded, the test will
1212 be deemed to have failed for reason of
1213 “Timeout” and the execution of that particular
1214 test will be abandoned. In the case of hardware, the time
1215 is measured in elapsed seconds: in the case of a simulator
1216 it is in CPU seconds.</PARA>
1217 <PARA>Three options are available using the drop-down
1221 <PARA>None - no maximum download time is to be
1225 <PARA>Specified - a user-specified value may be
1226 entered in the adjacent edit box</PARA>
1229 <PARA>Default - a default value of 30 seconds is
1235 <TITLE>Connection</TITLE>
1236 <PARA>The <EMPHASIS>Connection</EMPHASIS> controls may be used
1237 to specify how the target board is to be accessed.</PARA>
1239 <PARA>If the target board is connected using a serial cable, the <EMPHASIS>Serial</EMPHASIS> radio
1240 button should be checked. In this case you can select a port (COM1,
1241 COM2, …) and an appropriate baud rate using drop-list boxes.</PARA>
1242 <PARA>If the target board is accessed remotely using GDB remote
1243 protocol, the “TCP/IP” radio button should
1244 be checked. In this case you can select a host name and TCP/IP port
1245 number using edit boxes.</PARA>
1248 <TITLE>Executables Tab</TITLE>
1249 <PARA>This is used to adjust the set of tests available for execution.
1250 A check box against each executable name indicates whether that
1251 executable will be included when the <EMPHASIS>Run</EMPHASIS> button
1252 is pressed. The <EMPHASIS>Check All</EMPHASIS> and <EMPHASIS>Uncheck
1253 All</EMPHASIS> buttons may be used to check or uncheck all items.</PARA>
1254 <PARA>When the property sheet is first displayed, it will be pre-populated
1255 with those test executables that have been linked using the Build/Tests
1256 operation against the current configuration. </PARA>
1258 <TITLE>Run tests </TITLE>
1259 <GRAPHIC ENTITYREF="graphic27"></GRAPHIC>
1261 <PARA>You can right-click in the window to display a context menu
1262 containing <EMPHASIS>Add</EMPHASIS> and <EMPHASIS>Remove</EMPHASIS> items.
1263 Clicking <EMPHASIS>Remove</EMPHASIS> will remove those executables
1264 selected. Clicking <EMPHASIS>Add</EMPHASIS> will display a dialog
1265 box that allows you to add to the set of items. Equivalently the <EMPHASIS>Add</EMPHASIS> button
1266 may be used to add executables, and the <EMPHASIS>DEL</EMPHASIS> key
1267 may be used to remove them.</PARA>
1268 <PARA>You can use the <EMPHASIS>Add from Folder</EMPHASIS> button
1269 to add a number of executables in a specified folder (optionally
1270 including subfolders, if you click on <EMPHASIS>Yes</EMPHASIS> when
1273 <TITLE>Add files from folder </TITLE>
1274 <GRAPHIC ENTITYREF="graphic28"></GRAPHIC>
1278 <PARA>The “Add from subfolders” check box should
1279 be checked if you wish the search for executables to descend into
1280 subfolders (in the example above the whole of the C drive would
1281 be searched).</PARA>
1283 <PARA>The “Files of type” edit box should be used
1284 to specify the extension of those files to be matched [for
1285 example, “*.exe”].</PARA>
1289 <TITLE>Output Tab</TITLE>
1290 <PARA>This tab is used to display the output from running tests.
1291 The output can be saved to a file or cleared by means of the popup
1292 menu displayed when you right-click in the window.</PARA>
1295 <TITLE>Summary Tab</TITLE>
1296 <PARA>This tab is used to display a record, in summary form, of
1297 those tests executed. For each execution, the following information
1298 is displayed:</PARA>
1301 <PARA> <EMPHASIS>Time</EMPHASIS> - the date and time of execution</PARA>
1304 <PARA> <EMPHASIS>Host</EMPHASIS> - the host name of the machine
1305 from which the test was downloaded</PARA>
1308 <PARA> <EMPHASIS>Platform</EMPHASIS> - the platform on which
1309 the test was executed</PARA>
1312 <PARA> <EMPHASIS>Executable</EMPHASIS> - the executable (file
1313 name) of the test executed</PARA>
1316 <PARA> <EMPHASIS>Status</EMPHASIS> - the result of executing
1317 the test. This will be one of the following:</PARA>
1320 <PARA> Not started</PARA>
1323 <PARA>No result</PARA>
1326 <PARA>Inapplicable</PARA>
1332 <PARA>DTimeout</PARA>
1335 <PARA>Timeout</PARA>
1338 <PARA>Cancelled</PARA>
1344 <PARA>Assert fail</PARA>
1347 <PARA> <EMPHASIS>Size</EMPHASIS> - the size [stripped/unstripped] of
1348 the test executed</PARA>
1351 <PARA> <EMPHASIS>Download</EMPHASIS> - the download time [mm:ss/mm:ss] used.
1352 The first of the two times displayed represents the actual time
1353 used: the second the limit time.</PARA>
1356 <PARA> <EMPHASIS>Elapsed</EMPHASIS> - the elapsed time [mm:ss] used.</PARA>
1359 <PARA> <EMPHASIS>Execution</EMPHASIS> - the execution time
1360 [mm:ss/mm:ss] used. The first of the
1361 two times displayed represents the actual time used: the second
1362 the limit time.</PARA>
1365 <PARA>The output can be saved to a file or cleared by means of the
1366 popup menu displayed when you right-click in the window.</PARA>
1372 <!-- {{{ Creating a Shell -->
1374 <CHAPTER id="config-tool-creating-a-shell">
1375 <TITLE>Creating a Shell</TITLE>
1376 <PARA>To call up a shell window, select <EMPHASIS>Tools</EMPHASIS>-><EMPHASIS>Shell</EMPHASIS>.
1377 Under Windows, you will get a Cygwin shell similar to the one below. On Linux, you will
1378 get a standard Linux shell window.</PARA>
1379 <GRAPHIC ENTITYREF="graphic29"></GRAPHIC>
1380 <SECT1 id="config-tool-keyboard-accelerators">
1381 <TITLE>Keyboard Accelerators</TITLE>
1382 <PARA>The following table presents the list of keyboard accelerators
1383 that can be used with the <application>Configuration Tool</application>. </PARA>
1385 <table id="keyboard-accelerators"><title>Keyboard accelerators</title>
1389 <entry>Accelerator</entry>
1390 <entry>Action</entry>
1391 <entry>Remarks</entry>
1397 <entry><emphasis>Alt+1</emphasis></entry>
1398 <entry>hide/show properties window</entry>
1403 <entry><emphasis>Alt+2</emphasis></entry>
1404 <entry>hide/show output window</entry>
1405 <entry></entry></row>
1408 <entry><emphasis>Alt+3</emphasis></entry>
1409 <entry>hide/show short description window</entry>
1410 <entry></entry></row>
1413 <entry><emphasis>Alt+4</emphasis></entry>
1414 <entry>hide/show conflicts window</entry>
1419 <entry><emphasis>Ctrl+A</emphasis></entry>
1420 <entry>select all</entry><entry>output
1421 window and in-cell editing</entry></row>
1423 <entry><emphasis>Ctrl+C</emphasis></entry>
1424 <entry>copy</entry><entry>output window
1425 and in-cell editing</entry></row>
1427 <entry><emphasis>Ctrl+F</emphasis></entry>
1428 <entry>Edit->Find</entry><entry></entry></row>
1430 <entry><emphasis>Ctrl+N</emphasis></entry>
1431 <entry>File->New</entry><entry></entry></row>
1433 <entry><emphasis>Ctrl+O</emphasis></entry>
1434 <entry>File->Open</entry><entry></entry></row>
1436 <entry><emphasis>Ctrl+S</emphasis></entry>
1437 <entry>File->Save</entry><entry></entry></row>
1439 <entry><emphasis>Ctrl+V</emphasis></entry>
1440 <entry>Paste</entry><entry>in-cell editing
1443 <entry><emphasis>Ctrl+X</emphasis></entry>
1444 <entry>Cut</entry><entry>in-cell-editing
1447 <entry><emphasis>Ctrl+Z</emphasis></entry>
1448 <entry>Undo</entry><entry>in-cell editing
1451 <entry><emphasis>F1</emphasis></entry>
1452 <entry>Context-sensitive help</entry><entry></entry></row>
1454 <entry><emphasis>F3</emphasis></entry>
1455 <entry>Find next</entry><entry></entry></row>
1457 <entry><emphasis>F7</emphasis></entry>
1458 <entry>Build->Library</entry><entry></entry></row>
1460 <entry><emphasis>Shift+F7</emphasis></entry>
1461 <entry>Build->Tests</entry><entry></entry></row>
1463 <entry><emphasis>Alt+F6</emphasis></entry>
1464 <entry>View->Next window</entry>
1465 <entry></entry></row>
1467 <entry><emphasis>Shift+Alt+0</emphasis></entry>
1468 <entry>View->Previous window</entry>
1469 <entry></entry></row>
1471 <entry><emphasis>Shift+Ins</emphasis></entry>
1472 <entry>Paste</entry><entry>in-cell editing
1475 <entry><emphasis>Shift+F10</emphasis></entry>
1476 <entry>Display context menu</entry><entry>Configuration
1477 window</entry></row>
1479 <entry><emphasis>Alt+Enter</emphasis></entry>
1480 <entry>Display properties dialog box</entry>
1481 <entry>Configuration window</entry></row>
1483 <entry><emphasis>></emphasis></entry>
1484 <entry>Increment item value</entry><entry>Configuration
1485 window</entry></row>
1487 <entry><</entry><entry>Decrement
1488 item value</entry><entry>Configuration window</entry></row>
1490 <entry><emphasis>Space</emphasis></entry>
1491 <entry>Toggle item value</entry><entry>Configuration
1492 window</entry></row>
1504 <!-- Keep this comment at the end of the file
1509 sgml-namecase-general:t
1510 sgml-general-insert-case:lower
1511 sgml-minimize-attributes:nil
1512 sgml-always-quote-attributes:t
1515 sgml-parent-document:("user-guide.sgml" "book" "part")
1516 sgml-exposed-tags:nil
1517 sgml-local-catalogs:nil
1518 sgml-local-ecat-files:nil