ref-manual/faq: Add entry for why binaries are changed in images

(From yocto-docs rev: 33915ef51d0661c4dc76c572456a10a54fba960b)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 843a91187783b2e11512c45b8dd8302b19113569)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Richard Purdie
2020-10-28 11:29:10 +00:00
parent b591dcd33e
commit bc491d6956

View File

@@ -451,3 +451,14 @@ variant. For another example, permissions errors might be caused by a
Makefile that ignores ``DESTDIR`` or uses a different name for that Makefile that ignores ``DESTDIR`` or uses a different name for that
environment variable. Check the the build system to see if these kinds environment variable. Check the the build system to see if these kinds
of issues exist. of issues exist.
**Q:** I'm adding a binary in a recipe but it's different in the image, what is
changing it?
**A:** The first most obvious change is the system stripping debug symbols from
it. Setting :term:`INHIBIT_PACKAGE_STRIP` to stop debug symbols being stripped and/or
:term:`INHIBIT_PACKAGE_DEBUG_SPLIT` to stop debug symbols being split into a separate
file will ensure the binary is unchanged. The other less obvious thing that can
happen is prelinking of the image. This is set by default in local.conf via
:term:`USER_CLASSES` which can contain 'image-prelink'. If you remove that, the
image will not be prelinked meaning the binaries would be unchanged.