Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Paul Eggleton" <paul.eggleton@linux.microsoft.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH v2 11/14] ref-manual: tweak buildtools section
Date: Thu, 15 Apr 2021 02:59:09 -0700	[thread overview]
Message-ID: <e2506aa00aae03acf266efcd0a7797f2306791e2.1618480508.git.paul.eggleton@linux.microsoft.com> (raw)
In-Reply-To: <cover.1618480508.git.paul.eggleton@linux.microsoft.com>

From: Paul Eggleton <paul.eggleton@microsoft.com>

Add a joining paragraph and fix the second section so that it makes
sense with the addition of the first one.

Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
---
 documentation/ref-manual/system-requirements.rst | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst
index 2e2d0d3..80378ce 100644
--- a/documentation/ref-manual/system-requirements.rst
+++ b/documentation/ref-manual/system-requirements.rst
@@ -277,6 +277,9 @@ resolve this by installing a ``buildtools-extended`` tarball that
 contains additional tools, the equivalent of the Debian/Ubuntu ``build-essential``
 package.
 
+In the sections that follow, three different methods will be described for
+installing the ``buildtools`` or ``buildtools-extended`` toolset.
+
 Installing a Pre-Built ``buildtools`` Tarball with ``install-buildtools`` script
 --------------------------------------------------------------------------------
 
@@ -332,8 +335,9 @@ installer and automatically installs the tools for you:
 Downloading a Pre-Built ``buildtools`` Tarball
 ----------------------------------------------
 
-Downloading and running a pre-built buildtools installer is the easiest
-of the two methods by which you can get these tools:
+If you would prefer not to use the ``install-buildtools`` script, you can instead
+download and run a pre-built buildtools installer yourself with the following
+steps:
 
 1. Locate and download the ``*.sh`` at &YOCTO_RELEASE_DL_URL;/buildtools/
 
-- 
1.8.3.1


  parent reply	other threads:[~2021-04-15  9:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  9:58 [PATCH v2 00/14] Documentation updates for 3.3 Paul Eggleton
2021-04-15  9:58 ` [PATCH v2 01/14] ref-manual: add METADATA_REVISION and METADATA_BRANCH Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 02/14] Use variables for minimum host versions and bump Python to 3.6 Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 03/14] ref-manual: update/fix text for SDK_VERSION Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 04/14] overview-manual: fix git command line Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 05/14] ref-manual: and SDK_CUSTOM_TEMPLATECONF to glossary Paul Eggleton
2021-04-15 10:11   ` [docs] " Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 06/14] ref-manual: add REQUIRED_VERSION and adjust PREFERRED_VERSION entry Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 07/14] ref-manual: add python3targetconfig class and remove python 2 references Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 08/14] ref-manual: add passwd-expire to EXTRA_USERS_PARAMS Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 09/14] ref-manual: add FIT_KERNEL_COMP_ALG* Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 10/14] ref-manual: fix reference to build-essential Paul Eggleton
2021-04-15  9:59 ` Paul Eggleton [this message]
2021-04-15  9:59 ` [PATCH v2 12/14] ref-manual: add migration section for 3.3 release Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 13/14] ref-manual: migration guide: add release codenames Paul Eggleton
2021-04-15  9:59 ` [PATCH v2 14/14] ref-manual: add mention of DISTUTILS_SETUP_PATH Paul Eggleton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2506aa00aae03acf266efcd0a7797f2306791e2.1618480508.git.paul.eggleton@linux.microsoft.com \
    --to=paul.eggleton@linux.microsoft.com \
    --cc=docs@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox