Chapter 25. The Component Repository and Working Directories

Table of Contents
Component Repository
Build Tree
Install Tree
Application Build Tree

Each of the file trees involved in eCos development has a different role.

Component Repository

The eCos component repository contains directories for all the packages that are shipped with eCos or provided by third parties.

The component repository should not be modified as part of application development.

Figure 25-1. Component repository

Purpose

The component repository is the master copy of source code for all system and third party components. It also contains some files needed to administer and build the system, such as ecosadmin.tcl.

How is it modified?

You modify it by importing new versions of packages from a distribution or removing existing packages. These activities are undertaken using the eCos Package Administration Tool.

When is it edited manually?

Files in the component repository should only be edited manually as determined by the component maintainer.

User Applications

User application source code should not go into the component repository.

Examples of files in this hierarchy:

BASE_DIR/doc/ref/ecos-ref.html: The top level HTML file for the eCos Reference Manual.
BASE_DIR/prebuilt/pid/tests/kernel/<version>/tests/thread_gdb.exe
BASE_DIR/prebuilt/linux/tests/kernel/<version>/tests/thread_gdb.exe: Pre-built tests for the supported platforms, and the synthetic Linux target.
BASE_DIR/examples/twothreads.c: One of the example programs.
BASE_DIR/ecosadmin.tcl: The Tcl program which is used to import new versions of packages from a distribution or remove existing packages.
BASE_DIR/packages/language/c/libm/<version>/src/double/portable-api/s_tanh.c: Implementation of the hyperbolic tangent function in the standard math library.
BASE_DIR/pkgconf/rules.mak: A file with make rules, used by the makefile.