mirror of
https://git.yoctoproject.org/poky
synced 2026-04-22 06:32:12 +02:00
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: 824c075c31650b9b466ac54fdf926043927b7045) Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
This commit is contained in:
committed by
Steve Sakoman
parent
7b6b03a1eb
commit
9e5a9e6f94
@@ -303,8 +303,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
|
||||
--------------------------------------------------------------------------------
|
||||
@@ -339,6 +344,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::
|
||||
|
||||
@@ -373,6 +385,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``
|
||||
@@ -418,6 +434,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
|
||||
@@ -441,6 +461,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``
|
||||
|
||||
Reference in New Issue
Block a user