Bug 1300

Summary: multiple sysroot messed up sysroot
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: liping Ke <liping.ke>
Component: eclipse-pluginAssignee: liping Ke <liping.ke>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Medium CC: jessica.zhang, yp.ep.watcher, yp.watcher
Version: unspecified   
Target Milestone: 1.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description liping Ke 2011-07-28 01:17:46 UTC
When when testing arm, we found that there are several --sysroot messed up, when do autoconf, so config fails. Several sysroot messed up (I use user extracted rootfs, yet source meta-toolchain extracted env files) (if using adt installer, adt installer will help to do the sysroot override, maybe this problem will be avoided).

Need to settle down this problem.
Comment 1 liping Ke 2011-07-28 19:11:14 UTC
I am still thinking about the problem.

Now we source the environment files. In normal cases, this should be the only right ref. It decides the cmd line execution result. If user select a different sysroot in Eclipse Preference. The conflicts occurs. 

What's the best way of dealing this conflict?

For metatoolchain tarball, we originally suppose not supporting unfs. (we found the bug because we use unfs under this circumstances)
For adt-installer, we help to pass the env file and update it to the right loc.

But in eclipse, we do have a place to define the rootfs... If this is the case, then in eclipse, we'll say that env file does not have any effect, only eclipse settings are the correct one?

Thanks& Regards,
criping
Comment 2 Jessica 2011-07-28 20:08:43 UTC
Once in eclipse, eclipse setting should override the env setting,  but in the command line, the env file should take effect.  Will this rule clear the issue?
Comment 3 liping Ke 2011-07-28 20:19:25 UTC
Hi, jessica

Oh, the problem actually combined with 1305.

I found if we have one sysroot for compilation, one sysroot for unfs, we'll have problem. Actually, if we only support defining sysroot for unfs in preference page, we should never override the settings in the env file.

criping

(In reply to comment #2)
> Once in eclipse, eclipse setting should override the env setting,  but in the
> command line, the env file should take effect.  Will this rule clear the issue?
Comment 4 Jessica 2011-07-28 20:26:55 UTC
We don't need to override the sysroot in env file, just that in eclipse we'd expect user to setup the sysroot as the unfs one, if not, it'll run into problem.  In eclipse, the env file sysroot shouldn't take effect
Comment 5 liping Ke 2011-07-29 00:07:45 UTC
Mark this bug as the duplicates of 1305. When bug 1305 solved, this problem will be solved too.

http://bugzilla.pokylinux.org/show_bug.cgi?id=1305

*** This bug has been marked as a duplicate of bug 1305 ***