From: Alexander Kanavin <alex.kanavin@gmail.com>
To: yocto@lists.yoctoproject.org, Salahaldeen.Altous@leica-camera.com
Subject: Re: [yocto] Yocto common place holder for includes which used multiple recipe
Date: Tue, 23 Apr 2024 14:02:32 +0200 [thread overview]
Message-ID: <CANNYZj8KMPiz3kKT-XNwc1pEDDFp85aem6fMbQ_b9S=ZASfwvA@mail.gmail.com> (raw)
In-Reply-To: <COpS.1713873449234365047.hDTV@lists.yoctoproject.org>
I think you can simply make it a class and put under
classes/some.bbclass? Plenty of recipes in oe-core do this, see e.g.
gnomebase.bbclass.
Alex
On Tue, 23 Apr 2024 at 13:57, Altous, Salahaldeen via
lists.yoctoproject.org
<Salahaldeen.Altous=leica-camera.com@lists.yoctoproject.org> wrote:
>
> Hi All,
>
> I need a common place holder to share one include files which can be used by multiple recipe (this include files includes some variables like SRC_URL, tag, gitbranch, ..., etc).
>
> I can copy it to each recipe but I am looking for the best practice to share a common inc file for all recipes in meta-xxx which can be found by default and this need to be under meta-xxx folder.
>
> thanks in advance.
>
>
>
> Regards,
>
> Salahaldeen Altous
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#62985): https://lists.yoctoproject.org/g/yocto/message/62985
> Mute This Topic: https://lists.yoctoproject.org/mt/105687839/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2024-04-23 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 11:57 Yocto common place holder for includes which used multiple recipe Altous, Salahaldeen
2024-04-23 12:02 ` Alexander Kanavin [this message]
2024-04-23 12:19 ` [yocto] " Altous, Salahaldeen
2024-04-23 12:26 ` Alexander Kanavin
2024-04-23 13:06 ` Altous, Salahaldeen
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='CANNYZj8KMPiz3kKT-XNwc1pEDDFp85aem6fMbQ_b9S=ZASfwvA@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=Salahaldeen.Altous@leica-camera.com \
--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).