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