diff options
Diffstat (limited to 'user/start/preparation.rst')
| -rw-r--r-- | user/start/preparation.rst | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/user/start/preparation.rst b/user/start/preparation.rst index eb0d56b..4bfc214 100644 --- a/user/start/preparation.rst +++ b/user/start/preparation.rst @@ -1,7 +1,7 @@ .. SPDX-License-Identifier: CC-BY-SA-4.0 .. Copyright (C) 2018 Shashvat Jain -.. Copyright (C) 2019 embedded brains GmbH +.. Copyright (C) 2019 embedded brains GmbH & Co. KG .. Copyright (C) 2019 Sebastian Huber .. Copyright (C) 2020 Chris Johns .. Copyright (C) 2020 Gedare Bloom @@ -45,9 +45,11 @@ your tools, editors, documentation viewers, etc. You need a native C, C++, and Python development environment. Please make sure you can build native C/C++ applications on your host computer. You must be able to build native Python C modules as some RTEMS tools contain these modules. Usually, you have to -install a Python development package for this. Please have a look at the -:ref:`Host Computer <host-computer>` chapter for the gory details. In -particular :ref:`Microsoft Windows <microsoft-windows>` users should do this. +install a Python development package for this. The Python scripts of the RTEMS +Project expect on POSIX systems that a ``python`` command is available [1]_. +Please have a look at the :ref:`Host Computer <host-computer>` chapter for the +gory details. In particular :ref:`Microsoft Windows <microsoft-windows>` users +should do this. Selecting a BSP --------------- @@ -65,6 +67,8 @@ BSP. The BeagleBone Black support includes the RTEMS BSD Library (``libbsd``) and networking. The BeagleBone Black BSP is an ARM architecture BSP so the tool suite name is ``arm-rtems5``. +.. _QuickStartPreparation_Version: + Selecting a Version of RTEMS ---------------------------- @@ -111,3 +115,5 @@ within a release branch, for example the tools packaged with 5.1.1 still use the ``sparc-rtems5`` moniker, but are likely not the same as the tools used in version 5.1.0. This tool mismatch can be a source of confusion. Be sure to use the toolchain that matches your release. + +.. [1] The Python scripts use a shebang of ``#!/usr/bin/env python``. |