From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: "OE Core (openembedded-core@lists.openembedded.org)"
<openembedded-core@lists.openembedded.org>
Subject: How to build a devupstream variant of a recipe?
Date: Wed, 25 Aug 2021 13:51:34 +0000 [thread overview]
Message-ID: <68ca10644e1b4a59b4888b72feb571d8@axis.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
As I was recently looking at lttng-modules, which supports devupstream, I wanted to try to build the devupstream variant. However, neither the information in devupstream.bbclass nor the documentation in the manual were of any help. Since it uses the BBCLASSEXTEND mechanism, I thought it would be as simple as doing `bitbake lttng-modules-devupstream`, but that did not work. So what is the correct way to build a devupstream variant of a recipe?
//Peter
[-- Attachment #2: Type: text/html, Size: 1111 bytes --]
next reply other threads:[~2021-08-25 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 13:51 Peter Kjellerstedt [this message]
2021-08-25 14:00 ` [OE-core] How to build a devupstream variant of a recipe? Bruce Ashfield
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=68ca10644e1b4a59b4888b72feb571d8@axis.com \
--to=peter.kjellerstedt@axis.com \
--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