Bug 284

Summary: Enhance plugin UI's to make chroot requirement more explicit
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: Joshua Lock - Disabled <josh>
Component: eclipse-pluginAssignee: Jessica <jessica.zhang>
Status: VERIFIED FIXED QA Contact:
Severity: enhancement    
Priority: Low CC: kevin.tian, lianhao.lu, liping.ke, sgw, yongkang.you, yp.ep.watcher, yp.watcher
Version: 1.0   
Target Milestone: 1.0 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Attachments:
Description Flags
new preference setup window screen shot none

Description Joshua Lock - Disabled 2010-09-07 09:27:52 UTC
I'm referring to the Anjuta plugin in this bug report but I expect the situation is similar for the Eclipse one and I think the issue will want wider thought/discussion.

We have switched the Anjuta plugin to run local QEMU images in chroot mode by default, however we don't make this very explicit in the UI.

*Many* developers won't look to documentation first, if at all, so I think it would be good to spend some time tidying the UI to make the fact that we are running against a UNFS chroot more explicit.

Even better in my opinion would be some form of wizard to take a QEMU image and run the chroot processing scripts to create a chroot for the user.
Comment 1 Jessica 2011-01-28 16:33:56 UTC
Created attachment 90 [details]
new preference setup window screen shot
Comment 2 Jessica 2011-01-28 16:37:00 UTC
Everything is based on sysroot for 1.0 and it is setup using the rootfs file.  Please refer to the attached screen shot for the latest entries since the original rootfs selection is obsolete.

Also, we're going to use ADT installer to setup sysroot and planning to integrate it into Eclipse plug-in, so not taking calling poky-extract-sdk behind scene route.
Comment 3 Joshua Lock - Disabled 2011-07-25 08:22:47 UTC
Verify fixed