Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>,
	"zhenfeng.zhao@windriver.com" <zhenfeng.zhao@windriver.com>
Subject: Re: [PATCH 2/2] hob2: create a standalone deploy image tool
Date: Wed, 6 Jun 2012 11:29:04 +0800	[thread overview]
Message-ID: <4FCECE80.3090604@windriver.com> (raw)
In-Reply-To: <4FCE40D9.8070107@linux.intel.com>

On 2012年06月06日 01:24, Darren Hart wrote:
>
> On 06/05/2012 01:15 AM, Kang Kai wrote:
>> On 2012年06月05日 15:40, Wang, Shane wrote:
>>> Kang Kai wrote on 2012-06-05:
>>>
>>>> On 2012年06月05日 14:42, Wang, Shane wrote:
>>>>>> -----Original Message-----
>>>>>> From: Kang Kai [mailto:kai.kang@windriver.com]
>>>>>> Sent: Tuesday, June 05, 2012 11:37 AM
>>>>>> To: dvhart@linux.intel.com
>>>>>> Cc: Wang, Shane; zhenfeng.zhao@windriver.com;
>>>>>> bitbake-devel@lists.openembedded.org
>>>>>> Subject: [PATCH 2/2] hob2: create a standalone deploy image tool
>>>>>>
>>>>>> diff --git a/bitbake/lib/bb/ui/crumbs/utils.py
>>>>>> b/bitbake/lib/bb/ui/crumbs/utils.py
>>>>>> index cd01a04..939864f 100644
>>>>>> --- a/bitbake/lib/bb/ui/crumbs/utils.py
>>>>>> +++ b/bitbake/lib/bb/ui/crumbs/utils.py
>>>>>> @@ -22,6 +22,7 @@
>>>>>>     # bitbake which will allow more flexibility.
>>>>>>
>>>>>>     import os
>>>>>> +import bb
>>>>> Why is this needed? I don't see any change you made in utils.py.
>>>>> Is that to say without this line, the functions in utils.py don't work?
>>>> Without the import, it just complains that
>>>>
>>>> NameError: global name 'bb' is not defined
>>>>
>>>> Regards,
>>>> Kai
>>> OK, It seems Saul didn't test it when he created utils.py;-)
>> I am not quit sure because it is fine when call the deploy image in the
>> hob. little weird.
>>
> Probably because another file in the import list includes bb.
>
> However, this change is not specific to the image tool and should be
> broken out as a separate patch. utils.py makes calls to bb.utils.which()
> on the third source line, so bb should certainly be imported in utils.py.

But I import bb in the bitbake-deployimage too. It still complains lack 
of module bb.

Regards,
Kai



>
> --
> Darren
>
>
>> Regards,
>> Kai
>>
>>> --
>>> Shane




  reply	other threads:[~2012-06-06  3:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05  3:37 [PATCH 0/2] hob2: add a standalone deploy image tool Kang Kai
2012-06-05  3:37 ` [PATCH 1/2] hob2: update DeployImageDialog for seperated tool Kang Kai
2012-06-05 17:38   ` Darren Hart
2012-06-06  2:33     ` Kang Kai
2012-06-06  3:01       ` Kang Kai
2012-06-05  3:37 ` [PATCH 2/2] hob2: create a standalone deploy image tool Kang Kai
2012-06-05  6:42   ` Wang, Shane
2012-06-05  7:04     ` Kang Kai
2012-06-05  7:40       ` Wang, Shane
2012-06-05  8:15         ` Kang Kai
2012-06-05 17:24           ` Darren Hart
2012-06-06  3:29             ` Kang Kai [this message]
2012-06-06  5:01               ` Wang, Shane
2012-06-05 17:55   ` Darren Hart

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=4FCECE80.3090604@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=dvhart@linux.intel.com \
    --cc=zhenfeng.zhao@windriver.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