From: Peter Kjellerstedt <pkj@axis.com>
To: <docs@lists.yoctoproject.org>
Subject: [PATCHv3] ref-manual: Add documentation of PACKAGE_DEBUG_FILE_SUFFIX
Date: Fri, 7 Jan 2022 18:04:33 +0100 [thread overview]
Message-ID: <20220107170433.1958-1-pkj@axis.com> (raw)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
---
PATCHv2: Removed the reference to split_and_strip_files().
PATCHv3: Changed "dbg package" to "``-dbg`` package".
documentation/ref-manual/variables.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index e81a12030a..aaba23dbdf 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -5085,6 +5085,14 @@ system and gives an overview of their function and contents.
result of the package manager in use, see the
":ref:`package.bbclass <ref-classes-package>`" section.
+ :term:`PACKAGE_DEBUG_FILE_SUFFIX`
+ This suffix is added to the names of all files with debug symbols that go
+ into the ``-dbg`` package. It can be used to make the debug files produced
+ by one recipe unique to avoid them conflicting with identically named
+ debug files produced by another recipe. This may be needed since while the
+ target files may be split in multiple packages, the debug files for one
+ recipe are all in one package.
+
:term:`PACKAGE_DEBUG_SPLIT_STYLE`
Determines how to split up and package debug and source information
when creating debugging packages to be used with the GNU Project
next reply other threads:[~2022-01-07 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 17:04 Peter Kjellerstedt [this message]
2022-01-10 14:39 ` [docs] [PATCHv3] ref-manual: Add documentation of PACKAGE_DEBUG_FILE_SUFFIX Michael Opdenacker
2022-01-10 14:52 ` Peter Kjellerstedt
2022-01-10 15:18 ` Michael Opdenacker
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=20220107170433.1958-1-pkj@axis.com \
--to=pkj@axis.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