rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-07-24 04:34:25 +08:00
Code Issues Packages Projects Releases Wiki Activity

rsb: replace asciidoc with rst formatting

Browse Source
This commit is contained in:
Gedare Bloom 2020-04-05 14:47:27 -06:00
parent 79c37d2ed6
commit c9cb173eb7
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
user/rsb/commands.rst
View File

@ -199,22 +199,22 @@ The ``arguments`` are a list of build sets to build.
Path to the configuration directory. This overrides the built in defaults. Path to the configuration directory. This overrides the built in defaults.
``--builddir path``: ``--builddir path``:
Path to the build directory. This overrides the default of +build+. Path to the build directory. This overrides the default of `build`.
``--sourcedir path``: ``--sourcedir path``:
Path to the source directory. This overrides the default of +source+. Path to the source directory. This overrides the default of `source`.
``--patchdir path``: ``--patchdir path``:
Path to the patches directory. This overrides the default of +patches+. Path to the patches directory. This overrides the default of `patches`.
``--tmppath path``: ``--tmppath path``:
Path to the temporary directory. This overrides the default of +tmp+. Path to the temporary directory. This overrides the default of `tmp`.
``--macros files``: ``--macros files``:
Macro files to load. The configuration directory path is searched. Macro files to load. The configuration directory path is searched.
``--log file``: ``--log file``:
Log all the output from the build process. The output is directed to +stdout+ Log all the output from the build process. The output is directed to `stdout`
if no log file is provided. if no log file is provided.
``--url url``: ``--url url``:

10
user/rsb/configuration.rst
View File

@ -972,10 +972,10 @@ expansions supported are:
%prep %prep
~~~~~ ~~~~~
The +%prep+ macro starts a block that continues until the next block macro. The The `%prep` macro starts a block that continues until the next block macro. The
*prep* or preparation block defines the setup of the package's source and is a *prep* or preparation block defines the setup of the package's source and is a
mix of RTEMS Source Builder macros and shell scripting. The sequence is mix of RTEMS Source Builder macros and shell scripting. The sequence is
typically +%source+ macros for source, +%patch+ macros to patch the source typically `%source` macros for source, `%patch` macros to patch the source
mixed with some shell commands to correct any source issues: mixed with some shell commands to correct any source issues:
.. code-block:: spec .. code-block:: spec
@ -999,7 +999,7 @@ example:
This URL is the primary location of the GNU GDB source code and the RTEMS This URL is the primary location of the GNU GDB source code and the RTEMS
Source Builder can download the file from this location and by inspecting the Source Builder can download the file from this location and by inspecting the
file extension use ``bzip2`` decompression with +tar+. When the ``%prep`` file extension use ``bzip2`` decompression with `tar`. When the ``%prep``
section is processed a check of the local ``source`` directory is made to see section is processed a check of the local ``source`` directory is made to see
if the file has already been downloaded. If not found in the source cache if the file has already been downloaded. If not found in the source cache
directory the package is downloaded from the URL. You can append other base directory the package is downloaded from the URL. You can append other base
@ -1040,9 +1040,9 @@ and set up with:
Patching also occurs during the preparation stage. Patches are handled in a Patching also occurs during the preparation stage. Patches are handled in a
similar way to the source packages except you only ``add`` patches. Patches are similar way to the source packages except you only ``add`` patches. Patches are
applied using the +setup+ command. The +setup+ command takes the default patch applied using the `setup` command. The `setup` command takes the default patch
option. You can provide options with each patch by adding them as arguments option. You can provide options with each patch by adding them as arguments
before the patch URL. Patches with no options uses the +setup+ default. before the patch URL. Patches with no options uses the `setup` default.
.. code-block:: spec .. code-block:: spec