summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@microsoft.com>2022-10-10 02:24:03 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-10-28 15:48:03 +0100
commit20cf9c46a1ef298c434c57ae23b15fc434a922cb (patch)
tree0698db2b71ce0b8e8709817f46f2223793e66856 /documentation
parent67a48d05cf5b139e005a5c3b71f04548771e309e (diff)
downloadpoky-20cf9c46a1ef298c434c57ae23b15fc434a922cb.tar.gz
ref-manual: add info on buildtools-make-tarball
PENDING ON THIS OE-CORE PATCH: install-buildtools: support buildtools-make-tarball and update to 4.1 https://lists.openembedded.org/g/openembedded-core/message/171522 Cover the use case and the new provided tarball. (From yocto-docs rev: 3a06c35d059d7d43f7eb33a4f490f5d76afe6cb6) Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/ref-manual/system-requirements.rst26
1 files changed, 25 insertions, 1 deletions
diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst
index 2a6d444040..1502633816 100644
--- a/documentation/ref-manual/system-requirements.rst
+++ b/documentation/ref-manual/system-requirements.rst
@@ -220,8 +220,13 @@ resolve this by installing a ``buildtools-extended`` tarball that
220contains additional tools, the equivalent of the Debian/Ubuntu ``build-essential`` 220contains additional tools, the equivalent of the Debian/Ubuntu ``build-essential``
221package. 221package.
222 222
223For systems with a broken make version (e.g. make 4.2.1 without patches) but
224where the rest of the host tools are usable, you can use the ``buildtools-make``
225tarball instead.
226
223In the sections that follow, three different methods will be described for 227In the sections that follow, three different methods will be described for
224installing the ``buildtools`` or ``buildtools-extended`` toolset. 228installing the ``buildtools``, ``buildtools-extended`` or ``buildtools-make``
229toolset.
225 230
226Installing a Pre-Built ``buildtools`` Tarball with ``install-buildtools`` script 231Installing a Pre-Built ``buildtools`` Tarball with ``install-buildtools`` script
227-------------------------------------------------------------------------------- 232--------------------------------------------------------------------------------
@@ -256,6 +261,13 @@ installer and automatically installs the tools for you:
256 $ cd poky 261 $ cd poky
257 $ scripts/install-buildtools 262 $ scripts/install-buildtools
258 263
264 Alternatively if your host development system has a broken ``make``
265 version such that you only need a known good version of ``make``,
266 you can use the ``--make-only`` option:
267
268 $ cd poky
269 $ scripts/install-buildtools --make-only
270
2592. Source the tools environment setup script by using a command like the 2712. Source the tools environment setup script by using a command like the
260 following:: 272 following::
261 273
@@ -290,6 +302,10 @@ steps:
290 302
291 $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh 303 $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh
292 304
305 An example for the make-only installer::
306
307 $ sh ~/Downloads/x86_64-buildtools-make-nativesdk-standalone-&DISTRO;.sh
308
293 During execution, a prompt appears that allows you to choose the 309 During execution, a prompt appears that allows you to choose the
294 installation directory. For example, you could choose the following: 310 installation directory. For example, you could choose the following:
295 ``/home/your-username/buildtools`` 311 ``/home/your-username/buildtools``
@@ -335,6 +351,10 @@ installer:
335 351
336 $ bitbake buildtools-extended-tarball 352 $ bitbake buildtools-extended-tarball
337 353
354 or to build the make-only tarball::
355
356 $ bitbake buildtools-make-tarball
357
338 .. note:: 358 .. note::
339 359
340 The :term:`SDKMACHINE` variable in your ``local.conf`` file determines 360 The :term:`SDKMACHINE` variable in your ``local.conf`` file determines
@@ -358,6 +378,10 @@ installer:
358 378
359 $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh 379 $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh
360 380
381 or for the make-only installer::
382
383 $ sh ~/Downloads/x86_64-buildtools-make-nativesdk-standalone-&DISTRO;.sh
384
361 During execution, a prompt appears that allows you to choose the 385 During execution, a prompt appears that allows you to choose the
362 installation directory. For example, you could choose the following: 386 installation directory. For example, you could choose the following:
363 ``/home/your_username/buildtools`` 387 ``/home/your_username/buildtools``