From: Linus Nilsson <linusnilsson@hotmail.com>
To: Markus Volk <f_l_k@t-online.de>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Sv: [yocto] Correct way for multiple recipes to install files in the same directory
Date: Sat, 13 Apr 2024 10:16:40 +0000 [thread overview]
Message-ID: <GV1P195MB178586BEDD4B820A7BD7D559C80B2@GV1P195MB1785.EURP195.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <S0QUBS.O4LXIGQ2JHXB1@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
As I have no prior experience with classes I'll have to read through the manual to learn and I'll have that in mind, cheers. 🙂
________________________________
Från: Markus Volk <f_l_k@t-online.de>
Skickat: den 13 april 2024 00:48
Till: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>; linusnilsson@hotmail.com <linusnilsson@hotmail.com>
Ämne: Re: [yocto] Correct way for multiple recipes to install files in the same directory
On Fri, Apr 12 2024 at 09:14:45 AM -07:00:00, Linus Nilsson <linusnilsson@hotmail.com> wrote:
I haven't worked with the classes yet but I can see how they can be used to make things a lot easier in my case.
But don't use classen too invasively. They can be problematic, e.g. an :append may be ignored depending on the BBFILE_PRIORITY of a layer
[-- Attachment #2: Type: text/html, Size: 1534 bytes --]
prev parent reply other threads:[~2024-04-13 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 7:52 Correct way for multiple recipes to install files in the same directory linusnilsson
2024-04-11 8:02 ` [yocto] " Markus Volk
2024-04-11 8:45 ` Marko, Peter
2024-04-11 12:37 ` linusnilsson
2024-04-11 14:36 ` linusnilsson
2024-04-11 19:30 ` Marko, Peter
2024-04-12 6:07 ` linusnilsson
2024-04-12 16:14 ` Linus Nilsson
2024-04-12 22:48 ` Markus Volk
2024-04-13 10:16 ` Linus Nilsson [this message]
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=GV1P195MB178586BEDD4B820A7BD7D559C80B2@GV1P195MB1785.EURP195.PROD.OUTLOOK.COM \
--to=linusnilsson@hotmail.com \
--cc=f_l_k@t-online.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).