access to bitbake arguments

access to bitbake arguments

[stefnexter]

[-- Attachment #1: Type: text/plain, Size: 412 bytes --]

Hi,

I hope that this question is suitable for mailing list, if not please suggest a more proper one.
We are using bitbake 1.44

is there a way to get the arguments bitbake were started with during parsing of conf/bitbake.conf  ?

In 1.17 using python sys.argv  worked but with 1.44 I see that the config file is parsed several times, the last time there is no argument other than "decafbad"

//Stef

[-- Attachment #2: Type: text/html, Size: 456 bytes --]

Re: access to bitbake arguments

[stefnexter]

[-- Attachment #1: Type: text/plain, Size: 116 bytes --]

Hi
thanks for the answers, but it sounds it is necessary to rework the ci engine even as it is painful.

//Stef

[-- Attachment #2: Type: text/html, Size: 128 bytes --]

Re: access to bitbake arguments

[stefnexter]

[-- Attachment #1: Type: text/plain, Size: 619 bytes --]

Hi,
What we do is change a environment variable if the recipe name ends with unittest and then

require "conf/${FOO}.conf

Foo could be provided on command line like this

FOO=bar  bitbake something_unittest

and based on recipe name it is either unchanged or appends an "u"

when recipe ends with unittest the resulting FOO should be baru,  variable is also used as override.

I am basically looking list of recipes provided on command line or the dependencies, like pkgs_to_build.

I hope it made sense. It is complicated since we are trying to avoid too big changes to legacy CI engine.

//Stef

[-- Attachment #2: Type: text/html, Size: 931 bytes --]