1 | .. comment SPDX-License-Identifier: CC-BY-SA-4.0 |
---|
2 | |
---|
3 | .. comment: Copyright (c) 2016 Chris Johns <chrisj@rtems.org> |
---|
4 | .. comment: All rights reserved. |
---|
5 | |
---|
6 | .. _installation: |
---|
7 | |
---|
8 | Installation |
---|
9 | ============ |
---|
10 | .. index:: Installation |
---|
11 | |
---|
12 | This section details how to set up and install the RTEMS Ecosystem. You will |
---|
13 | create a set of tools and an RTEMS kernel for your selected Board Support |
---|
14 | Package (BSP). |
---|
15 | |
---|
16 | You will be asked to follow a few simple steps and when you have finished you |
---|
17 | will have a development environment set up you can use to build applications |
---|
18 | for RTEMS. You will have also created a development environment you and a team |
---|
19 | can adapt for a project of any size and complexity. |
---|
20 | |
---|
21 | .. index:: Tools |
---|
22 | |
---|
23 | RTEMS applications are developed using cross-development tools running on a |
---|
24 | development computer, more commonlly referred to as the host computer. These |
---|
25 | are typically your desktop machine or a special build server. All RTEMS tools |
---|
26 | and runtime libraries are built from source on your host machine. The RTEMS |
---|
27 | Project does not maintain binary builds of the tools. This may appear to be the |
---|
28 | opposite to what you normally experience with host operating systems, and it |
---|
29 | is, however this approach works well. RTEMS is not a host operating system and |
---|
30 | it is not a distrbution. Providing binary packages for every possible host |
---|
31 | operating system is too big a task for the RTEMS Project and it is not a good |
---|
32 | use of core developer time. Their time is better spent making RTEMS better and |
---|
33 | faster. |
---|
34 | |
---|
35 | The RTEMS Project base installation set ups the tools and the RTEMS kernel for |
---|
36 | the selected BSPs. The tools run on your host computer are used to compile, |
---|
37 | link, and format executables so they can run on your target hardware. |
---|
38 | |
---|
39 | The RTEMS Project supports two set ups, release and developer |
---|
40 | environments. Release installations create the tools and kernel in a single |
---|
41 | pass ready for you to use. The tools and kernel are stable and only bug fixes |
---|
42 | are added creating new dot point releases. The developer set up tracks the Git |
---|
43 | repositories for the tools and kernel. |
---|
44 | |
---|
45 | .. include:: prefixes-sandboxing.rst |
---|
46 | .. include:: releases.rst |
---|
47 | .. include:: developer.rst |
---|