($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Paulo Neves <paulo@myneves.com>
To: Vasyl Vavrychuk <vvavrychuk@gmail.com>,
	bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] how to appendVar via Tinfoil API
Date: Mon, 15 Jan 2024 11:57:22 +0000	[thread overview]
Message-ID: <18a82940-55ce-48d0-841b-754b736839b3@myneves.com> (raw)
In-Reply-To: <rjF5.1704750728530444364.AHOb@lists.openembedded.org>

Hello Vasyl,

The way I did in the past is to create a conf file that is injected to 
bitbake by making the script set os.environ["BBPOSTCONF"] = "<my special 
conf>"

This will then be picked up by 
https://github.com/openembedded/bitbake/blob/966f25dfc23a6d17b2b6d3e0100e9ae264f99025/lib/bb/main.py#L328

Another way, I haven't tested is that your default configuration 
includes a variable that is normally unset and then in tinfoil.prepare 
you pass config_params argument as in 
https://github.com/openembedded/bitbake/blob/966f25dfc23a6d17b2b6d3e0100e9ae264f99025/lib/bb/tinfoil.py#L364

For example

BB_MULTI_PROVIDER_ALLOWED += "A B ${EXTRA_MULTIPROVIDER_ALLOWED}"

and then tinfoil.prepare(self, config_only=False, 
config_params={EXTRA_MULTIPROVIDER_ALLOWED: "C"}, quiet=0, 
extra_features=None):

Cheers

Paulo Neves

On 08/01/2024 22:52, Vasyl Vavrychuk wrote:
> I would like temporary appendVar before parsing recipes via Tinfoil 
> API. Specifically, I want to do using Tinfoil API:
>
> BB_MULTI_PROVIDER_ALLOWED += "..."
>
> and then call Tinfoil API to get all providers including skipped one.
>
> Can I do appendVar using Tinfoil? 



      reply	other threads:[~2024-01-15 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 21:52 how to appendVar via Tinfoil API Vasyl Vavrychuk
2024-01-15 11:57 ` Paulo Neves [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=18a82940-55ce-48d0-841b-754b736839b3@myneves.com \
    --to=paulo@myneves.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=vvavrychuk@gmail.com \
    /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).