diff options
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r-- | documentation/ref-manual/ref-devtool-reference.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/ref-manual/ref-devtool-reference.xml b/documentation/ref-manual/ref-devtool-reference.xml index a577d1a457..f8342390ce 100644 --- a/documentation/ref-manual/ref-devtool-reference.xml +++ b/documentation/ref-manual/ref-devtool-reference.xml | |||
@@ -324,7 +324,7 @@ | |||
324 | Use the <filename>devtool modify</filename> command to begin | 324 | Use the <filename>devtool modify</filename> command to begin |
325 | modifying the source of an existing recipe. | 325 | modifying the source of an existing recipe. |
326 | This command is very similar to the | 326 | This command is very similar to the |
327 | <ulink url='&YOCTO_DOCS_DEV_URL;#devtool-adding-a-new-recipe-to-the-workspace'><filename>add</filename></ulink> | 327 | <link linkend='devtool-adding-a-new-recipe-to-the-workspace'><filename>add</filename></link> |
328 | command except that it does not physically create the | 328 | command except that it does not physically create the |
329 | recipe in the workspace layer because the recipe already | 329 | recipe in the workspace layer because the recipe already |
330 | exists in an another layer. | 330 | exists in an another layer. |
@@ -382,7 +382,7 @@ | |||
382 | to the source files. | 382 | to the source files. |
383 | For example, if you know you are going to work on some | 383 | For example, if you know you are going to work on some |
384 | code, you could first use the | 384 | code, you could first use the |
385 | <ulink url='&YOCTO_DOCS_DEV_URL;#devtool-modifying-a-recipe'><filename>devtool modify</filename></ulink> | 385 | <link linkend='devtool-modifying-a-recipe'><filename>devtool modify</filename></link> |
386 | command to extract the code and set up the workspace. | 386 | command to extract the code and set up the workspace. |
387 | After which, you could modify, compile, and test the code. | 387 | After which, you could modify, compile, and test the code. |
388 | </para> | 388 | </para> |
@@ -604,7 +604,7 @@ | |||
604 | remove deployed build output from the target machine. | 604 | remove deployed build output from the target machine. |
605 | For the <filename>devtool undeploy-target</filename> command to | 605 | For the <filename>devtool undeploy-target</filename> command to |
606 | work, you must have previously used the | 606 | work, you must have previously used the |
607 | <ulink url='&YOCTO_DOCS_DEV_URL;#devtool-deploying-your-software-on-the-target-machine'><filename>devtool deploy-target</filename></ulink> | 607 | <link linkend='devtool-deploying-your-software-on-the-target-machine'><filename>devtool deploy-target</filename></link> |
608 | command. | 608 | command. |
609 | <literallayout class='monospaced'> | 609 | <literallayout class='monospaced'> |
610 | $ devtool undeploy-target <replaceable>recipe</replaceable> <replaceable>target</replaceable> | 610 | $ devtool undeploy-target <replaceable>recipe</replaceable> <replaceable>target</replaceable> |
@@ -664,7 +664,7 @@ | |||
664 | $ devtool status | 664 | $ devtool status |
665 | </literallayout> | 665 | </literallayout> |
666 | Following is sample output after using | 666 | Following is sample output after using |
667 | <ulink url='&YOCTO_DOCS_DEV_URL;#devtool-adding-a-new-recipe-to-the-workspace'><filename>devtool add</filename></ulink> | 667 | <link linkend='devtool-adding-a-new-recipe-to-the-workspace'><filename>devtool add</filename></link> |
668 | to create and add the <filename>mtr_0.86.bb</filename> recipe | 668 | to create and add the <filename>mtr_0.86.bb</filename> recipe |
669 | to the <filename>workspace</filename> directory: | 669 | to the <filename>workspace</filename> directory: |
670 | <literallayout class='monospaced'> | 670 | <literallayout class='monospaced'> |