source: rtems/doc/develenv/intro.texi @ 6449498
Last change on this file since 6449498 was 6449498, checked in by Joel Sherrill <joel.sherrill@…>, on Jan 17, 2002 at 9:47:47 PM

2001-01-17 Joel Sherrill <joel@…>

  • SUPPORT, LICENSE: New files.
  • Numerous files touched as part of merging the 4.5 branch onto the mainline development trunk and ensuring that the script that cuts snapshots and releases works on the documentation.
  • Property mode set to 100644
File size: 2.2 KB
2@c  COPYRIGHT (c) 1988-2002.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
6@c  $Id$
10@node Introduction, Directory Structure, Top, Top
11@end ifinfo
12@chapter Introduction
14This document describes the RTEMS development
15environment.  Discussions are provided for the following topics:
17@itemize @bullet
18@item the directory structure used by RTEMS,
20@item usage of the GNU Make utility within the RTEMS
21development environment,
23@item sample applications, and
25@item the RTEMS specific utilities.
26@end itemize
28RTEMS was designed as a reusable software component.
29Highly reusable software such as RTEMS is typically distributed
30in the form of source code without providing any support tools.
31RTEMS is the foundation for a complex family of facilities
32including board support packages, device drivers, and support
33libraries.  The RTEMS Development Environment is not a CASE
34tool.  It is a collection of tools designed to reduce the
35complexity of using and enhancing the RTEMS family.  Tools are
36provided which aid in the management of the development,
37maintenance, and usage of RTEMS, its run-time support
38facilities, and applications which utilize the executive.
40A key component of the RTEMS development environment
41is the GNU family of free tools.  This is  robust set of
42development and POSIX compatible tools for which source code is
43freely available.  The primary compilers, assemblers, linkers,
44and make utility used by the RTEMS development team are the GNU
45tools.  They are highly portable supporting a wide variety of
46host computers and, in the case of the development tools, a wide
47variety of target processors.
49It is recommended that the RTEMS developer become
50familiar with the RTEMS Development Environment before
51proceeding with any modifications to the executive source tree.
52The source code for the executive is very modular and source
53code is divided amongst directories based upon functionality as
54well as dependencies on CPU and target board.  This organization
55is aimed at isolating and minimizing non-portable code.  This
56has the immediate result that adding support for a new CPU or
57target board requires very little "wandering" around the source
Note: See TracBrowser for help on using the repository browser.