Getting Started
To Contents | To previous page | To next page

## Getting Started

### Introduction

The eCos Configuration Tool is used to tailor eCos at source level, prior to compilation or assembly, and provides a configuration file and a set of files used to build user applications. The sources and other files used for building a configuration are provided in a component repository, which is loaded when the eCos Configuration Tool is invoked. The component repository includes a set of files defining the structure of relationships between the Configuration Tool and other components, and is written in a Component Definition Language (CDL). For a description of the concepts underlying component configuration, see CDL Concepts .

### Invoking the eCos Configuration Tool

There are two ways in which to invoke the eCos Configuration Tool:

- from the desktop explorer or program set up at installation time (by default Start Programs Red Hat eCos Configuration Tool ).

- type (at a command prompt or in the Start menu's Run item): <foldername>\ConfigTool.exe where <foldername> is the full path of the directory in which you installed the eCos Configuration Tool .

- The Configuration Tool will be displayed (see Figure 1 ).

Configuration Tool

### The Component Repository

When you invoke the eCos Configuration Tool, it accesses the Component Repository, a read-only location of configuration information. For an explanation of "Component Repository" see CDL Concepts .

The eCos Configuration Tool will look for a component repository using (in descending order of preference):

- The component repository most recently used by the current user

- A default location set by the installation procedure

- User input

The final case above will normally only occur if the previous repository has been moved or installation information stored in the NT registry has been modified; it will result in a dialog box being displayed that allows you to specify the repository location:

Repository relocation dialog box

Note that in order to use the eCos Configuration Tool you are obliged to provide a valid repository location.

In the rare event that you subsequently wish to change the component location, select Build Repository and the above dialog box will then be displayed.

### eCos Configuration Tool Documents

### Configuration Save File

eCos configuration settings and other information (such as disabled conflicts) that are set using the eCos Configuration Tool are saved to a file between sessions. By default, when the eCos Configuration Tool is first invoked, it reads and displays information from the Component Registry and displays the information in an untitled blank document. You can perform the following operations on a document:

#### Save the currently active document

Use the " FileSave " menu item or click the Save Document icon on the toolbar; if the current document is unnamed, you will be prompted to supply a name for the configuration save file.

Save As dialog box

#### Open an existing document

Select File Open, or click the Open Document icon on the toolbar. You will be prompted to supply a name for the configuration save file.

Open dialog box

#### Open a document you have used recently

Click its name at the bottom of the File menu.

Documents may also be opened by:

- dragging and dropping a Configuration Save File from the desktop explorer to the eCos Configuration Tool

- double-clicking a Configuration Save File in the desktop explorer

- invoke the eCos Configuration Tool with the name of a Configuration File as command-line argument, or by creating a shortcut to the eCos Configuration Tool with such an argument.

#### Create a new blank document based on the Component Registry

Select File New, or click the New Document icon on the toolbar.

#### Save to a different file name

Select File Save As. You will be prompted to supply a new name for the configuration save file.

### Build and Install Trees

The location of the build and install trees are derived from the eCos save file name as illustrated in the following example:

Save file name = "c:\My eCos\config1.ecc"

Install tree folder = "c:\My eCos\config1_install"

Build tree folder = "c:\My eCos\config1_build"

These names are automatically generated from the name of the save file.

See also CDL Concepts .

Getting Started
To Contents | To previous page | To next page