currently hob is tightly coupled with bitbake, even though it's capable of communicate with bitbake server through xmlrpc, but there's no clean way to start a standalone hob as an python client and just connect to bitbake server over xmlrpc and achieve all the existing functionality, etc. By separate hob from bitbake, allows further explore porting hob to other platforms other than Linux that allows user to still able to run a bitbake build
Updated the requirements, to support eclipse running on windows, we need to allow launching hob via windows environment.
Hello Jessica, Given the current way Hob works, and the directions established for 1.4 release (sync Hob configuration with a bitbake build dir), this feature means changing a lot of the inner and outer working of Hob. Also, this feature does not have a lot of details regarding the exact requirements (How to choose a specific bitbake build dir, etc). Can we please clarify this one? Wouldn't webhob be a much better approach into this one? At this point, there is a need to clarify all of this before being able to provide a work estimate on this one.
Hi Cristian, I talked with RP during ELCE and he pointed that bitbake has the option of running as server only and allow front-end to connect to it. So probably we should take a look of this option and see what need to be changed from hob's end to make it a front-end UI and connect to the bitbake server? I'd think the flow should be after in Eclipse create a bitbake commander project, which map to a meta-data directory. When launch hob, just like the existing pop out dialog, the user needs to specify the build directory. Then instead of just launching hob as the current behavior. It'll be 2 steps, 1st. start bitbake on the linux machine as server only. Then start hob as a front end UI and connect to the bitbake server running on linux box. Ioana, Can you show Cristian the current eclipse flow of bitbake commander and launching hob, so he can have a better picture of the flow from Eclipse perspective. Thanks, Jessica
Hello Jessica, Your comments clarify the request. Thank you. I will come back with an estimation. Regards, Cristian
Based on the information and requirements that are now available, the aim would be to have this feature available in beta before YP 1.4 M2 ends.
Technologies involved: Python GTK PyGTK XML-RPC Setup my development environment: Windows, PyGTK, GTK, VMware Player, Ubuntu Linux VM, bitbake, Windows git
Status report: Hob interface starts and after that crashes during the "Hob is checking for correct build system setup" initialization phase. Next step is to activate the XML-RPC backend.
Since we can preliminary support bitbake commander windows build via build appliance and also our Eclipse windows support needs to focus on application developer experienc improvement. So this requirement is pushed off from 1.4 and once the underline bitbake server side changes are in place, this should be faily easy to enable.
At this point, work will take place on toaster, not hob, so marking as won't fix.