source: rtems-docs/develenv/introduction.rst @ 735de5f

Last change on this file since 735de5f was 735de5f, checked in by Amar Takhar <amar@…>, on 01/17/16 at 00:10:06

Move preface/intro one level up so the section is unnumbered.

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