mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-08 05:09:24 +00:00
Code Issues Projects Releases Wiki Activity

ref-manual: add info on buildtools-make-tarball

Browse Source 
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>
This commit is contained in:
Paul Eggleton
2022-10-10 02:24:03 -07:00
committed by Richard Purdie
parent 67a48d05cf
commit 20cf9c46a1
1 changed files with 25 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/ref-manual/system-requirements.rst
+25 -1
View File
@@ -220,8 +220,13 @@ resolve this by installing a ``buildtools-extended`` tarball that
contains additional tools, the equivalent of the Debian/Ubuntu ``build-essential``
package.
For systems with a broken make version (e.g. make 4.2.1 without patches) but
where the rest of the host tools are usable, you can use the ``buildtools-make``
tarball instead.
In the sections that follow, three different methods will be described for
installing the ``buildtools`` or ``buildtools-extended`` toolset.
installing the ``buildtools``, ``buildtools-extended`` or ``buildtools-make``
toolset.
Installing a Pre-Built ``buildtools`` Tarball with ``install-buildtools`` script
--------------------------------------------------------------------------------
@@ -256,6 +261,13 @@ installer and automatically installs the tools for you:
$ cd poky
$ scripts/install-buildtools
Alternatively if your host development system has a broken ``make``
version such that you only need a known good version of ``make``,
you can use the ``--make-only`` option:
$ cd poky
$ scripts/install-buildtools --make-only
2. Source the tools environment setup script by using a command like the
following::
@@ -290,6 +302,10 @@ steps:
$ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh
An example for the make-only installer::
$ sh ~/Downloads/x86_64-buildtools-make-nativesdk-standalone-&DISTRO;.sh
During execution, a prompt appears that allows you to choose the
installation directory. For example, you could choose the following:
``/home/your-username/buildtools``
@@ -335,6 +351,10 @@ installer:
$ bitbake buildtools-extended-tarball
or to build the make-only tarball::
$ bitbake buildtools-make-tarball
.. note::
The :term:`SDKMACHINE` variable in your ``local.conf`` file determines
@@ -358,6 +378,10 @@ installer:
$ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh
or for the make-only installer::
$ sh ~/Downloads/x86_64-buildtools-make-nativesdk-standalone-&DISTRO;.sh
During execution, a prompt appears that allows you to choose the
installation directory. For example, you could choose the following:
``/home/your_username/buildtools``