Changeset 2674d6a in rtems-docs for user/rsb/project-sets.rst


Ignore:
Timestamp:
Feb 21, 2019, 2:06:58 AM (12 months ago)
Author:
Chris Johns <chrisj@…>
Branches:
master
Children:
921037f
Parents:
2e6f49f
git-author:
Chris Johns <chrisj@…> (02/21/19 02:06:58)
git-committer:
Chris Johns <chrisj@…> (02/27/19 23:22:54)
Message:

user: Remove nit-picky warnings.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • user/rsb/project-sets.rst

    r2e6f49f r2674d6a  
    44
    55Project Sets
    6 ============
     6------------
    77
    88The RTEMS Source Builder supports project configurations. Project
     
    3737
    3838Bare Metal
    39 ----------
     39^^^^^^^^^^
    4040
    4141The RSB contains a 'bare' configuration tree and you can use this to add
     
    4848``lang/gcc491`` build set. You need to provide a target via the command line
    4949``--target`` option and this is in the standard 2 or 3 tuple form. For example
    50 for an ARM compiler you would use ``arm-eabi`` or ``arm-eabihf`, and for SPARC
    51 you would use `sparc-elf`::
     50for an ARM compiler you would use ``arm-eabi`` or ``arm-eabihf``, and for SPARC
     51you would use ``sparc-elf``:
     52
     53.. code-block:: shell
    5254
    5355    $ cd rtems-source-builder/bare
     
    7880
    7981RTEMS
    80 -----
     82^^^^^
    8183
    8284The RTEMS Configurations found in the ``rtems`` directory. The configurations
     
    106108packages only after they have been built so if you host does not have a
    107109recent enough version of ``autoconf`` and ``automake`` you first need to build them
    108 and install them then build your tool set. The commands are::
     110and install them then build your tool set. The commands are:
     111
     112.. code-block:: shell
    109113
    110114    $ ../source-builder/sb-set-builder --log=l-4.11-at.txt \
     
    126130passing them on the command line using the ``--macros`` option. For RTEMS these
    127131are held in ``config/snapshots`` directory. The following builds *newlib* from
    128 CVS::
     132CVS:
     133
     134.. code-block:: shell
    129135
    130136    $ ../source-builder/sb-set-builder --log=l-4.11-sparc.txt \
     
    134140
    135141and the following uses the version control heads for ``binutils``, ``gcc``,
    136 ``newlib``, ``gdb`` and *RTEMS*::
     142``newlib``, ``gdb`` and *RTEMS*:
     143
     144.. code-block:: shell
    137145
    138146    $ ../source-builder/sb-set-builder --log=l-heads-sparc.txt \
     
    160168
    161169Patches
    162 -------
     170^^^^^^^
    163171
    164172Packages being built by the RSB need patches from time to time and the RSB
     
    200208Patches can be declared in build set up files.
    201209
    202 This examples shows how to declare a patch for gdb in the ``lm32`` architecture::
     210This examples shows how to declare a patch for gdb in the ``lm32`` architecture:
     211
     212.. code-block:: spec
    203213
    204214    %patch add <1> gdb <2> %{rtems_gdb_patches}/lm32/gdb-sim-lm32uart.diff <3>
     
    213223
    214224Patches require a checksum to avoid a warning. The ``%hash`` directive can be
    215 used to add a checksum for a patch that is used to verify the patch::
     225used to add a checksum for a patch that is used to verify the patch:
     226
     227.. code-block:: spec
    216228
    217229    %hash md5 <1> gdb-sim-lm32uart.diff <2> 77d070878112783292461bd6e7db17fb <3>
     
    227239The patches are applied when a patch ``setup`` command is issued in the
    228240``%prep:`` section. All patches in the group are applied. To apply the GDB
    229 patch above use::
     241patch above use:
     242
     243.. code-block:: spec
    230244
    231245    %patch setup <1> gdb <2> -p1 <3>
     
    252266``rtems/config/tools/`` that is included by the bset you use:
    253267
    254 .. code-block:: auto
     268.. code-block:: spec
    255269
    256270    %patch add newlib file://0001-this-is-a-newlib-patch.patch   <1>
Note: See TracChangeset for help on using the changeset viewer.