From: "Altous, Salahaldeen" <Salahaldeen.Altous@leica-camera.com>
To: "Alexander Kanavin" <alex.kanavin@gmail.com>,
yocto@lists.yoctoproject.org
Subject: Re: [yocto] Yocto common place holder for includes which used multiple recipe
Date: Tue, 23 Apr 2024 06:06:38 -0700 [thread overview]
Message-ID: <14877.1713877598189993473@lists.yoctoproject.org> (raw)
In-Reply-To: <CANNYZj_o623xZpW+RwS__VAP1Weu=gWnorX38ZghkhEsWm54Qw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2193 bytes --]
On Tue, Apr 23, 2024 at 05:27 AM, Alexander Kanavin wrote:
>
> Yes this should be fine. But don't forget to inherit it in all the
> recipes that would use these variables.
>
> Here's an example:
> https://git.yoctoproject.org/poky/tree/meta/classes-recipe/gnomebase.bbclass
>
Thanks I will give a try
>
>
> Alex
>
> On Tue, 23 Apr 2024 at 14:19, Altous, Salahaldeen via
> Lists.Yoctoproject.Org
> <Salahaldeen.Altous=leica-camera.com@lists.yoctoproject.org> wrote:
>
>> Hi Alex
>>
>> thanks for your quick reply.
>>
>> On Tue, Apr 23, 2024 at 05:02 AM, Alexander Kanavin wrote:
>>
>> 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.
>>
>> I need something like these these variables
>>
>> EXTERNAL_PROJECT_XXX_TYPE ?= "lib"
>> EXTERNAL_PROJECT_XXX_NAME ?= "lc_xxx"
>> EXTERNAL_PROJECT_XXX_GIT_URI ?=
>> "${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
>> EXTERNAL_PROJECT_XXX_GIT_BRANCH ?= "development"
>> EXTERNAL_PROJECT_XXX_GIT_TAG ?= "0.4.3-dev"
>>
>> EXTERNAL_PROJECT_YYY_TYPE ?= "lib"
>> EXTERNAL_PROJECT_YYY_NAME ?= "lc-yyy"
>> EXTERNAL_PROJECT_XXX_GIT_URI ?=
>> "${COMPANY_GIT_REPO}:test/independent-modules/lc_xxx.git"
>> EXTERNAL_PROJECT_YYY_GIT_BRANCH ?= "development"
>> EXTERNAL_PROJECT_YYY_GIT_TAG ?= "0.2.1-dev"
>>
>> is this something possible with bbclass?
>>
>> Salahaldeen
>>
>>
>> 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
>
>
Thanks I will give a try
[-- Attachment #2: Type: text/html, Size: 2436 bytes --]
prev parent reply other threads:[~2024-04-23 13:06 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 ` [yocto] " Alexander Kanavin
2024-04-23 12:19 ` Altous, Salahaldeen
2024-04-23 12:26 ` Alexander Kanavin
2024-04-23 13:06 ` Altous, Salahaldeen [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=14877.1713877598189993473@lists.yoctoproject.org \
--to=salahaldeen.altous@leica-camera.com \
--cc=alex.kanavin@gmail.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).