From: ChenQi <Qi.Chen@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 1/7] scripts/oe-setup-builddir: add a check that TEMPLATECONF is valid
Date: Wed, 14 Sep 2022 16:17:38 +0800 [thread overview]
Message-ID: <8f083713-d00a-2393-3b74-35491e830bb0@windriver.com> (raw)
In-Reply-To: <CANNYZj8owg_f1=g6VWVo-S6Qhq8VOgeYiGwQgNYQ5-GmbP8OTQ@mail.gmail.com>
On 9/14/22 16:03, Alexander Kanavin wrote:
> On Wed, 14 Sept 2022 at 09:42, ChenQi <Qi.Chen@windriver.com> wrote:
>
>> Yes. The bblayers.conf.sample is generated dynamically according to
>> project setup.
> Can we step back for a moment, I'd like to know more about how you do
> this. Is the code that does dynamic generation of the list in bblayers
> published somewhere? How a decision to include (or not) a layer is
> made?
>
> Alex
The codes are in: https://github.com/WindRiver-Labs/wrlinux-x
e.g.
./wrlinux-x/setup.sh --all-layers (this pulls down all supported layers)
./wrlinux-x/setup.sh --all-layers --dl-layers (this pulls down all
supported layers, together with their needed tarballs/git repos)
./wrlinux-x/setup.sh (this pulls down the default list of layers)
./wrlinux-x/setup.sh --layers meta-xxx (this pulls down the default list
of layers + meta-xxx and its dependencies)
And the final list of layers are in
<project_dir>/config/bblayers.conf.sample, which will be updated if
needed when re-running the setup.sh script.
Regards,
Qi
next prev parent reply other threads:[~2022-09-14 8:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 11:13 [PATCH 1/7] scripts/oe-setup-builddir: add a check that TEMPLATECONF is valid Alexander Kanavin
2022-08-31 11:13 ` [PATCH 2/7] bitbake-layers: add a command to save the active build configuration as a template into a layer Alexander Kanavin
2022-08-31 11:13 ` [PATCH 3/7] meta/files: add layer setup JSON schema and example Alexander Kanavin
2022-08-31 11:13 ` [PATCH 4/7] bitbake-layers: add ability to save current layer repository configuration into a file Alexander Kanavin
2022-08-31 11:13 ` [PATCH 5/7] scripts/oe-setup-layers: add a script that restores the layer configuration from a json file Alexander Kanavin
2022-08-31 11:14 ` [PATCH 6/7] selftest/bblayers: add a test for creating a layer setup and using it to restore the layers Alexander Kanavin
2022-08-31 11:14 ` [PATCH 7/7] selftest/bblayers: adjust the revision for the layer setup test Alexander Kanavin
2022-09-14 3:27 ` [OE-core] [PATCH 1/7] scripts/oe-setup-builddir: add a check that TEMPLATECONF is valid ChenQi
2022-09-14 5:00 ` Alexander Kanavin
2022-09-14 5:49 ` ChenQi
2022-09-14 6:39 ` Alexander Kanavin
2022-09-14 7:42 ` ChenQi
2022-09-14 8:03 ` Alexander Kanavin
2022-09-14 8:17 ` ChenQi [this message]
2022-09-14 8:42 ` Alexander Kanavin
2022-09-15 1:07 ` Peter Kjellerstedt
2022-09-15 9:20 ` Alexander Kanavin
2022-09-15 22:59 ` Peter Kjellerstedt
2022-09-16 10:57 ` Alexander Kanavin
2022-09-17 0:06 ` Peter Kjellerstedt
2022-09-17 8:17 ` Alexander Kanavin
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=8f083713-d00a-2393-3b74-35491e830bb0@windriver.com \
--to=qi.chen@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--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