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