[PATCH 0/1] bitbake-layers: stop the warning 'not been run using the bitbake wrapper...'

[PATCH 0/1] bitbake-layers: stop the warning 'not been run using the bitbake wrapper...'

[Dexuan Cui]

Please review the patch.

The following changes since commit 1b53eef2769d1b5e4ff527ccabf9b700afc02220:

  native/nativesdk: Clean up the depends ordering after bitbake override handling updates (2011-06-09 22:49:10 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib dcui/bb
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dcui/bb

Dexuan Cui (1):
  bitbake-layers: stop the warning "not been run using the bitbake
    wrapper..."

 bitbake/bin/bitbake-layers |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

-- 
1.7.2

[PATCH 1/1] bitbake-layers: stop the warning "not been run using the bitbake wrapper..."

[Dexuan Cui]

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))
-- 
1.7.2

Re: [PATCH 1/1] bitbake-layers: stop the warning "not been run using the bitbake wrapper..."

[Richard Purdie]

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

Re: [PATCH 1/1] bitbake-layers: stop the warning "not been run using the bitbake wrapper..."

[Paul Eggleton]

On Friday 10 June 2011 13:29:24 Richard Purdie wrote:
> We can't add implementation specific information to bitbake I'm afraid
> so we'll need to find a different way to handle this...

Perhaps we could just change sanity.bbclass to check argv[0] somehow (or some 
equivalent way to get the current process name) and skip the check if it isn't 
"bitbake"? This would have the added bonus of solving the problem for future 
tools that use bitbake code in a similar way to bitbake-layers.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: [PATCH 1/1] bitbake-layers: stop the warning "not been run using the bitbake wrapper..."

[Cui, Dexuan]

Paul Eggleton wrote:
> On Friday 10 June 2011 13:29:24 Richard Purdie wrote:
>> We can't add implementation specific information to bitbake I'm
>> afraid so we'll need to find a different way to handle this...
> 
> Perhaps we could just change sanity.bbclass to check argv[0] somehow
> (or some equivalent way to get the current process name) and skip the
> check if it isn't "bitbake"? This would have the added bonus of
> solving the problem for future tools that use bitbake code in a
> similar way to bitbake-layers. 
(sorry for the late reply!) 
Thanks a lot for Paul's good suggestion!
I sent the new patch to oe-core mailing list just now.

Thanks,
-- Dexuan