diff options
| author | Chris Johns <chrisj@rtems.org> | 2016-11-02 15:20:35 +1100 |
|---|---|---|
| committer | Chris Johns <chrisj@rtems.org> | 2016-11-02 15:20:35 +1100 |
| commit | 9742e45add23c7bb7f0f42a47421dc532fac9e45 (patch) | |
| tree | 5be37762733a95e769e92d48ae2d4b7958636613 /rsb/quick-start.rst | |
| parent | Update the top level README.txt. (diff) | |
| download | rtems-docs-9742e45add23c7bb7f0f42a47421dc532fac9e45.tar.bz2 | |
RSB: Fix the heading level for the PDF.
Diffstat (limited to '')
| -rw-r--r-- | rsb/quick-start.rst | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/rsb/quick-start.rst b/rsb/quick-start.rst index 1d4677e..e3696a5 100644 --- a/rsb/quick-start.rst +++ b/rsb/quick-start.rst @@ -4,7 +4,7 @@ .. comment Chris Johns <chrisj@rtems.org> Quick Start -########### +=========== The quick start will show you how to build a set of RTEMS tools for a supported architecture. The tools are installed into a build *prefix*. The *prefix* is the @@ -69,7 +69,7 @@ difficult to manage in production systems. Branches are available for the 4.9, 4.10, and 4.11 versions of RTEMS. Setup -~~~~~ +----- Setup a development work space:: @@ -91,7 +91,7 @@ from the RTEMS GIT repository:: about *Sandboxing* and the *prefix*. Checking -~~~~~~~~ +-------- The next step is to check if your host is set up correctly. The RTEMS Source Builder provides a tool to help:: @@ -124,7 +124,7 @@ The :ref:`Hosts` section lists packages you should install for common host operating systems. It maybe worth checking if you have those installed. Build Sets -~~~~~~~~~~ +---------- The RTEMS tools can be built within the RTEMS Source Builder's source tree. We recommend you do this so lets change into the RTEMS directory in the RTEMS @@ -203,7 +203,7 @@ build ask the tool:: set files. Building -~~~~~~~~ +-------- The quick start builds a SPARC tool set:: @@ -354,12 +354,12 @@ The installed tools:: level. The RTEMS Source Builder can build bare metal tool chains as well. Look in the top level ``bare`` directory. -Distributing and Archiving A Build -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Deployment +---------- If you wish to create and distribute your build or you want to archive a build -you can create a tar file. This is a more advanced method for binary packaging -and installing of tools. +you can create a tar file. We term this deploying a build. This is a more +advanced method for binary packaging and installing of tools. By default the RTEMS Source Builder installs the built packages directly and optionally it can also create a *build set tar file* or a *package tar file* @@ -508,7 +508,7 @@ build set:: 3. The build set tar file. All the others in a single tar file. Controlling the Build -~~~~~~~~~~~~~~~~~~~~~ +--------------------- Build sets can be controlled via the command line to enable and disable various features. There is no definitive list of build options that can be listed |