All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Dexuan Cui <dexuan.cui@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] bitbake-layers: stop the warning "not been run using the bitbake wrapper..."
Date: Fri, 10 Jun 2011 13:29:24 +0100	[thread overview]
Message-ID: <1307708964.15712.210.camel@rex> (raw)
In-Reply-To: <6439f6f95ef1157063276692bcf2adfebb7597eb.1307693771.git.dexuan.cui@intel.com>

On Fri, 2011-06-10 at 16:18 +0800, Dexuan Cui wrote:
> Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
> ---
>  bitbake/bin/bitbake-layers |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/bitbake/bin/bitbake-layers b/bitbake/bin/bitbake-layers
> index 6b5ad5a..aa6d031 100755
> --- a/bitbake/bin/bitbake-layers
> +++ b/bitbake/bin/bitbake-layers
> @@ -29,6 +29,10 @@ def main(args):
>      logging.basicConfig(format='%(levelname)s: %(message)s')
>      bb.utils.clean_environment()
>  
> +    # set PSEUDO_BUILD after clean_environment() , or else, the setting will
> +    # be filtered out.
> +    os.environ["PSEUDO_BUILD"] = "0"
> +
>      cmds = Commands()
>      if args:
>          cmds.onecmd(' '.join(args))

We can't add implementation specific information to bitbake I'm afraid
so we'll need to find a different way to handle this...

Cheers,

Richard




  reply	other threads:[~2011-06-10 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10  8:18 [PATCH 0/1] bitbake-layers: stop the warning 'not been run using the bitbake wrapper...' Dexuan Cui
2011-06-10  8:18 ` [PATCH 1/1] bitbake-layers: stop the warning "not been run using the bitbake wrapper..." Dexuan Cui
2011-06-10 12:29   ` Richard Purdie [this message]
2011-06-10 12:45     ` Paul Eggleton
2011-06-20  4:26       ` Cui, Dexuan

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=1307708964.15712.210.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=dexuan.cui@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.