Changeset eae5454 in rtems-docs
- Timestamp:
- 01/11/19 14:47:00 (5 years ago)
- Branches:
- 5, master
- Children:
- 947e8eb
- Parents:
- 2445655
- git-author:
- Sebastian Huber <sebastian.huber@…> (01/11/19 14:47:00)
- git-committer:
- Sebastian Huber <sebastian.huber@…> (02/18/19 12:50:31)
- Location:
- user
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
user/hosts/posix.rst
r2445655 reae5454 36 36 have restricted access rights to only those who manage and have configuration 37 37 control of the machine. We call this project sandboxing and 38 :ref:` project-sandboxing` explains this in more detail.38 :ref:`ProjectSandboxing` explains this in more detail. 39 39 40 40 Linux -
user/installation/project-sandboxing.rst
r2445655 reae5454 3 3 .. Copyright (C) 2016 Chris Johns <chrisj@rtems.org> 4 4 5 .. _ project-sandboxing:5 .. _ProjectSandboxing: 6 6 7 7 Project Sandboxing -
user/start/index.rst
r2445655 reae5454 58 58 doing this. You can build and install the tools anywhere on the host's 59 59 file system you, as a standard user, have read and write access too. 60 :ref:`Prefixes` and :ref:` project-sandboxing` provide detailed examples60 :ref:`Prefixes` and :ref:`ProjectSandboxing` provide detailed examples 61 61 of possible locations and set ups. 62 62 -
user/start/prefixes.rst
r2445655 reae5454 1 1 .. SPDX-License-Identifier: CC-BY-SA-4.0 2 2 3 .. Copyright (C) 2019 embedded brains GmbH 4 .. Copyright (C) 2019 Sebastian Huber 3 5 .. Copyright (C) 2016 Chris Johns <chrisj@rtems.org> 4 6 5 7 .. _QuickStartPrefixes: 6 8 7 Prefixes 8 ======== 9 Choose an Installation Prefix 10 ============================= 9 11 10 12 .. index:: prefix 11 13 12 You will see the term :ref:term:`prefix` referred to th oughout this14 You will see the term :ref:term:`prefix` referred to throughout this 13 15 documentation and in a wide number of software packages you can download from 14 the internet. A **prefix** is the path on your computer a software package is15 built and installed under. Packages that have a **prefix** will place all parts 16 under the **prefix** path. On a host computer like Linux the packages you 17 install from your distribution typically use a platform specific standard 18 **prefix**. For example on Linux it is :file:`/usr` and on FreeBSD it is 19 :file:`/usr/local` .16 the internet. It is also used in the 17 `GNU Coding Standard <https://www.gnu.org/prep/standards/html_node/Directory-Variables.html>`_. 18 A *prefix* is the path on your host computer a software package is installed 19 under. Packages that have a prefix will place all parts under the prefix 20 path. Packages for your host computer typically use a default prefix of 21 :file:`/usr/local` on FreeBSD and Linux. 20 22 21 We recommend you *DO NOT* use the standard **prefix** when installing the RTEMS22 Tools. The standard **prefix** is the default **prefix** each package built by 23 the RSB contains. If you are building the tools when logged in as a *Standard 24 User* and not as the *Super User* (``root``) or *Administrator* the RTEMS 25 Source Builder (RSB) *will* fail and report an error if the default **prefix** 26 is not writable. We recommend you leave the standand **prefix** for the 27 packages your operating system installs or software you manually install such 28 as applications.23 You have to select a prefix for your RTEMS tool suite installation. The RTEMS 24 tool suite consists of a cross tool chain (Binutils, GCC, GDB, Newlib, etc.) 25 for your target architecture and :ref:`other tools <HostTools>` provided by the 26 RTEMS Project. You build and install the tool suite with the 27 :ref:`RTEMS Source Builder (RSB) <RSB>`. By default, the RSB will start the 28 prefix path with a host operating system specific path plus :file:`rtems` plus 29 the RTEMS version, e.g. :file:`/opt/rtems/5` on Linux and 30 :file:`/usr/local/rtems/5` on FreeBSD and macOS. 29 31 30 A further reason not to use the standard **prefix** is to allow more than one 31 version of RTEMS to exist on your host machine at a time. The ``autoconf`` and 32 ``automake`` tools required by RTEMS are not versioned and vary between the 33 various versions of RTEMS. If you use a single **prefix** such as the standard 34 **prefix** there is a chance parts from a package of different versions may 35 interact. This should not happen but it can. 32 It 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 34 make sure that your normal user has sufficient privileges to create files and 35 directories 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 37 execute permissions. Alternatively, you can choose a prefix in your home 38 directory, 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 41 chapter, we will choose :file:`$HOME/quick-start/rtems/5` for the RTEMS tool 42 suite prefix. 36 43 37 For POSIX or Unix hosts, the RTEMS Project uses :file:`/opt/rtems` as it's 38 standard **prefix**. We view this **prefix** as a production level path, and we 39 prefer to place development versions under a different **prefix** away from the 40 production versions. Under this top level **prefix** we place the various 41 versions we need for development. For example the version 4.11.0 **prefix** 42 would be :file:`/opt/rtems/4.11.0`. If an update called 4.11.1 is released the 43 **prefix** would be :file:`/opt/rtems/4.11.1`. These are recommendations and 44 the choice of what you use is entirely yours. You may decide to have a single 45 path for all RTEMS 4.11 releases of :file:`/opt/rtems/4.11`. 44 .. warning:: 46 45 47 For Windows a typical **prefix** is :file:`C:\\opt\\rtems` and as an MSYS2 path 48 this is :file:`/c/opt/rtems`. 46 The prefix must not contain space characters. -
user/tools/index.rst
r2445655 reae5454 2 2 3 3 .. Copyright (C) 2017 Chris Johns <chrisj@rtems.org> 4 5 .. _HostTools: 4 6 5 7 Host Tools
Note: See TracChangeset
for help on using the changeset viewer.