source: rtems-docs/user/start/prefixes.rst

Last change on this file was bbb8b7a, checked in by Sebastian Huber <sebastian.huber@…>, on 05/19/23 at 05:34:36

Update company name

The embedded brains GmbH & Co. KG is the legal successor of embedded
brains GmbH.

  • Property mode set to 100644
File size: 2.9 KB
Line 
1.. SPDX-License-Identifier: CC-BY-SA-4.0
2
3.. Copyright (C) 2019 embedded brains GmbH & Co. KG
4.. Copyright (C) 2019 Sebastian Huber
5.. Copyright (C) 2016 Chris Johns <chrisj@rtems.org>
6
7.. _QuickStartPrefixes:
8
9Choose an Installation Prefix
10=============================
11
12.. index:: prefix
13
14You will see the term :ref:term:`prefix` referred to throughout this
15documentation and in a wide number of software packages you can download from
16the internet.  It is also used in the
17`GNU Coding Standard <https://www.gnu.org/prep/standards/html_node/Directory-Variables.html>`_.
18A *prefix* is the path on your host computer a software package is installed
19under.  Packages that have a prefix will place all parts under the prefix
20path.  Packages for your host computer typically use a default prefix of
21:file:`/usr/local` on FreeBSD and Linux.
22
23You have to select a prefix for your installation. You will build and install
24the RTEMS tool suite, an RTEMS kernel for a BSP, and you may build and install
25third party libraries. You can build all the parts as a stack with a single
26prefix or you can separate various parts by providing different prefixes to
27each part as it is built. Using separate prefixes is for experienced RTEMS
28users.
29
30Do not select a prefix that is under the top of any of the source trees. The
31prefix collects the install output of the various build steps you take in this
32guide and need to be kept separate from the sources used.
33
34The RTEMS tool suite consists of a cross tool chain (Binutils, GCC, GDB,
35Newlib, etc.)  for your target architecture and :ref:`RTEMS tools <HostTools>`
36provided by the RTEMS Project. The RTEMS Tools are a toolkit that help create
37the RTEMS ecosystem and help support the building of embedded real-time
38applications and systems.
39
40You build and install the tool suite with the :ref:`RTEMS Source Builder (RSB)
41<RSB>`.  By default, the RSB will start the prefix path with a host operating
42system specific path plus :file:`rtems`, and the RTEMS version, e.g.
43:file:`/opt/rtems/6` on Linux, and :file:`/usr/local/rtems/6` on FreeBSD and
44macOS. Placing the RTEMS version number in the path lets you manage and
45migrate RTEMS versions as they are released.
46
47It is strongly recommended to run the RSB as a *normal user* and not with
48*root* privileges (also known as *super user* or *Administrator*).  You have to
49make sure that your normal user has sufficient privileges to create files and
50directories under the prefix.  For example, you can create a directory
51:file:`/opt/rtems` and give it to a developer group with read, write, and
52execute permissions.  Alternatively, you can choose a prefix in your home
53directory, e.g. :file:`$HOME/rtems/6` or with a project-specific component
54:file:`$HOME/project-x/rtems/6`.  For more ideas, see the :ref:`project
55sandboxing <ProjectSandboxing>` section.  In this quick start chapter, we will
56choose :file:`$HOME/quick-start/rtems/6` for the RTEMS tool suite prefix.
57
58.. warning::
59
60    The prefix must not contain space characters.
Note: See TracBrowser for help on using the repository browser.