summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-devtool-reference.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/ref-devtool-reference.rst')
-rw-r--r--documentation/ref-manual/ref-devtool-reference.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/ref-manual/ref-devtool-reference.rst b/documentation/ref-manual/ref-devtool-reference.rst
index 5bb1a64d99..b0c4bcc7a0 100644
--- a/documentation/ref-manual/ref-devtool-reference.rst
+++ b/documentation/ref-manual/ref-devtool-reference.rst
@@ -217,7 +217,7 @@ Git, checks out a branch for development, and applies any patches from
217the recipe as commits on top. You can use the following command to 217the recipe as commits on top. You can use the following command to
218checkout the source files: $ devtool modify recipe Using the above 218checkout the source files: $ devtool modify recipe Using the above
219command form, ``devtool`` uses the existing recipe's 219command form, ``devtool`` uses the existing recipe's
220```SRC_URI`` <#var-SRC_URI>`__ statement to locate the upstream source, 220:term:`SRC_URI` statement to locate the upstream source,
221extracts the source into the default sources location in the workspace. 221extracts the source into the default sources location in the workspace.
222The default development branch used is "devtool". 222The default development branch used is "devtool".
223 223
@@ -360,9 +360,9 @@ When you use the ``devtool upgrade`` command, you must supply the root
360name of the recipe (i.e. no version, paths, or extensions), and you must 360name of the recipe (i.e. no version, paths, or extensions), and you must
361supply the directory to which you want the source extracted. Additional 361supply the directory to which you want the source extracted. Additional
362command options let you control things such as the version number to 362command options let you control things such as the version number to
363which you want to upgrade (i.e. the ```PV`` <#var-PV>`__), the source 363which you want to upgrade (i.e. the :term:`PV`), the source
364revision to which you want to upgrade (i.e. the 364revision to which you want to upgrade (i.e. the
365```SRCREV`` <#var-SRCREV>`__), whether or not to apply patches, and so 365:term:`SRCREV`), whether or not to apply patches, and so
366forth. 366forth.
367 367
368You can read more on the ``devtool upgrade`` workflow in the "`Use 368You can read more on the ``devtool upgrade`` workflow in the "`Use
@@ -439,7 +439,7 @@ The target is the address of the target machine, which must be running
439an SSH server (i.e. ``user@hostname[:destdir]``). 439an SSH server (i.e. ``user@hostname[:destdir]``).
440 440
441This command deploys all files installed during the 441This command deploys all files installed during the
442```do_install`` <#ref-tasks-install>`__ task. Furthermore, you do not 442:ref:`ref-tasks-install` task. Furthermore, you do not
443need to have package management enabled within the target machine. If 443need to have package management enabled within the target machine. If
444you do, the package manager is bypassed. 444you do, the package manager is bypassed.
445 445
@@ -492,7 +492,7 @@ Creating the Workspace Layer in an Alternative Location
492======================================================= 492=======================================================
493 493
494Use the ``devtool create-workspace`` command to create a new workspace 494Use the ``devtool create-workspace`` command to create a new workspace
495layer in your `Build Directory <#build-directory>`__. When you create a 495layer in your :term:`Build Directory`. When you create a
496new workspace layer, it is populated with the ``README`` file and the 496new workspace layer, it is populated with the ``README`` file and the
497``conf`` directory only. 497``conf`` directory only.
498 498