public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2 3/4] buildstats: Manage buildstats via USER_CLASSES variable
Date: Tue, 5 Oct 2021 11:21:21 +0200	[thread overview]
Message-ID: <20211005112121.3f994cb7@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20210927141705.25386-4-ubely@ilbers.de>

Am Mon, 27 Sep 2021 16:17:04 +0200
schrieb Uladzimir Bely <ubely@ilbers.de>:

> Such variable is used in OE, so this patch makes buildstat usage
> similar to OE/Poky.
> 
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
>  meta-isar/conf/local.conf.sample | 2 ++
>  meta/conf/bitbake.conf           | 2 ++
>  2 files changed, 4 insertions(+)
> 
> diff --git a/meta-isar/conf/local.conf.sample
> b/meta-isar/conf/local.conf.sample index 88a8175..3f806e2 100644
> --- a/meta-isar/conf/local.conf.sample
> +++ b/meta-isar/conf/local.conf.sample
> @@ -222,5 +222,7 @@ USER_isar[flags] = "system create-home"
>  USER_isar[password] = "isar"
>  USER_isar[flags] += "clear-text-password"
>  
> +USER_CLASSES ?= "buildstats"

Is that the name that OE uses? I find it a bit confusing coming right
after the other USER_ bits, which have a totally different context.

Maybe rename, reorder or add a comment.

Henning

> +
>  # Uncomment the below line to debug WIC.
>  # WIC_CREATE_EXTRA_ARGS += "-D"
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 7f5901d..51af5ca 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -120,4 +120,6 @@ include conf/multiconfig/${BB_CURRENT_MC}.conf
>  include conf/machine/${MACHINE}.conf
>  include conf/distro/${DISTRO}.conf
>  
> +INHERIT += "${USER_CLASSES}"
> +
>  PATCHRESOLVE ?= "noop"


  reply	other threads:[~2021-10-05  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 14:17 [PATCH v2 0/4] Use buildstats from OE to generate build charts Uladzimir Bely
2021-09-27 14:17 ` [PATCH v2 1/4] buildstats: Borrow buildstats and pybootchartgui from OE Uladzimir Bely
2021-10-05  9:13   ` Henning Schild
2021-09-27 14:17 ` [PATCH v2 2/4] buildstats: Fix bbclass to work with ISAR Uladzimir Bely
2021-10-05  9:19   ` Henning Schild
2021-09-27 14:17 ` [PATCH v2 3/4] buildstats: Manage buildstats via USER_CLASSES variable Uladzimir Bely
2021-10-05  9:21   ` Henning Schild [this message]
2021-09-27 14:17 ` [PATCH v2 4/4] doc: Add buildstats section in user manual Uladzimir Bely

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=20211005112121.3f994cb7@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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