mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-01-29 21:08:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

manuals: add missing references to SDKMACHINE and SDK_ARCH

Browse Source 
Doing this, fix the odd identation of the corresponding paragraphs

(From yocto-docs rev: e319b3bf4eb6420949372e699d60c7383945e513)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker
2022-10-27 15:24:15 +02:00
committed by Richard Purdie
parent 6f4ccc4dad
commit 50458d9238
3 changed files with 14 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
documentation/overview-manual/concepts.rst
View File

@@ -1482,12 +1482,11 @@ relocatable SDK used to develop applications. When you run the
installer, it installs the toolchain, which contains the development
tools (e.g., ``gcc-cross-canadian``, ``binutils-cross-canadian``, and
other ``nativesdk-*`` tools), which are tools native to the SDK (i.e.
native to :term:`SDK_ARCH`), you
need to cross-compile and test your software. The figure shows the
commands you use to easily build out this toolchain. This
cross-development toolchain is built to execute on the
:term:`SDKMACHINE`, which might or
might not be the same machine as the Build Host.
native to :term:`SDK_ARCH`), you need to cross-compile and test your
software. The figure shows the commands you use to easily build out
this toolchain. This cross-development toolchain is built to execute on the
:term:`SDKMACHINE`, which might or might not be the same machine as
the Build Host.
.. note::

17
documentation/sdk-manual/appendix-obtain.rst
View File

@@ -132,22 +132,21 @@ build the SDK installer. Follow these steps:
5. *Make Sure Your SDK Machine is Correctly Set:* If you are building a
toolchain designed to run on an architecture that differs from your
current development host machine (i.e. the build host), be sure that
the :term:`SDKMACHINE` variable
in the ``local.conf`` file in your Build Directory is correctly set.
the :term:`SDKMACHINE` variable in the ``local.conf`` file in your
Build Directory is correctly set.
.. note::
If you are building an SDK installer for the Extensible SDK, the
SDKMACHINE
value must be set for the architecture of the machine you are
using to build the installer. If
SDKMACHINE
:term:`SDKMACHINE` value must be set for the architecture of the
machine you are using to build the installer. If :term:`SDKMACHINE`
is not set appropriately, the build fails and provides an error
message similar to the following::
The extensible SDK can currently only be built for the same architecture as the machine being built on - SDK_ARCH is
set to i686 (likely via setting SDKMACHINE) which is different from the architecture of the build machine (x86_64).
Unable to continue.
The extensible SDK can currently only be built for the same
architecture as the machine being built on --- :term:`SDK_ARCH`
is set to ``i686`` (likely via setting :term:`SDKMACHINE`) which is
different from the architecture of the build machine (``x86_64``).
6. *Build the SDK Installer:* To build the SDK installer for a standard

2
documentation/test-manual/understand-autobuilder.rst
View File

@@ -56,7 +56,7 @@ the "templates" section, which looks like::
Combining these two entries you can see that "qemux86-64" is a three step build where the
``bitbake BBTARGETS`` would be run, then ``bitbake SANITYTARGETS`` for each step; all for
``MACHINE="qemux86-64"`` but with differing SDKMACHINE settings. In step
``MACHINE="qemux86-64"`` but with differing :term:`SDKMACHINE` settings. In step
1 an extra variable is added to the ``auto.conf`` file to enable wic
image generation.