From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Automatic -dbg FILES generation
Date: Tue, 15 Dec 2015 15:43:31 +0000 [thread overview]
Message-ID: <1450194211.13505.63.camel@linuxfoundation.org> (raw)
I don't think I'm alone in being a bit frustrated with the effort
needed to get FILES_${PN}-dbg correct. I've just posted a patch to oe
-core which automates this and means we can drop 99% of the cases where
we set this variable.
I'm giving a heads up here since this is an architectural change to the
way the system works and wanted people to be aware of it. I'm hoping it
will be welcomed and not too controversial.
Setting FILES_${PN}-dbg doesn't harm anything, it just becomes
unnecessary in most cases.
Cheers,
Richard
next reply other threads:[~2015-12-15 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 15:43 Richard Purdie [this message]
2015-12-15 18:44 ` [Openembedded-architecture] Automatic -dbg FILES generation Christopher Larson
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=1450194211.13505.63.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.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