summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/bsp-guide/bsp.xml2
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml11
-rw-r--r--documentation/dev-manual/dev-manual-intro.xml2
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml2
-rw-r--r--documentation/dev-manual/dev-manual-start.xml2
-rw-r--r--documentation/kernel-dev/kernel-dev-advanced.xml2
-rw-r--r--documentation/kernel-dev/kernel-dev-common.xml2
-rw-r--r--documentation/kernel-dev/kernel-dev-intro.xml2
-rw-r--r--documentation/ref-manual/closer-look.xml2
-rw-r--r--documentation/ref-manual/migration.xml2
-rw-r--r--documentation/ref-manual/ref-bitbake.xml4
-rw-r--r--documentation/ref-manual/ref-classes.xml4
-rw-r--r--documentation/ref-manual/ref-features.xml2
-rw-r--r--documentation/ref-manual/ref-release-process.xml2
-rw-r--r--documentation/ref-manual/ref-structure.xml4
-rw-r--r--documentation/ref-manual/ref-variables.xml10
-rw-r--r--documentation/ref-manual/technical-details.xml6
-rw-r--r--documentation/sdk-manual/sdk-intro.xml2
18 files changed, 32 insertions, 31 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 9226e5cdd4..40c2a7dd27 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -417,7 +417,7 @@
417 released with the BSP. 417 released with the BSP.
418 The information in the <filename>README.sources</filename> 418 The information in the <filename>README.sources</filename>
419 file also helps you find the 419 file also helps you find the
420 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 420 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
421 used to generate the images that ship with the BSP. 421 used to generate the images that ship with the BSP.
422 <note> 422 <note>
423 If the BSP's <filename>binary</filename> directory is 423 If the BSP's <filename>binary</filename> directory is
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index d73b663250..108ac78fe0 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -18,7 +18,8 @@
18 18
19 <para> 19 <para>
20 The OpenEmbedded build system supports organizing 20 The OpenEmbedded build system supports organizing
21 <link linkend='metadata'>Metadata</link> into multiple layers. 21 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> into
22 multiple layers.
22 Layers allow you to isolate different types of customizations from 23 Layers allow you to isolate different types of customizations from
23 each other. 24 each other.
24 You might find it tempting to keep everything in one layer when 25 You might find it tempting to keep everything in one layer when
@@ -6933,8 +6934,8 @@
6933 <para> 6934 <para>
6934 When you build an image using the Yocto Project and 6935 When you build an image using the Yocto Project and
6935 do not alter any distribution 6936 do not alter any distribution
6936 <link linkend='metadata'>Metadata</link>, you are creating a 6937 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>,
6937 Poky distribution. 6938 you are creating a Poky distribution.
6938 If you wish to gain more control over package alternative 6939 If you wish to gain more control over package alternative
6939 selections, compile-time options, and other low-level 6940 selections, compile-time options, and other low-level
6940 configurations, you can create your own distribution. 6941 configurations, you can create your own distribution.
@@ -11680,8 +11681,8 @@
11680 " 11681 "
11681 </literallayout> 11682 </literallayout>
11682 Creating and providing an archive of the 11683 Creating and providing an archive of the
11683 <link linkend='metadata'>Metadata</link> layers 11684 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
11684 (recipes, configuration files, and so forth) 11685 layers (recipes, configuration files, and so forth)
11685 enables you to meet your 11686 enables you to meet your
11686 requirements to include the scripts to control compilation 11687 requirements to include the scripts to control compilation
11687 as well as any modifications to the original source. 11688 as well as any modifications to the original source.
diff --git a/documentation/dev-manual/dev-manual-intro.xml b/documentation/dev-manual/dev-manual-intro.xml
index 020f9373e6..98d5d53758 100644
--- a/documentation/dev-manual/dev-manual-intro.xml
+++ b/documentation/dev-manual/dev-manual-intro.xml
@@ -36,7 +36,7 @@
36 <note> 36 <note>
37 By default, using the Yocto Project creates a Poky distribution. 37 By default, using the Yocto Project creates a Poky distribution.
38 However, you can create your own distribution by providing key 38 However, you can create your own distribution by providing key
39 <link linkend='metadata'>Metadata</link>. 39 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>.
40 A good example is Angstrom, which has had a distribution 40 A good example is Angstrom, which has had a distribution
41 based on the Yocto Project since its inception. 41 based on the Yocto Project since its inception.
42 Other examples include commercial distributions like 42 Other examples include commercial distributions like
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 5a3e3ea107..b9fc265211 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -211,7 +211,7 @@
211 211
212 <para> 212 <para>
213 Keeping your 213 Keeping your
214 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 214 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
215 and any software you are developing under the 215 and any software you are developing under the
216 control of an SCM system that is compatible 216 control of an SCM system that is compatible
217 with the OpenEmbedded build system is advisable. 217 with the OpenEmbedded build system is advisable.
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index 6b97c52ada..271c9fed0e 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -41,7 +41,7 @@
41 <note> 41 <note>
42 By default, using the Yocto Project creates a Poky distribution. 42 By default, using the Yocto Project creates a Poky distribution.
43 However, you can create your own distribution by providing key 43 However, you can create your own distribution by providing key
44 <link linkend='metadata'>Metadata</link>. 44 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>.
45 See the "<link linkend='creating-your-own-distribution'>Creating Your Own Distribution</link>" 45 See the "<link linkend='creating-your-own-distribution'>Creating Your Own Distribution</link>"
46 section for more information. 46 section for more information.
47 </note> 47 </note>
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml
index 5c08019655..22afc66587 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -11,7 +11,7 @@
11 <para> 11 <para>
12 In addition to supporting configuration fragments and patches, the 12 In addition to supporting configuration fragments and patches, the
13 Yocto Project kernel tools also support rich 13 Yocto Project kernel tools also support rich
14 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> that you can 14 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> that you can
15 use to define complex policies and Board Support Package (BSP) support. 15 use to define complex policies and Board Support Package (BSP) support.
16 The purpose of the Metadata and the tools that manage it, known as 16 The purpose of the Metadata and the tools that manage it, known as
17 the kern-tools (<filename>kern-tools-native_git.bb</filename>), is 17 the kern-tools (<filename>kern-tools-native_git.bb</filename>), is
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index 5af0f9a927..8c74a7081e 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -759,7 +759,7 @@
759 working with your own sources. 759 working with your own sources.
760 When you use your own sources, you will not be able to 760 When you use your own sources, you will not be able to
761 leverage the existing kernel 761 leverage the existing kernel
762 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> and 762 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> and
763 stabilization work of the linux-yocto sources. 763 stabilization work of the linux-yocto sources.
764 However, you will be able to manage your own Metadata in the same 764 However, you will be able to manage your own Metadata in the same
765 format as the linux-yocto sources. 765 format as the linux-yocto sources.
diff --git a/documentation/kernel-dev/kernel-dev-intro.xml b/documentation/kernel-dev/kernel-dev-intro.xml
index 263e50098f..83ca988acf 100644
--- a/documentation/kernel-dev/kernel-dev-intro.xml
+++ b/documentation/kernel-dev/kernel-dev-intro.xml
@@ -35,7 +35,7 @@
35 Regardless of how you intend to make use of the Yocto Project, 35 Regardless of how you intend to make use of the Yocto Project,
36 chances are you will work with the Linux kernel. 36 chances are you will work with the Linux kernel.
37 This manual provides background information on the Yocto Linux kernel 37 This manual provides background information on the Yocto Linux kernel
38 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>, 38 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>,
39 describes common tasks you can perform using the kernel tools, 39 describes common tasks you can perform using the kernel tools,
40 and shows you how to use the kernel Metadata needed to work with 40 and shows you how to use the kernel Metadata needed to work with
41 the kernel inside the Yocto Project. 41 the kernel inside the Yocto Project.
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index e4a2a022a7..5046465fba 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -12,7 +12,7 @@
12 high level. 12 high level.
13 The remainder of this chapter expands on the fundamental input, output, 13 The remainder of this chapter expands on the fundamental input, output,
14 process, and 14 process, and
15 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>) blocks 15 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>) blocks
16 in the Yocto Project development environment. 16 in the Yocto Project development environment.
17 </para> 17 </para>
18 18
diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml
index 5c700bc5ea..b6b067b910 100644
--- a/documentation/ref-manual/migration.xml
+++ b/documentation/ref-manual/migration.xml
@@ -251,7 +251,7 @@
251 The following recipes have been removed. 251 The following recipes have been removed.
252 For most of them, it is unlikely that you would have any 252 For most of them, it is unlikely that you would have any
253 references to them in your own 253 references to them in your own
254 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>. 254 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>.
255 However, you should check your metadata against this list to be sure: 255 However, you should check your metadata against this list to be sure:
256 <itemizedlist> 256 <itemizedlist>
257 <listitem><para><emphasis><filename>libx11-trim</filename></emphasis>: 257 <listitem><para><emphasis><filename>libx11-trim</filename></emphasis>:
diff --git a/documentation/ref-manual/ref-bitbake.xml b/documentation/ref-manual/ref-bitbake.xml
index 2f36e16eaf..9a9499115c 100644
--- a/documentation/ref-manual/ref-bitbake.xml
+++ b/documentation/ref-manual/ref-bitbake.xml
@@ -8,7 +8,7 @@
8 8
9 <para> 9 <para>
10 BitBake is a program written in Python that interprets the 10 BitBake is a program written in Python that interprets the
11 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> used by 11 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> used by
12 the OpenEmbedded build system. 12 the OpenEmbedded build system.
13 At some point, developers wonder what actually happens when you enter: 13 At some point, developers wonder what actually happens when you enter:
14 <literallayout class='monospaced'> 14 <literallayout class='monospaced'>
@@ -24,7 +24,7 @@
24 BitBake strives to be a generic "task" executor that is capable of handling complex dependency relationships. 24 BitBake strives to be a generic "task" executor that is capable of handling complex dependency relationships.
25 As such, it has no real knowledge of what the tasks being executed actually do. 25 As such, it has no real knowledge of what the tasks being executed actually do.
26 BitBake just considers a list of tasks with dependencies and handles 26 BitBake just considers a list of tasks with dependencies and handles
27 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 27 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
28 consisting of variables in a certain format that get passed to the tasks. 28 consisting of variables in a certain format that get passed to the tasks.
29 </note> 29 </note>
30 30
diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index 472215c25a..1801faf501 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -16,7 +16,7 @@
16</para> 16</para>
17 17
18<para> 18<para>
19 Any <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> usually 19 Any <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> usually
20 found in a recipe can also be placed in a class file. 20 found in a recipe can also be placed in a class file.
21 Class files are identified by the extension <filename>.bbclass</filename> 21 Class files are identified by the extension <filename>.bbclass</filename>
22 and are usually placed in a <filename>classes/</filename> directory beneath 22 and are usually placed in a <filename>classes/</filename> directory beneath
@@ -2419,7 +2419,7 @@ This check was removed for YP 2.3 release
2419 all dependencies previously built. 2419 all dependencies previously built.
2420 The reason for this discrepancy is because the RPM package manager 2420 The reason for this discrepancy is because the RPM package manager
2421 creates and processes more 2421 creates and processes more
2422 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> than the 2422 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> than the
2423 IPK package manager. 2423 IPK package manager.
2424 Consequently, you might consider setting 2424 Consequently, you might consider setting
2425 <filename>PACKAGE_CLASSES</filename> to "package_ipk" if you are 2425 <filename>PACKAGE_CLASSES</filename> to "package_ipk" if you are
diff --git a/documentation/ref-manual/ref-features.xml b/documentation/ref-manual/ref-features.xml
index 7e1c5ef2f1..551db6535a 100644
--- a/documentation/ref-manual/ref-features.xml
+++ b/documentation/ref-manual/ref-features.xml
@@ -36,7 +36,7 @@
36 <para> 36 <para>
37 One method you can use to determine which recipes are checking to see if a 37 One method you can use to determine which recipes are checking to see if a
38 particular feature is contained or not is to <filename>grep</filename> through 38 particular feature is contained or not is to <filename>grep</filename> through
39 the <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 39 the <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
40 for the feature. 40 for the feature.
41 Here is an example that discovers the recipes whose build is potentially 41 Here is an example that discovers the recipes whose build is potentially
42 changed based on a given feature: 42 changed based on a given feature:
diff --git a/documentation/ref-manual/ref-release-process.xml b/documentation/ref-manual/ref-release-process.xml
index fe3ba0933e..aa1ff89a7d 100644
--- a/documentation/ref-manual/ref-release-process.xml
+++ b/documentation/ref-manual/ref-release-process.xml
@@ -63,7 +63,7 @@
63 the 63 the
64 <ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>. 64 <ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>.
65 The concept is that branches of 65 The concept is that branches of
66 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 66 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
67 with the same codename are likely to be compatible and thus 67 with the same codename are likely to be compatible and thus
68 work together. 68 work together.
69 <note> 69 <note>
diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml
index 424b8cc003..3b3f0779cd 100644
--- a/documentation/ref-manual/ref-structure.xml
+++ b/documentation/ref-manual/ref-structure.xml
@@ -42,7 +42,7 @@
42 The copy usually matches the current stable BitBake release from 42 The copy usually matches the current stable BitBake release from
43 the BitBake project. 43 the BitBake project.
44 BitBake, a 44 BitBake, a
45 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 45 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
46 interpreter, reads the Yocto Project Metadata and runs the tasks 46 interpreter, reads the Yocto Project Metadata and runs the tasks
47 defined by that data. 47 defined by that data.
48 Failures are usually from the Metadata and not from BitBake itself. 48 Failures are usually from the Metadata and not from BitBake itself.
@@ -1023,7 +1023,7 @@
1023 1023
1024 <para> 1024 <para>
1025 As mentioned previously, 1025 As mentioned previously,
1026 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> is the core 1026 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> is the core
1027 of the Yocto Project. 1027 of the Yocto Project.
1028 Metadata has several important subdivisions: 1028 Metadata has several important subdivisions:
1029 </para> 1029 </para>
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index da4da8550d..632d78aa7e 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -1969,7 +1969,7 @@
1969<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> --> 1969<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
1970 Specifies the directory BitBake uses to store a cache 1970 Specifies the directory BitBake uses to store a cache
1971 of the 1971 of the
1972 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 1972 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
1973 so it does not need to be parsed every time BitBake is 1973 so it does not need to be parsed every time BitBake is
1974 started. 1974 started.
1975 </para> 1975 </para>
@@ -3455,7 +3455,7 @@
3455 <para> 3455 <para>
3456 Distribution configuration files are located in a 3456 Distribution configuration files are located in a
3457 <filename>conf/distro</filename> directory within the 3457 <filename>conf/distro</filename> directory within the
3458 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 3458 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
3459 that contains the distribution configuration. 3459 that contains the distribution configuration.
3460 The value for <filename>DISTRO</filename> must not contain 3460 The value for <filename>DISTRO</filename> must not contain
3461 spaces, and is typically all lower-case. 3461 spaces, and is typically all lower-case.
@@ -7037,7 +7037,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
7037<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> --> 7037<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
7038 Includes additional metadata from the Yocto Project kernel Git repository. 7038 Includes additional metadata from the Yocto Project kernel Git repository.
7039 In the OpenEmbedded build system, the default Board Support Packages (BSPs) 7039 In the OpenEmbedded build system, the default Board Support Packages (BSPs)
7040 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 7040 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
7041 is provided through 7041 is provided through
7042 the <link linkend='var-KMACHINE'><filename>KMACHINE</filename></link> 7042 the <link linkend='var-KMACHINE'><filename>KMACHINE</filename></link>
7043 and <link linkend='var-KBRANCH'><filename>KBRANCH</filename></link> variables. 7043 and <link linkend='var-KBRANCH'><filename>KBRANCH</filename></link> variables.
@@ -7839,7 +7839,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
7839 defines the search 7839 defines the search
7840 arguments used by the kernel tools to find the appropriate 7840 arguments used by the kernel tools to find the appropriate
7841 description within the kernel 7841 description within the kernel
7842 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 7842 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
7843 with which to build out the sources and configuration. 7843 with which to build out the sources and configuration.
7844 </para> 7844 </para>
7845 </glossdef> 7845 </glossdef>
@@ -12620,7 +12620,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
12620 <listitem><para><emphasis><filename>file://</filename> -</emphasis> 12620 <listitem><para><emphasis><filename>file://</filename> -</emphasis>
12621 Fetches files, which are usually files shipped with 12621 Fetches files, which are usually files shipped with
12622 the 12622 the
12623 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>, 12623 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>,
12624 from the local machine. 12624 from the local machine.
12625 The path is relative to the 12625 The path is relative to the
12626 <link linkend='var-FILESPATH'><filename>FILESPATH</filename></link> 12626 <link linkend='var-FILESPATH'><filename>FILESPATH</filename></link>
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 597bfbc55b..768f70186b 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -65,7 +65,7 @@
65 <para> 65 <para>
66 BitBake is the tool at the heart of the OpenEmbedded build system 66 BitBake is the tool at the heart of the OpenEmbedded build system
67 and is responsible for parsing the 67 and is responsible for parsing the
68 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>, 68 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>,
69 generating a list of tasks from it, and then executing those tasks. 69 generating a list of tasks from it, and then executing those tasks.
70 </para> 70 </para>
71 71
@@ -152,7 +152,7 @@
152 <para> 152 <para>
153 Class files (<filename>.bbclass</filename>) contain information that 153 Class files (<filename>.bbclass</filename>) contain information that
154 is useful to share between 154 is useful to share between
155 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> files. 155 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> files.
156 An example is the 156 An example is the
157 <link linkend='ref-classes-autotools'><filename>autotools</filename></link> 157 <link linkend='ref-classes-autotools'><filename>autotools</filename></link>
158 class, which contains common settings for any application that 158 class, which contains common settings for any application that
@@ -610,7 +610,7 @@
610 The "OEBasicHash" <filename>BB_SIGNATURE_HANDLER</filename> is the same as the 610 The "OEBasicHash" <filename>BB_SIGNATURE_HANDLER</filename> is the same as the
611 "OEBasic" version but adds the task hash to the stamp files. 611 "OEBasic" version but adds the task hash to the stamp files.
612 This results in any 612 This results in any
613 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 613 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
614 change that changes the task hash, automatically 614 change that changes the task hash, automatically
615 causing the task to be run again. 615 causing the task to be run again.
616 This removes the need to bump <link linkend='var-PR'><filename>PR</filename></link> 616 This removes the need to bump <link linkend='var-PR'><filename>PR</filename></link>
diff --git a/documentation/sdk-manual/sdk-intro.xml b/documentation/sdk-manual/sdk-intro.xml
index 10af621a02..c2e43c2deb 100644
--- a/documentation/sdk-manual/sdk-intro.xml
+++ b/documentation/sdk-manual/sdk-intro.xml
@@ -93,7 +93,7 @@
93 matching sysroots (target and native) all built by the 93 matching sysroots (target and native) all built by the
94 OpenEmbedded build system (e.g. the SDK). 94 OpenEmbedded build system (e.g. the SDK).
95 The toolchain and sysroots are based on a 95 The toolchain and sysroots are based on a
96 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> 96 <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
97 configuration and extensions, 97 configuration and extensions,
98 which allows you to cross-develop on the host machine for the 98 which allows you to cross-develop on the host machine for the
99 target hardware. 99 target hardware.