From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH] ref-manual: document DEBUG_PREFIX_MAP
Date: Tue, 5 Oct 2021 18:04:07 +0200 [thread overview]
Message-ID: <20211005160407.899144-1-michael.opdenacker@bootlin.com> (raw)
Fixes [YOCTO #14433]
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/variables.rst | 17 +++++++++++++++++
.../test-manual/reproducible-builds.rst | 2 +-
2 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 5f6f91146b..b83e9f8511 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -1582,6 +1582,23 @@ system and gives an overview of their function and contents.
by :term:`BBFILE_PRIORITY` if that variable is different between two
layers that contain different versions of the same recipe.
+ :term:`DEBUG_PREFIX_MAP`
+ Allows to set C compiler options, such as ``-fdebug-prefix-map``,
+ ``-fmacro-prefix-map``, and ``-ffile-prefix-map``, which allow to
+ replace build-time paths by install-time ones in the debugging sections
+ of binaries. This makes compiler output files location independent,
+ at the cost of having to pass an extra command to tell the debugger
+ where source files are.
+
+ This is used by the Yocto Project to guarantee
+ :doc:`/test-manual/reproducible-builds` even when the source code of
+ a package uses the ``__FILE__`` or ``assert()`` macros. See the
+ `reproducible-builds.org <https://reproducible-builds.org/docs/build-path/>`__
+ website for details.
+
+ This variable is set in the ``meta/conf/bitbake.conf`` file. It is
+ not intended to be user-configurable.
+
:term:`DEFAULTTUNE`
The default CPU and Application Binary Interface (ABI) tunings (i.e.
the "tune") used by the OpenEmbedded build system. The
diff --git a/documentation/test-manual/reproducible-builds.rst b/documentation/test-manual/reproducible-builds.rst
index 68fdf547bd..349cd1953e 100644
--- a/documentation/test-manual/reproducible-builds.rst
+++ b/documentation/test-manual/reproducible-builds.rst
@@ -53,7 +53,7 @@ things we do within the build system to ensure reproducibility include:
- Adding mappings to the compiler options to ensure debug filepaths are mapped
to consistent target compatible paths. This is done through the
- ``DEBUG_PREFIX_MAP`` variable which sets the ``-fmacro-prefix-map`` and
+ :term:`DEBUG_PREFIX_MAP` variable which sets the ``-fmacro-prefix-map`` and
``-fdebug-prefix-map`` compiler options correctly to map to target paths.
- Being explicit about recipe dependencies and their configuration (no floating
configure options or host dependencies creeping in). In particular this means
--
2.25.1
reply other threads:[~2021-10-05 16:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211005160407.899144-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox