diff options
| author | Paul Eggleton <paul.eggleton@microsoft.com> | 2022-10-10 02:24:03 -0700 |
|---|---|---|
| committer | Steve Sakoman <steve@sakoman.com> | 2024-03-01 05:19:55 -1000 |
| commit | 9e5a9e6f945dae5c3d2e1932449d9494d903cbff (patch) | |
| tree | 0dab60cf02e37df886cc647119f3c420709b8976 /documentation/ref-manual/system-requirements.rst | |
| parent | 7b6b03a1ebb43e737c6feb8700ef679d09302f1d (diff) | |
| download | poky-9e5a9e6f945dae5c3d2e1932449d9494d903cbff.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: 824c075c31650b9b466ac54fdf926043927b7045)
Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'documentation/ref-manual/system-requirements.rst')
| -rw-r--r-- | documentation/ref-manual/system-requirements.rst | 26 |
1 files changed, 25 insertions, 1 deletions
diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst index 92e2211629..e0b8400178 100644 --- a/documentation/ref-manual/system-requirements.rst +++ b/documentation/ref-manual/system-requirements.rst | |||
| @@ -303,8 +303,13 @@ resolve this by installing a ``buildtools-extended`` tarball that | |||
| 303 | contains additional tools, the equivalent of the Debian/Ubuntu ``build-essential`` | 303 | contains additional tools, the equivalent of the Debian/Ubuntu ``build-essential`` |
| 304 | package. | 304 | package. |
| 305 | 305 | ||
| 306 | For systems with a broken make version (e.g. make 4.2.1 without patches) but | ||
| 307 | where the rest of the host tools are usable, you can use the ``buildtools-make`` | ||
| 308 | tarball instead. | ||
| 309 | |||
| 306 | In the sections that follow, three different methods will be described for | 310 | In the sections that follow, three different methods will be described for |
| 307 | installing the ``buildtools`` or ``buildtools-extended`` toolset. | 311 | installing the ``buildtools``, ``buildtools-extended`` or ``buildtools-make`` |
| 312 | toolset. | ||
| 308 | 313 | ||
| 309 | Installing a Pre-Built ``buildtools`` Tarball with ``install-buildtools`` script | 314 | Installing a Pre-Built ``buildtools`` Tarball with ``install-buildtools`` script |
| 310 | -------------------------------------------------------------------------------- | 315 | -------------------------------------------------------------------------------- |
| @@ -339,6 +344,13 @@ installer and automatically installs the tools for you: | |||
| 339 | $ cd poky | 344 | $ cd poky |
| 340 | $ scripts/install-buildtools | 345 | $ scripts/install-buildtools |
| 341 | 346 | ||
| 347 | Alternatively if your host development system has a broken ``make`` | ||
| 348 | version such that you only need a known good version of ``make``, | ||
| 349 | you can use the ``--make-only`` option: | ||
| 350 | |||
| 351 | $ cd poky | ||
| 352 | $ scripts/install-buildtools --make-only | ||
| 353 | |||
| 342 | 2. Source the tools environment setup script by using a command like the | 354 | 2. Source the tools environment setup script by using a command like the |
| 343 | following:: | 355 | following:: |
| 344 | 356 | ||
| @@ -373,6 +385,10 @@ steps: | |||
| 373 | 385 | ||
| 374 | $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh | 386 | $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh |
| 375 | 387 | ||
| 388 | An example for the make-only installer:: | ||
| 389 | |||
| 390 | $ sh ~/Downloads/x86_64-buildtools-make-nativesdk-standalone-&DISTRO;.sh | ||
| 391 | |||
| 376 | During execution, a prompt appears that allows you to choose the | 392 | During execution, a prompt appears that allows you to choose the |
| 377 | installation directory. For example, you could choose the following: | 393 | installation directory. For example, you could choose the following: |
| 378 | ``/home/your-username/buildtools`` | 394 | ``/home/your-username/buildtools`` |
| @@ -418,6 +434,10 @@ installer: | |||
| 418 | 434 | ||
| 419 | $ bitbake buildtools-extended-tarball | 435 | $ bitbake buildtools-extended-tarball |
| 420 | 436 | ||
| 437 | or to build the make-only tarball:: | ||
| 438 | |||
| 439 | $ bitbake buildtools-make-tarball | ||
| 440 | |||
| 421 | .. note:: | 441 | .. note:: |
| 422 | 442 | ||
| 423 | The :term:`SDKMACHINE` variable in your ``local.conf`` file determines | 443 | The :term:`SDKMACHINE` variable in your ``local.conf`` file determines |
| @@ -441,6 +461,10 @@ installer: | |||
| 441 | 461 | ||
| 442 | $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh | 462 | $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh |
| 443 | 463 | ||
| 464 | or for the make-only installer:: | ||
| 465 | |||
| 466 | $ sh ~/Downloads/x86_64-buildtools-make-nativesdk-standalone-&DISTRO;.sh | ||
| 467 | |||
| 444 | During execution, a prompt appears that allows you to choose the | 468 | During execution, a prompt appears that allows you to choose the |
| 445 | installation directory. For example, you could choose the following: | 469 | installation directory. For example, you could choose the following: |
| 446 | ``/home/your_username/buildtools`` | 470 | ``/home/your_username/buildtools`` |
