Changeset 0facb9d in rtems-docs
- Timestamp:
- 01/11/19 14:28:57 (5 years ago)
- Branches:
- 5, master
- Children:
- 3ed59ce
- Parents:
- 3de74ba
- git-author:
- Sebastian Huber <sebastian.huber@…> (01/11/19 14:28:57)
- git-committer:
- Sebastian Huber <sebastian.huber@…> (01/14/19 06:15:27)
- Location:
- user
- Files:
-
- 1 added
- 2 edited
- 1 moved
Legend:
- Unmodified
- Added
- Removed
-
user/installation/index.rst
r3de74ba r0facb9d 46 46 .. toctree:: 47 47 48 prefixes-sandboxing49 48 releases 50 49 developer 51 50 kernel 51 project-sandboxing -
user/installation/project-sandboxing.rst
r3de74ba r0facb9d 5 5 .. index:: Prefixes 6 6 .. _prefixes: 7 8 Prefixes9 ========10 11 You will see the term :ref:term:`prefix` referred to thoughout this12 documentation and in a wide number of software packages you can download from13 the internet. A **prefix** is the path on your computer a software package is14 built and installed under. Packages that have a **prefix** will place all parts15 under the **prefix** path. On a host computer like Linux the packages you16 install from your distribution typically use a platform specific standard17 **prefix**. For example on Linux it is :file:`/usr` and on FreeBSD it is18 :file:`/usr/local`.19 20 We recommend you *DO NOT* use the standard **prefix** when installing the RTEMS21 Tools. The standard **prefix** is the default **prefix** each package built by22 the RSB contains. If you are building the tools when logged in as a *Standard23 User* and not as the *Super User* (``root``) or *Administrator* the RTEMS24 Source Builder (RSB) *will* fail and report an error if the default **prefix**25 is not writable. We recommend you leave the standand **prefix** for the26 packages your operating system installs or software you manually install such27 as applications.28 29 A further reason not to use the standard **prefix** is to allow more than one30 version of RTEMS to exist on your host machine at a time. The ``autoconf`` and31 ``automake`` tools required by RTEMS are not versioned and vary between the32 various versions of RTEMS. If you use a single **prefix** such as the standard33 **prefix** there is a chance parts from a package of different versions may34 interact. This should not happen but it can.35 36 For POSIX or Unix hosts, the RTEMS Project uses :file:`/opt/rtems` as it's37 standard **prefix**. We view this **prefix** as a production level path, and we38 prefer to place development versions under a different **prefix** away from the39 production versions. Under this top level **prefix** we place the various40 versions we need for development. For example the version 4.11.0 **prefix**41 would be :file:`/opt/rtems/4.11.0`. If an update called 4.11.1 is released the42 **prefix** would be :file:`/opt/rtems/4.11.1`. These are recommendations and43 the choice of what you use is entirely yours. You may decide to have a single44 path for all RTEMS 4.11 releases of :file:`/opt/rtems/4.11`.45 46 For Windows a typical **prefix** is :file:`C:\\opt\\rtems` and as an MSYS2 path47 this is :file:`/c/opt/rtems`.48 7 49 8 .. _project-sandboxing: -
user/start/index.rst
r3de74ba r0facb9d 9 9 Quick Start 10 10 *********** 11 12 Follow the sections of this chapter step by step to get started developing 13 applications on top of RTEMS. 14 15 .. toctree:: 16 :maxdepth: 5 17 :numbered: 18 19 prefixes 11 20 12 21 The following is a quick start guide that provides a basic set of commands to
Note: See TracChangeset
for help on using the changeset viewer.