diff options
author | Scott Rifenbark <srifenbark@gmail.com> | 2017-06-13 17:47:10 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-06-22 09:16:42 +0100 |
commit | 74bf586c940d20fc5546a60a290545c7c0edecb0 (patch) | |
tree | 5887ef777422efab49cc0ff37de17cd736faa242 /documentation/ref-manual/ref-structure.xml | |
parent | b8b87dd690ef2f828c21937ec82c2d1dab405734 (diff) | |
download | poky-74bf586c940d20fc5546a60a290545c7c0edecb0.tar.gz |
documentation: Fixed links for "build-directory" term.
Fixes [YOCTO #11630]
Moving the "Yocto Project Terms" section from the dev-manual to the
ref-manual broke several links to the id "build-directory". I fixed
these to reference into the ref-manual now.
(From yocto-docs rev: debe2ae8ce203ebe0f1cee0de54124c15df8bb7e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/ref-structure.xml')
-rw-r--r-- | documentation/ref-manual/ref-structure.xml | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml index b0c4bfeaa4..424b8cc003 100644 --- a/documentation/ref-manual/ref-structure.xml +++ b/documentation/ref-manual/ref-structure.xml | |||
@@ -75,7 +75,8 @@ | |||
75 | This directory contains user configuration files and the output | 75 | This directory contains user configuration files and the output |
76 | generated by the OpenEmbedded build system in its standard configuration where | 76 | generated by the OpenEmbedded build system in its standard configuration where |
77 | the source tree is combined with the output. | 77 | the source tree is combined with the output. |
78 | The <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> | 78 | The |
79 | <link linkend='build-directory'>Build Directory</link> | ||
79 | is created initially when you <filename>source</filename> | 80 | is created initially when you <filename>source</filename> |
80 | the OpenEmbedded build environment setup script | 81 | the OpenEmbedded build environment setup script |
81 | (i.e. | 82 | (i.e. |
@@ -212,7 +213,7 @@ | |||
212 | <para> | 213 | <para> |
213 | When you run this script, your Yocto Project environment is set | 214 | When you run this script, your Yocto Project environment is set |
214 | up, a | 215 | up, a |
215 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> | 216 | <link linkend='build-directory'>Build Directory</link> |
216 | is created, your working directory becomes the Build Directory, | 217 | is created, your working directory becomes the Build Directory, |
217 | and you are presented with a list of common BitBake targets. | 218 | and you are presented with a list of common BitBake targets. |
218 | Here is an example: | 219 | Here is an example: |
@@ -246,7 +247,7 @@ | |||
246 | 247 | ||
247 | <para> | 248 | <para> |
248 | By default, running this script without a | 249 | By default, running this script without a |
249 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> | 250 | <link linkend='build-directory'>Build Directory</link> |
250 | argument creates the <filename>build</filename> directory | 251 | argument creates the <filename>build</filename> directory |
251 | in your current working directory. | 252 | in your current working directory. |
252 | If you provide a Build Directory argument when you | 253 | If you provide a Build Directory argument when you |
@@ -330,7 +331,7 @@ | |||
330 | <listitem><para> | 331 | <listitem><para> |
331 | The script's parameters are positionally dependent. | 332 | The script's parameters are positionally dependent. |
332 | Consequently, you cannot run the script and provide a | 333 | Consequently, you cannot run the script and provide a |
333 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> | 334 | <link linkend='build-directory'>Build Directory</link> |
334 | name without also providing a port number. | 335 | name without also providing a port number. |
335 | In other words, the following syntax is illegal: | 336 | In other words, the following syntax is illegal: |
336 | <literallayout class='monospaced'> | 337 | <literallayout class='monospaced'> |
@@ -386,7 +387,7 @@ | |||
386 | 387 | ||
387 | <para> | 388 | <para> |
388 | By default, running this script without a | 389 | By default, running this script without a |
389 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> | 390 | <link linkend='build-directory'>Build Directory</link> |
390 | argument creates a build directory named | 391 | argument creates a build directory named |
391 | <filename>build</filename>. | 392 | <filename>build</filename>. |
392 | If you provide a Build Directory argument and port number when you | 393 | If you provide a Build Directory argument and port number when you |
@@ -443,7 +444,7 @@ | |||
443 | 444 | ||
444 | <para> | 445 | <para> |
445 | The OpenEmbedded build system creates the | 446 | The OpenEmbedded build system creates the |
446 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> | 447 | <link linkend='build-directory'>Build Directory</link> |
447 | when you run one of the build environment setup scripts (i.e. | 448 | when you run one of the build environment setup scripts (i.e. |
448 | <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link> | 449 | <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link> |
449 | or | 450 | or |