mirror of
https://git.yoctoproject.org/poky
synced 2026-07-15 15:37:03 +00:00
ref-manual: clarify use of "PACKAGE_ARCH" in a packagegroup
Warn the developer that if they need to set "PACKAGE_ARCH" in a custom packagegroup file, that setting must precede the "inherit packagegroup" line in the packagegroup recipe file. (From yocto-docs rev: 9d84e1ccddb2cf17641447721cd2b0b524ef872f) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> (cherry picked from commit 98a14fe885370d52a6f46e940834c725bad6933d) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Paul Barker <paul@pbarker.dev>
This commit is contained in:
committed by
Paul Barker
parent
cee4047ae6
commit
267e62dae3
@@ -2404,6 +2404,18 @@ section in the Yocto Project Development Tasks Manual.
|
||||
|
||||
Previously, this class was called the ``task`` class.
|
||||
|
||||
.. note::
|
||||
|
||||
If you're defining a packagegroup and need to set::
|
||||
|
||||
PACKAGE_ARCH = "${MACHINE_ARCH}"
|
||||
|
||||
for the packagegroup, you need to do that *before* the
|
||||
``inherit packagegroup`` line in the recipe file.
|
||||
Setting it afterward can break BitBake parsing, result in
|
||||
an "allarch" architecture mismatch error, or allow
|
||||
architecture-independent defaults to override your intent.
|
||||
|
||||
.. _ref-classes-patch:
|
||||
|
||||
``patch``
|
||||
|
||||
Reference in New Issue
Block a user