| 1 |
1026 |
ivang |
@c
|
| 2 |
|
|
@c COPYRIGHT (c) 1988-2002.
|
| 3 |
|
|
@c On-Line Applications Research Corporation (OAR).
|
| 4 |
|
|
@c All rights reserved.
|
| 5 |
|
|
@c
|
| 6 |
|
|
@c intro.texi,v 1.5 2002/01/17 21:47:44 joel Exp
|
| 7 |
|
|
@c
|
| 8 |
|
|
|
| 9 |
|
|
@ifinfo
|
| 10 |
|
|
@node Introduction, Directory Structure, Top, Top
|
| 11 |
|
|
@end ifinfo
|
| 12 |
|
|
@chapter Introduction
|
| 13 |
|
|
|
| 14 |
|
|
This document describes the RTEMS development
|
| 15 |
|
|
environment. Discussions are provided for the following topics:
|
| 16 |
|
|
|
| 17 |
|
|
@itemize @bullet
|
| 18 |
|
|
@item the directory structure used by RTEMS,
|
| 19 |
|
|
|
| 20 |
|
|
@item usage of the GNU Make utility within the RTEMS
|
| 21 |
|
|
development environment,
|
| 22 |
|
|
|
| 23 |
|
|
@item sample applications, and
|
| 24 |
|
|
|
| 25 |
|
|
@item the RTEMS specific utilities.
|
| 26 |
|
|
@end itemize
|
| 27 |
|
|
|
| 28 |
|
|
RTEMS was designed as a reusable software component.
|
| 29 |
|
|
Highly reusable software such as RTEMS is typically distributed
|
| 30 |
|
|
in the form of source code without providing any support tools.
|
| 31 |
|
|
RTEMS is the foundation for a complex family of facilities
|
| 32 |
|
|
including board support packages, device drivers, and support
|
| 33 |
|
|
libraries. The RTEMS Development Environment is not a CASE
|
| 34 |
|
|
tool. It is a collection of tools designed to reduce the
|
| 35 |
|
|
complexity of using and enhancing the RTEMS family. Tools are
|
| 36 |
|
|
provided which aid in the management of the development,
|
| 37 |
|
|
maintenance, and usage of RTEMS, its run-time support
|
| 38 |
|
|
facilities, and applications which utilize the executive.
|
| 39 |
|
|
|
| 40 |
|
|
A key component of the RTEMS development environment
|
| 41 |
|
|
is the GNU family of free tools. This is robust set of
|
| 42 |
|
|
development and POSIX compatible tools for which source code is
|
| 43 |
|
|
freely available. The primary compilers, assemblers, linkers,
|
| 44 |
|
|
and make utility used by the RTEMS development team are the GNU
|
| 45 |
|
|
tools. They are highly portable supporting a wide variety of
|
| 46 |
|
|
host computers and, in the case of the development tools, a wide
|
| 47 |
|
|
variety of target processors.
|
| 48 |
|
|
|
| 49 |
|
|
It is recommended that the RTEMS developer become
|
| 50 |
|
|
familiar with the RTEMS Development Environment before
|
| 51 |
|
|
proceeding with any modifications to the executive source tree.
|
| 52 |
|
|
The source code for the executive is very modular and source
|
| 53 |
|
|
code is divided amongst directories based upon functionality as
|
| 54 |
|
|
well as dependencies on CPU and target board. This organization
|
| 55 |
|
|
is aimed at isolating and minimizing non-portable code. This
|
| 56 |
|
|
has the immediate result that adding support for a new CPU or
|
| 57 |
|
|
target board requires very little "wandering" around the source
|
| 58 |
|
|
tree.
|
