From 74bf586c940d20fc5546a60a290545c7c0edecb0 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <srifenbark@gmail.com>
Date: Tue, 13 Jun 2017 17:47:10 -0700
Subject: 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>
---
 documentation/dev-manual/dev-manual-model.xml | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

(limited to 'documentation/dev-manual/dev-manual-model.xml')

diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 0782f0acdb..068fd66893 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -87,7 +87,8 @@
 
         <note>
             For a brief list of terms used when describing the development process in the Yocto Project,
-            see the "<link linkend='yocto-project-terms'>Yocto Project Terms</link>" section.
+            see the
+            "<ulink url='&YOCTO_DOCS_REF_URL;#yocto-project-terms'>Yocto Project Terms</ulink>" section.
         </note>
 
         <para>
@@ -431,8 +432,8 @@
                 The following figure shows the temporary file structure
                 created on your host system when the build occurs.
                 This
-                <link linkend='build-directory'>Build Directory</link> contains all the
-                source files used during the build.
+                <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>
+                contains all the source files used during the build.
             </para>
 
             <para>
@@ -478,7 +479,7 @@
                         </para></listitem>
                     <listitem><para><emphasis>Establish the temporary kernel source files</emphasis>:
                         Temporary kernel source files are kept in the
-                        <link linkend='build-directory'>Build Directory</link>
+                        <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>
                         created by the
                         OpenEmbedded build system when you run BitBake.
                         If you have never built the kernel in which you are
@@ -1270,7 +1271,7 @@
                 <listitem><para><emphasis>Find the Source Code:</emphasis>
                     Temporary source code used by the OpenEmbedded build system
                     is kept in the
-                    <link linkend='build-directory'>Build Directory</link>.
+                    <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>.
                     See the
                     "<link linkend='finding-the-temporary-source-code'>Finding Temporary Source Code</link>"
                     section to learn how to locate the directory that has the
@@ -1364,8 +1365,8 @@
             experiment a bit to figure out your solution.
             After you have initially built the package, you can iteratively
             tweak the source code, which is located in the
-            <link linkend='build-directory'>Build Directory</link>, and then
-            you can force a re-compile and quickly test your altered code.
+            <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>,
+            and then you can force a re-compile and quickly test your altered code.
             Once you settle on a solution, you can then preserve your changes
             in the form of patches.
             If you are using Quilt for development, see the
-- 
cgit v1.2.3-54-g00ecf