source: rtems-docs/develenv/introduction.rst @ 9aafb39

4.115
Last change on this file since 9aafb39 was 9b53679, checked in by Chris Johns <chrisj@…>, on 10/27/16 at 23:12:50

Fix develenv. Needs more fixes.

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