source: rtems-docs/develenv/introduction.rst @ c0d6eff6

4.115am
Last change on this file since c0d6eff6 was c0d6eff6, checked in by Amar Takhar <verm@…>, on 01/16/16 at 19:53:40

Split document.

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