source: rtems-docs/user/ecosys/index.rst @ aa1c010

4.115
Last change on this file since aa1c010 was aa1c010, checked in by Chris Johns <chrisj@…>, on 11/09/16 at 01:20:46

user: Fix header levels.

  • Property mode set to 100644
File size: 4.0 KB
Line 
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.. _ecosystem:
7
8RTEMS Ecosystem
9***************
10.. index:: Ecosystem
11
12The RTEMS Ecosystem is the collection of tools, packages, code, documentation
13and online content provided by the RTEMS Project. The ecosystem provides a way
14to develop, maintain, and use RTEMS. It's parts interact with the user, the
15host environment, and each other to make RTEMS accessable, useable and
16predicable.
17
18The ecosystem is for users, developers and maintainers and it is an on going
19effort that needs your help and support. The RTEMS project is always improving
20the way it delivers the kernel to you and your feedback is important so please
21join the mailing lists and contribute back comments, success stories, bugs and
22patches.
23
24What the RTEMS project describes here to develop, maintain and use RTEMS does
25not dictate what you need to use in your project. You can and should select the
26work-flow that best suites the demands of your project and what you are
27delivering.
28
29Rational
30========
31
32RTEMS is complex and the focus of the RTEMS Ecosystem is to simplify the
33complexity for users by providing a stable documented way to build, configure
34and run RTEMS. RTEMS is more than a kernel running real-time applications on
35target hardware, it is part of a project's and therefore team's workflow and
36every project and team is different.
37
38RTEMS's ecosystem does not mandate a way to work. It is a series of parts,
39components, and items that are used to create a suitable development
40environment to work with. The processes explained in this manual are the same
41things an RTEMS maintainer does to maintain the kernel or an experienced user
42does to build their production system. It is important to keep this in mind
43when working through this manual. We encourage users to explore what can be
44done and to discover ways to make it fit their needs. The ecosystem provided by
45the RTEMS Project will not install in a single click of a mouse because we want
46users to learn the parts they will come to depend on as their project's
47development matures.
48
49The RTEMS Ecosystem provides a standard interface that is the same on all
50supported host systems. Standardizing how a user interacts with RTEMS is
51important and making that experience portable is also important. As a result
52the ecosystem is documented at the command line level and we leave GUI and IDE
53integration for users and integrators.
54
55Standardizing the parts and how to use them lets users create processes and
56procedures that are stable over releases. The RTEMS Ecosystem generates data
57that can be used to audit the build process so their configuration can be
58documented.
59
60The ecosystem is based around the source code used in the various parts,
61compontents and items of the RTEMS development environment. A user can create
62an archive of the complete build process including all the source code for long
63term storage. This is important for projects with a long life cycle.
64
65Open Source
66===========
67
68RTEMS is an open source operating system and an open source project and this
69extends to the ecosystem. We encourage users to integrate the processes to
70build tools, the kernel and any 3rd party libraries into their project's
71configuration management processes.
72
73All the parts that make up the ecosystem are open source. The ecosystem uses a
74package's source code to create an executable on a host so when an example
75RTEMS executable is created and run for the first time the user will have built
76every tool as well as the executable from source. The RTEMS Project believes
77the freedom this gives a user is as important as the freedom of having access
78to the source code for a package.
79
80Deployment
81==========
82
83The RTEMS Project provides the ecosystem as source code that users can download
84to create personalised development environments. The RTEMS Project does not
85provide packaging and deployment for a specific host environment, target
86architecture or BSP. The RTEMS Project encourages users and organizations to
87fill this role for the community.
Note: See TracBrowser for help on using the repository browser.