diff options
| author | Gedare Bloom <gedare@rtems.org> | 2020-04-05 14:47:27 -0600 |
|---|---|---|
| committer | Gedare Bloom <gedare@rtems.org> | 2020-04-05 14:47:27 -0600 |
| commit | c9cb173eb798238ce614cddd53b0fdf5a0cf0a05 (patch) | |
| tree | 383fabddb6c9584e65fa22825bcea6d13ba8cffd /user/rsb/configuration.rst | |
| parent | user/rsb/configuration: fix typo xy to xz (diff) | |
| download | rtems-docs-c9cb173eb798238ce614cddd53b0fdf5a0cf0a05.tar.bz2 | |
rsb: replace asciidoc with rst formatting
Diffstat (limited to 'user/rsb/configuration.rst')
| -rw-r--r-- | user/rsb/configuration.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst index 541b3fd..8d0ac14 100644 --- a/user/rsb/configuration.rst +++ b/user/rsb/configuration.rst @@ -972,10 +972,10 @@ expansions supported are: %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 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: .. code-block:: spec @@ -999,7 +999,7 @@ example: 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 -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 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 @@ -1040,9 +1040,9 @@ and set up with: 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 -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 -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 |