diff options
Diffstat (limited to 'user/rsb')
| -rw-r--r-- | user/rsb/bug-reporting.rst | 8 | ||||
| -rw-r--r-- | user/rsb/commands.rst | 8 | ||||
| -rw-r--r-- | user/rsb/configuration.rst | 8 | ||||
| -rw-r--r-- | user/rsb/cross-canadian-cross.rst | 6 | ||||
| -rw-r--r-- | user/rsb/deployment.rst | 8 | ||||
| -rw-r--r-- | user/rsb/project-sets.rst | 8 | ||||
| -rw-r--r-- | user/rsb/third-party-packages.rst | 2 |
7 files changed, 25 insertions, 23 deletions
diff --git a/user/rsb/bug-reporting.rst b/user/rsb/bug-reporting.rst index 2adf90a..304da17 100644 --- a/user/rsb/bug-reporting.rst +++ b/user/rsb/bug-reporting.rst @@ -13,10 +13,12 @@ find a bug please report it via the :r:url:`devel` or email on the RTEMS Users list. Please include the generated RSB report. If you see the following a report has -been generated:: +been generated: - ... - ... +.. code-block:: none + + ... + ... Build FAILED <1> See error report: rsb-report-4.11-rtems-lm32.txt <2> diff --git a/user/rsb/commands.rst b/user/rsb/commands.rst index 80d74a5..b85692d 100644 --- a/user/rsb/commands.rst +++ b/user/rsb/commands.rst @@ -10,7 +10,7 @@ Checker (sb-check) This commands checks your system is set up correctly. Most options are ignored: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-check --help sb-check: [options] [args] @@ -54,7 +54,7 @@ Defaults (sb-defaults) This commands outputs and the default macros for your when given no arguments. Most options are ignored: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-defaults --help sb-defaults: [options] [args] @@ -94,7 +94,7 @@ Set Builder (sb-set-builder) This command builds a set: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --help RTEMS Source Builder, an RTEMS Tools Project (c) 2012-2013 Chris Johns @@ -302,7 +302,7 @@ Set Builder (sb-builder) This command builds a configuration as described in a configuration file. Configuration files have the extension of ``.cfg``: -.. code-block:: shell +.. code-block:: none $ ./source-builder/sb-builder --help sb-builder: [options] [args] diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst index 85e3626..e9a6ad4 100644 --- a/user/rsb/configuration.rst +++ b/user/rsb/configuration.rst @@ -238,7 +238,7 @@ with: The ``sb-defaults`` command lists the defaults for your host. I will not include the output of this command because of its size: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-defaults @@ -518,7 +518,7 @@ provides. To create a private configuration change to a suitable directory: -.. code-block:: shell +.. code-block:: none $ cd ~/work $ mkdir test @@ -749,7 +749,7 @@ Once we have the configuration files we can execute the build using the ``sb-builder`` command. The command will perform the build and create a tar file in the ``tar`` directory: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-builder --prefix=/usr/local \ --log=log_dtc devel/dtc-1.2.0 @@ -782,7 +782,7 @@ The DTC build set file is called ``dtc.bset`` and contains: To build this you can use something similar to: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --prefix=/usr/local --log=log_dtc \ --trace --bset-tar-file --no-install dtc diff --git a/user/rsb/cross-canadian-cross.rst b/user/rsb/cross-canadian-cross.rst index fc903e4..d78952f 100644 --- a/user/rsb/cross-canadian-cross.rst +++ b/user/rsb/cross-canadian-cross.rst @@ -22,7 +22,7 @@ development machine. To build the NTP package for RTEMS you enter the RSB command: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder \ --log=log_ntp_arm.txt \ @@ -85,7 +85,7 @@ To perform a cross build add ``--host=`` to the command line. For example to build a MinGW tool set on FreeBSD for Windows add ``--host=mingw32`` if the cross compiler is ``mingw32-gcc``: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --host=mingw32 \ --log=l-mingw32-4.11-sparc.txt \ @@ -95,7 +95,7 @@ if the cross compiler is ``mingw32-gcc``: If you are on a Linux Fedora build host with the MinGW packages installed the command line is: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --host=i686-w64-mingw32 \ --log=l-mingw32-4.11-sparc.txt \ diff --git a/user/rsb/deployment.rst b/user/rsb/deployment.rst index c0cd1ce..ad5dd57 100644 --- a/user/rsb/deployment.rst +++ b/user/rsb/deployment.rst @@ -32,7 +32,7 @@ directory to the root (``/``) and untar the file because the ``/home`` is root access only. To install a tar file you have downloaded into your new machine's ``Downloads`` directory in your home directoty you would enter: -.. code-block:: shell +.. code-block:: none $ cd /somewhere $ tar --strip-components=3 -xjf \ @@ -41,7 +41,7 @@ access only. To install a tar file you have downloaded into your new machine's A build set tar file is created by adding ``--bset-tar-file`` option to the ``sb-set-builder`` command: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --log=l-sparc.txt \ --prefix=$HOME/development/rtems/4.11 \ @@ -84,7 +84,7 @@ You can also suppress installing the files using the ``--no-install`` option. This is useful if your prefix is not accessiable, for example when building Canadian cross compiled tool sets: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --log=l-sparc.txt \ --prefix=$HOME/development/rtems/4.11 \ @@ -124,7 +124,7 @@ A package tar file can be created by adding the ``--pkg-tar-files`` to the ``sb-set-builder`` command. This creates a tar file per package built in the build set: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --log=l-sparc.txt \ --prefix=$HOME/development/rtems/4.11 \ diff --git a/user/rsb/project-sets.rst b/user/rsb/project-sets.rst index 64a23d4..5ffce26 100644 --- a/user/rsb/project-sets.rst +++ b/user/rsb/project-sets.rst @@ -50,7 +50,7 @@ The **bare metal** support for GNU Tool chains. An example is the for an ARM compiler you would use ``arm-eabi`` or ``arm-eabihf``, and for SPARC you would use ``sparc-elf``: -.. code-block:: shell +.. code-block:: none $ cd rtems-source-builder/bare $ ../source-builder/sb-set-builder --log=log_arm_eabihf \ @@ -109,7 +109,7 @@ packages only after they have been built so if you host does not have a recent enough version of ``autoconf`` and ``automake`` you first need to build them and install them then build your tool set. The commands are: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --log=l-4.11-at.txt \ --prefix=$HOME/development/rtems/4.11 4.11/rtems-autotools @@ -131,7 +131,7 @@ passing them on the command line using the ``--macros`` option. For RTEMS these are held in ``config/snapshots`` directory. The following builds *newlib* from CVS: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --log=l-4.11-sparc.txt \ --prefix=$HOME/development/rtems/4.11 \ @@ -141,7 +141,7 @@ CVS: and the following uses the version control heads for ``binutils``, ``gcc``, ``newlib``, ``gdb`` and *RTEMS*: -.. code-block:: shell +.. code-block:: none $ ../source-builder/sb-set-builder --log=l-heads-sparc.txt \ --prefix=$HOME/development/rtems/4.11-head \ diff --git a/user/rsb/third-party-packages.rst b/user/rsb/third-party-packages.rst index c02153b..b8ca15a 100644 --- a/user/rsb/third-party-packages.rst +++ b/user/rsb/third-party-packages.rst @@ -39,7 +39,7 @@ needs to be the same as the prefix used to build RTEMS. To build Net-SNMP the command is: -.. code-block:: shell +.. code-block:: none $ cd rtems-source-builder/rtems $ ../source-builder/sb-set-builder --log=log_sis_net_snmp \ |