Bug 1305

Summary:	qemu unfs root messed up with sysroot
Product:	[Yocto Project Subprojects] Eclipse Plugin	Reporter:	liping Ke <liping.ke>
Component:	eclipse-plugin	Assignee:	Jessica <jessica.zhang>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Undecided	CC:	yp.ep.watcher, yp.watcher
Version:	unspecified
Target Milestone:	---
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description liping Ke 2011-07-28 19:21:59 UTC

Now we only have one place for deciding sysroot in unfs. But for meta-toolchain mode, sysroot does not contain unfs target sysroot, it only contains compilation build sysroot. So qemu unfs style will fail to boot. 
This problem relates to bug 1300.

in preference page, we expect user input unfs sysroot or compilation sysroot? It might be messed up...

Thanks& Regards,
criping

Comment 1 Jessica 2011-07-28 20:11:26 UTC

In preference page, the sysroot should be the sysroot that extracted from target rootfs, which support unfs.  We should never use the sysroot of the toolchain one in eclipse

Comment 2 liping Ke 2011-07-28 20:13:25 UTC

Hi, Jessica

Then seems we need to remove a piece of code in the code logic. Seems we also paste this --sysroot to eclipse settings. Then we will have multiple sysroot ... (eclipse env combined with environment vars)


Thanks& Regards,
criping

Comment 3 Jessica 2011-07-28 20:27:49 UTC

Yes, probably we should, we just don't take in the sysroot from the env file

Comment 4 liping Ke 2011-07-29 00:06:40 UTC

Final solution is that in eclipse, we will only have one sysroot. Same sysroot for compilation as well as qemu. When user define the sysroot, the one in the environement-setup file will be override.

The changeset is 

http://git.pokylinux.org/cgit/cgit.cgi/eclipse-poky/commit/?id=e5cff64183f42502b02169b2aa5febc4c1b87dd6

Comment 5 liping Ke 2011-07-29 00:07:45 UTC

*** Bug 1300 has been marked as a duplicate of this bug. ***