source: rtems-docs/user/start/prefixes.rst @ 947e8eb

5
Last change on this file since 947e8eb was eae5454, checked in by Sebastian Huber <sebastian.huber@…>, on 01/11/19 at 14:47:00

user: Rework Prefixes section

Rename it to "Choose an Installation Prefix".

Update #3675.

  • Property mode set to 100644
File size: 2.2 KB
Line 
1.. SPDX-License-Identifier: CC-BY-SA-4.0
2
3.. Copyright (C) 2019 embedded brains GmbH
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 RTEMS tool suite installation.  The RTEMS
24tool suite consists of a cross tool chain (Binutils, GCC, GDB, Newlib, etc.)
25for your target architecture and :ref:`other tools <HostTools>` provided by the
26RTEMS Project.  You build and install the tool suite with the
27:ref:`RTEMS Source Builder (RSB) <RSB>`.  By default, the RSB will start the
28prefix path with a host operating system specific path plus :file:`rtems` plus
29the RTEMS version, e.g.  :file:`/opt/rtems/5` on Linux and
30:file:`/usr/local/rtems/5` on FreeBSD and macOS.
31
32It is strongly recommended to run the RSB as a *normal user* and not with
33*root* privileges (also known as *super user* or *Administrator*).  You have to
34make sure that your normal user has sufficient privileges to create files and
35directories under the prefix.  For example, you can create a directory
36:file:`/opt/rtems` and give it to a developer group with read, write and
37execute permissions.  Alternatively, you can choose a prefix in your home
38directory, e.g. :file:`$HOME/rtems/5` or with a project-specific component
39:file:`$HOME/project-x/rtems/5`.  For more ideas, see the
40:ref:`project sandboxing <ProjectSandboxing>` section.  In this quick start
41chapter, we will choose :file:`$HOME/quick-start/rtems/5` for the RTEMS tool
42suite prefix.
43
44.. warning::
45
46    The prefix must not contain space characters.
Note: See TracBrowser for help on using the repository browser.