From c380ba5a177de32e97820279685c4af6f837c010 Mon Sep 17 00:00:00 2001 From: Quentin Schulz Date: Wed, 7 Apr 2021 18:07:24 +0200 Subject: 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 Reviewed-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/sdk-manual/using.rst | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'documentation/sdk-manual/using.rst') diff --git a/documentation/sdk-manual/using.rst b/documentation/sdk-manual/using.rst index 29fb50465f..62967f5572 100644 --- a/documentation/sdk-manual/using.rst +++ b/documentation/sdk-manual/using.rst @@ -16,8 +16,9 @@ standard SDK. " section. You can use a standard SDK to work on Makefile and Autotools-based -projects. See the "`Using the SDK Toolchain -Directly <#sdk-working-projects>`__" chapter for more information. +projects. See the +":ref:`sdk-manual/working-projects:using the sdk toolchain directly`" chapter +for more information. Why use the Standard SDK and What is in It? =========================================== @@ -31,9 +32,9 @@ the extensible SDK, which provides an internal build system and the The installed Standard SDK consists of several files and directories. Basically, it contains an SDK environment setup script, some configuration files, and host and target root filesystems to support -usage. You can see the directory structure in the "`Installed Standard -SDK Directory -Structure <#sdk-installed-standard-sdk-directory-structure>`__" section. +usage. You can see the directory structure in the +":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`" +section. Installing the SDK ================== @@ -120,9 +121,9 @@ architecture. The example assumes the SDK installer is located in Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . /opt/poky/&DISTRO;/environment-setup-i586-poky-linux -Again, reference the "`Installed Standard SDK Directory -Structure <#sdk-installed-standard-sdk-directory-structure>`__" section -for more details on the resulting directory structure of the installed +Again, reference the +":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`" +section for more details on the resulting directory structure of the installed SDK. Running the SDK Environment Setup Script @@ -147,7 +148,6 @@ script is for an IA-based target machine using i586 tuning: When you run the setup script, the same environment variables are defined as are when you -run the setup script for an extensible SDK. See the "`Running the -Extensible SDK Environment Setup -Script <#sdk-running-the-extensible-sdk-environment-setup-script>`__" +run the setup script for an extensible SDK. See the +":ref:`sdk-manual/appendix-obtain:installed extensible sdk directory structure`" section for more information. -- cgit v1.2.3-54-g00ecf