Changeset 633a24f in rtems-docs


Ignore:
Timestamp:
Jan 10, 2019, 11:52:23 AM (6 days ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
master
Children:
9e18bcb
Parents:
e52906b
git-author:
Sebastian Huber <sebastian.huber@…> (01/10/19 11:52:23)
git-committer:
Sebastian Huber <sebastian.huber@…> (01/11/19 06:22:58)
Message:

rsb: Move "History" to own chapter

Move it to the end of the document. It is auxiliary information.

Location:
rsb
Files:
1 added
2 edited

Legend:

Unmodified
Added
Removed
  • rsb/index.rst

    re52906b r633a24f  
    2525
    2626.. toctree::
    27         :maxdepth: 5
    28         :numbered:
     27    :maxdepth: 5
     28    :numbered:
    2929
    30         source-builder
    31         building-tools-and-rtems.rst
    32         project-sets
    33         cross-canadian-cross
    34         third-party-packages
    35         configuration
    36         commands
    37         bug-reporting
     30    source-builder
     31    building-tools-and-rtems.rst
     32    project-sets
     33    cross-canadian-cross
     34    third-party-packages
     35    configuration
     36    commands
     37    bug-reporting
     38    history
    3839
    3940* :ref:`genindex`
  • rsb/source-builder.rst

    re52906b r633a24f  
    134134computing environment.
    135135
    136 History
    137 -------
    138 
    139 The RTEMS Source Builder is a stand alone tool based on another tool called the
    140 *SpecBuilder* written by Chris Johns. The *SpecBuilder* was written around 2010
    141 for the RTEMS project to provide Chris with a way to build tools on hosts that
    142 did not support RPMs. At the time the RTEMS tools maintainer only supported
    143 *spec* files and these files held all the vital configuration data needed to
    144 create suitable tool sets. The available SRPM and *spec* files by themselves
    145 where of little use because a suitable ``rpm`` tool was needed to use them. At
    146 the time the available versions of ``rpm`` for a number of non-RPM hosts were
    147 broken and randomly maintained. The solution Chris settled on was to use the
    148 *spec* files and to write a Python based tool that parsed the *spec* file
    149 format creating a shell script that could be run to build the package. The
    150 approach proved successful and Chris was able to track the RPM version of the
    151 RTEMS tools on a non-RPM host for a number of years.
    152 
    153 The *SpecBuilder* tool did not build tools or packages unrelated to the RTEMS
    154 Project where no suitable *spec* file was available so another tool was
    155 needed. Rather than start again Chris decided to take the parsing code for the
    156 *spec* file format and build a new tool called the RTEMS Source Builder.
    157 
    158136Controlling the Tools Build
    159137---------------------------
Note: See TracChangeset for help on using the changeset viewer.