summaryrefslogtreecommitdiffstats
path: root/documentation/sdk-manual/appendix-customizing.rst
diff options
context:
space:
mode:
authorQuentin Schulz <foss@0leil.net>2021-04-07 18:07:24 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-04-09 15:24:46 +0100
commitc380ba5a177de32e97820279685c4af6f837c010 (patch)
treec494289cda99f5bb76bad0d9492a3d1104d176d4 /documentation/sdk-manual/appendix-customizing.rst
parent802ac0b75e42657c7ff9f4ff5b2816c65ad29eea (diff)
downloadpoky-c380ba5a177de32e97820279685c4af6f837c010.tar.gz
docs: replace anchor links
Anchor links are treated by Sphinx as external links and are not checked during build, meaning it is impossible to know if a link becomes broken or not. As a matter of fact, most of the anchor links replaced in this commit were actually broken. The README now states that anchor links are forbidden so that there's no need to go through such a change later on. (From yocto-docs rev: de9e4d26b46afa3c79137d07529a74553400d2e0) Signed-off-by: Quentin Schulz <foss@0leil.net> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/sdk-manual/appendix-customizing.rst')
-rw-r--r--documentation/sdk-manual/appendix-customizing.rst25
1 files changed, 11 insertions, 14 deletions
diff --git a/documentation/sdk-manual/appendix-customizing.rst b/documentation/sdk-manual/appendix-customizing.rst
index cdfde8b4b2..8e7115046b 100644
--- a/documentation/sdk-manual/appendix-customizing.rst
+++ b/documentation/sdk-manual/appendix-customizing.rst
@@ -101,17 +101,15 @@ adjustments:
101 101
102- Generally, you want to have a shared state mirror set up so users of 102- Generally, you want to have a shared state mirror set up so users of
103 the SDK can add additional items to the SDK after installation 103 the SDK can add additional items to the SDK after installation
104 without needing to build the items from source. See the "`Providing 104 without needing to build the items from source. See the
105 Additional Installable Extensible SDK 105 ":ref:`sdk-manual/appendix-customizing:providing additional installable extensible sdk content`"
106 Content <#sdk-providing-additional-installable-extensible-sdk-content>`__"
107 section for information. 106 section for information.
108 107
109- If you want users of the SDK to be able to easily update the SDK, you 108- If you want users of the SDK to be able to easily update the SDK, you
110 need to set the 109 need to set the
111 :term:`SDK_UPDATE_URL` 110 :term:`SDK_UPDATE_URL`
112 variable. For more information, see the "`Providing Updates to the 111 variable. For more information, see the
113 Extensible SDK After 112 ":ref:`sdk-manual/appendix-customizing:providing updates to the extensible sdk after installation`"
114 Installation <#sdk-providing-updates-to-the-extensible-sdk-after-installation>`__"
115 section. 113 section.
116 114
117- If you have adjusted the list of files and directories that appear in 115- If you have adjusted the list of files and directories that appear in
@@ -140,8 +138,8 @@ Changing the Extensible SDK Installer Title
140You can change the displayed title for the SDK installer by setting the 138You can change the displayed title for the SDK installer by setting the
141:term:`SDK_TITLE` variable and then 139:term:`SDK_TITLE` variable and then
142rebuilding the SDK installer. For information on how to build an SDK 140rebuilding the SDK installer. For information on how to build an SDK
143installer, see the "`Building an SDK 141installer, see the ":ref:`sdk-manual/appendix-obtain:building an sdk installer`"
144Installer <#sdk-building-an-sdk-installer>`__" section. 142section.
145 143
146By default, this title is derived from 144By default, this title is derived from
147:term:`DISTRO_NAME` when it is 145:term:`DISTRO_NAME` when it is
@@ -189,9 +187,8 @@ the installed SDKs to update the installed SDKs by using the
189 variable to point to the corresponding HTTP or HTTPS URL. Setting 187 variable to point to the corresponding HTTP or HTTPS URL. Setting
190 this variable causes any SDK built to default to that URL and thus, 188 this variable causes any SDK built to default to that URL and thus,
191 the user does not have to pass the URL to the ``devtool sdk-update`` 189 the user does not have to pass the URL to the ``devtool sdk-update``
192 command as described in the "`Applying Updates to an Installed 190 command as described in the
193 Extensible 191 ":ref:`sdk-manual/extensible:applying updates to an installed extensible sdk`"
194 SDK <#sdk-applying-updates-to-an-installed-extensible-sdk>`__"
195 section. 192 section.
196 193
1973. Build the extensible SDK normally (i.e., use the 1943. Build the extensible SDK normally (i.e., use the
@@ -208,9 +205,9 @@ the installed SDKs to update the installed SDKs by using the
208 205
209Completing the above steps allows users of the existing installed SDKs 206Completing the above steps allows users of the existing installed SDKs
210to simply run ``devtool sdk-update`` to retrieve and apply the latest 207to simply run ``devtool sdk-update`` to retrieve and apply the latest
211updates. See the "`Applying Updates to an Installed Extensible 208updates. See the
212SDK <#sdk-applying-updates-to-an-installed-extensible-sdk>`__" section 209":ref:`sdk-manual/extensible:applying updates to an installed extensible sdk`"
213for further information. 210section for further information.
214 211
215Changing the Default SDK Installation Directory 212Changing the Default SDK Installation Directory
216=============================================== 213===============================================