From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: RE: [yocto] bbappend usage
Date: Mon, 25 Oct 2021 13:24:14 +0000 [thread overview]
Message-ID: <20211025132520.BE621C433F5@smtp.lore.kernel.org> (raw)
In-Reply-To: <08a4cb0-64ab-6dd-b80-d64ee5a219ff@crashcourse.ca>
No, you got it wromg... I have a buildable image which has all the components necessary, I want to remove some overhead installed by some components that I will not be within my running application...
-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf Of Robert P. J. Day
Sent: Monday, October 25, 2021 9:10 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] bbappend usage
External Email Alert
This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.
On Mon, 25 Oct 2021, Monsees, Steven C (US) via lists.yoctoproject.org wrote:
> If I am building an image “image-ABC”, and it is composed of a number
> recipes, and for some of these recipes I may NOT want to install their
> final components within my image…
>
> Which is the best place to modify the build with bbappend ?
>
> Would I modify a recipe’s do_install (do_install_append-recipe_xyz) ?,
> or would I modify the image recipe (do_install_append-image_ABC) I am
> leaning this way to avoid cases where the component recipes might have
> bbappends in place already ?
i would think start with defining a minimal image, then define other images based on that one which add more recipes. this has nothing to do with redefining the recipes, it just means defining more than one image.
rday
next parent reply other threads:[~2021-10-25 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <08a4cb0-64ab-6dd-b80-d64ee5a219ff@crashcourse.ca>
2021-10-25 13:24 ` Monsees, Steven C (US) [this message]
[not found] <MADEUP.16B1474819B9F6FA.19066@lists.yoctoproject.org>
2021-10-25 13:11 ` [yocto] bbappend usage Leon Woestenberg
2021-10-25 13:26 ` Monsees, Steven C (US)
[not found] ` <MADEUP.16B148FB50D2BC13.19066@lists.yoctoproject.org>
2021-10-25 14:03 ` Alexander Kanavin
2021-10-25 13:22 ` Konrad Weihmann
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=20211025132520.BE621C433F5@smtp.lore.kernel.org \
--to=steven.monsees@baesystems.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.