From 0079a0464452fac031794a56a1178c4c1c04b1e0 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Wed, 28 Oct 2020 11:29:10 +0000 Subject: ref-manual/faq: Add entry for why binaries are changed in images (From yocto-docs rev: 843a91187783b2e11512c45b8dd8302b19113569) Signed-off-by: Richard Purdie --- documentation/ref-manual/faq.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'documentation/ref-manual') diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst index 7a1614028a..8c2b34be5f 100644 --- a/documentation/ref-manual/faq.rst +++ b/documentation/ref-manual/faq.rst @@ -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 environment variable. Check the the build system to see if these kinds 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. -- cgit v1.2.3-54-g00ecf