Bug 800 - adt-installer should handle cases of no sysroot setup better
Summary: adt-installer should handle cases of no sysroot setup better
Status: RESOLVED FIXED
Alias: None
Product: ADT
Classification: Yocto Project Subprojects
Component: adt (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.0 M4
Assignee: Jessica
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-03-03 19:22 UTC by Jessica
Modified: 2011-03-09 07:34 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jessica 2011-03-03 19:22:23 UTC
During adt-installer testing found if I choose not setup sysroot using the adt-installer, in the environment script the --sysroot and --with-libtool-sysroot will be setup to ##TARGETSDKSYSROOT##, probably we should capture what is sysroot is defined in the adt-installer.conf, if it's empty there, don't set sysroot altogether.  The issue is in this case if user use command line, they have to setup sysroot anyway, but if using in the Eclipse IDE, the sysroot is setup there but the wrong setting in the script may override the IDE sysroot setup
Comment 1 liping Ke 2011-03-04 00:05:05 UTC
Hi, Jessica

After further thoughts, I think if user use default sysroot given by IDE, it will also be a fault. And also, it is a bug if he try it under command line. ##XXX## in any way, is a good prompt error, better than linking to default native sysroot. In a word, user must setup the sysroot, otherwise, he will meet all sorts of problems in the long run.

Then how about if user refuse to install target rootfs we'll
give a prompt, tell him that he should define the correct sysroot for the environment-setup-file?

Thanks & Regards,
criping