Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: "Wang, Shane" <shane.wang@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: Tue, 5 Jun 2012 15:04:41 +0800	[thread overview]
Message-ID: <4FCDAF89.8000803@windriver.com> (raw)
In-Reply-To: <3AB6CE7F274E534CAFD089D127A8A1FC23BCA57C@SHSMSX102.ccr.corp.intel.com>

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
>>
>> [Yocto 2388]
>>
>> Create a standalone deploy image tool using the existing dialog
>> including DeployImageDialog and ImageSelectionDialog.
>>
>> Duplicate the gtk and pygtk versions check in the hob.py because this
>> will be run separately.
>>
>> Update ui/crumbs/utils.py that it needs to 'import bb' when run this
>> tool.
>>
>> Signed-off-by: Kang Kai<kai.kang@windriver.com>
>> ---
>>   bitbake/bin/bitbake-deployimage   |  135
>> +++++++++++++++++++++++++++++++++++++
>>   bitbake/lib/bb/ui/crumbs/utils.py |    1 +
>>   2 files changed, 136 insertions(+), 0 deletions(-)
>>   create mode 100755 bitbake/bin/bitbake-deployimage
>>
>> diff --git a/bitbake/bin/bitbake-deployimage
>> b/bitbake/bin/bitbake-deployimage
>> new file mode 100755
>> index 0000000..8fdd21b
>> --- /dev/null
>> +++ b/bitbake/bin/bitbake-deployimage
>> @@ -0,0 +1,135 @@
>> +#!/usr/bin/python
>> +
>> +
>> +requirements = "FATAL: Gtk+ 2.20.0 or higher, PyGtk version 2.22.0 or higher
>> and PyGobject are required to use Hob"

Hi Shane,

> Kai, I don't like you have this kind of limitation for GTK and PyGTK.
> Hob.py does have because we want special efforts on the visual components. For this simple app,
> I don't want you to exclude a lot of users who only have lower versions.

Fine, I'll remove the version check.

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

>
>>   def which_terminal():
>>       term = bb.utils.which(os.environ["PATH"], "xterm")
>> --
>> 1.7.5.4
>




  reply	other threads:[~2012-06-05  7:14 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 [this message]
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
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=4FCDAF89.8000803@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=shane.wang@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