[bitbake-devel] 答复: hob2: make xterm automatically exit after qemu exits?

[Lu, Lianhao]

I'm afraid we have the same problem. Have you tried append ";exit" to the run-qemu command?

Sorry for the automatic Chinese translation. I have to use webmail light to access the email, I don't know why the VPN connection today is so slow that my Outlook doesn't work at all.

-Lianhao

________________________________________
发件人: Wang, Shane
发送时间: 2012年4月7日 14:50
到: Cui, Dexuan; Xu, Dongxiao; Saul Wold; Paul Eggleton
Cc: bitbake-devel at lists.openembedded.org; Zhang, Jessica; Lu, Lianhao
主题: RE: [bitbake-devel] hob2: make xterm automatically exit after qemu  exits?

Cui, Dexuan wrote on 2012-04-06:

> Cui, Dexuan wrote on 2012-04-05:
>> Hi all, I'm testing hob2's "Run image" functionality and found the xterm
>> window doesn't exit automatically after the qemu exits.
>>
>> As a result, every time when I try "Run image", a new xterm window is
>> created. After some rounds of testing, I have to manually terminate
>> many windows one by one... Is this the intended behavior? If no, I
>> think we should remove the "; bash" from builder.py(see the grep result
>> at the end of the mail)?
Intended to be. Removing "bash" doesn't fix the problem. I tried that before.
We followed what ADT did. Lianhao told me when the user needs to launch qemu to debug in ADT Eclipse plugin, the ADT team uses xterm, since that is the minimal terminal. So I didn't investigate other approaches but stood on the shoulder of the ADT team.

I suspect that will occur on ADT's side. Jessica, Lianhao, do you have better solution?

>>
>> BTW, I think the hig.py (the deploy tool) has the same issue?
>>
>> $ grep "; bash" bitbake/ -nr bitbake/lib/bb/ui/crumbs/builder.py:937:
>> cmdline += "runqemu " + kernel_path + " " + image_path + "; bash\""
>> bitbake/lib/bb/ui/crumbs/hig.py:741: cmdline += "\"sudo dd if=" +
>> self.image_path + " of=" + combo_item + "; bash\""
Yes.

>
> A new question:
> Why do we use /usr/bin/xterm here by hardcode?
> Can we change it to matchbox-terminal? Or, can we use some kind of
> algorithm to determine the available terminal?
Is matchbox-terminal the minimal terminal on Linux distributions, compared with xterm? If so, we can replace xterm with that.
Yes, we can, feature enhancement.

>
> I asked the question because in the self-hosted-image of poky,
> we don't have xterm (poky doesn't have a recipe for xterm) and I
> think it may not deserve the effort to add a recipe for xterm only
> for this specific usage in self-hosted-image.
I see. My concern is whether matchbox-terminal is available on Ubuntu/Fedora/OpenSuse/CentOS, and so on.

>
> Thanks,
> -- Dexuan
>