Re: [yocto] [PATCH 0/2][Image Creator] Hob Cache for speed up switching

[mailto:yocto-boun...@yoctoproject.org] On Behalf Of Joshua Lock > Sent: Wednesday, July 20, 2011 8:42 AM > To: yocto@yoctoproject.org > Subject: Re: [yocto] [PATCH 0/2][Image Creator] Hob Cache for speed up > switching > > On Mon, 2011-07-11 at 15:31 +0800, Ke Liping wrote: >

Re: [yocto] [PATCH 1/1][Image Creator] Remove unused target tree data for Hob

> > Looking good to me. The revised patch would ideally be sent to > bitbake-de...@lists.openembedded.org > Hi, Josh Thanks for the review. I will rebase to the latest poky master and resend the patch to the bitbake-devel list too! criping ___ yocto

[yocto] [PATCH 1/1] Remove unused target tree data for Hob

From: Liping Ke Since Hob only needes package dependency information, we can create a new version of package information retrieving methods, remove task dependency information, so that we can greatly reduce data loading time for Hob Signed-off-by: Liping Ke --- bitbake/lib/bb/cooker.py | 96

[yocto] [PATCH 0/1][Image Creator] Remove unused target tree data for Hob

From: Liping Ke Since Hob only needes package dependency information, we can create a new version of package information retrieving methods, remove task dependency information, so that we can greatly reduce data loading time for Hob The following changes since commit fa4bcfdb73167f8159b88e5a4d71

[yocto] [PATCH 2/2][Image Creator] Hob Cache for speed up switching

From: Liping Ke This patch is to cache target dependency tree for Hob (cache impl). Hob User might switch between different configuration combinations (machine, sdk-machine, distro, etc). Each dependency re-calcuation might be time consuming. We use a hashset to cache those result for avoiding re

[yocto] [PATCH 1/2][Image Creator] Hob Cache for speed up switching

From: Liping Ke This patch is the centralized place for storing Hob attributes. Most of informations in Prefs will be used when caching user-select packages information. Those information will be the cache hash-key which is useful in deciding whether the configuration combination value has been c

[yocto] [PATCH 0/2][Image Creator] Hob Cache for speed up switching

From: Liping Ke The two patches are the implmentation of Hob Cache for accelarating UI switching. If one configuration has been saved before, when user switch back to the same configuration combination, we will use the cache content instead of re-triggering parsing/loading phase. The following c

[yocto] [PATCH 4/4][Image Creator]Implement multiple extra cache fields request support

From: Liping Ke This patch is to support extra cache. If user needs to request extra cache fields besides CoreRecipeInfo fields, just add a new XXXRecipeInfo class definition as Hob Does. Currently supported Extra RecipeInfo name is an array. We can support multiple extra cache fields at the same

[yocto] [PATCH 3/4][Image Creator]Introduce new param caches_array into Cache impl.

From: Liping Ke When using hob ui interface, we need extra cache fields. We will save ui required extra cache fields into a separate cache file. This patch introduce this caches_array parameter. It will be used in the extra cache implementation (following patch). Caches_array at least contains Co

[yocto] [PATCH 2/4][Image Creator]Introduce extra cache class for image creator

From: Liping Ke Extra RecipeInfo will be all defined in this file. Currently, Only Hob (Image Creator) Requests some extra fields. So HobRecipeInfo is defined. It's named HobRecipeInfo because it is introduced by 'hob'. Users could also introduce other RecipeInfo or simply use those already defin

[yocto] [PATCH 1/4][Image Creator]Refactory Current Cache implementation

From: Liping Ke This patch is for refactorying current cache implementation, the main reason is for introducing extra cache fields requests for image creator as well as other users. The refactory parts include: Move cache data retrieve methods out of Cache Data Fields Definition. Since this retri

[yocto] [PATCH 0/4][Image Creator]Add mulitple extra cache fields request support

From: Liping Ke The series of patch are for mplementing multiple extra cache fields request support.If user needs to request extra cache fields besides CoreRecipeInfo fields, just add a new XXXRecipeInfo class definition as Image Creator UI Hob Does. For implementing this new feature, we refactor

Re: [yocto] [PATCH 0/4][Image Creator]Put extra requested fields into different cache files

to finish this refactory. Thanks& Regards, criping > -Original Message- > From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > Sent: Thursday, May 19, 2011 8:10 AM > To: Ke, Liping > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] [PATCH 0/4][I

Re: [yocto] [PATCH 0/4][Image Creator]Put extra requested fields into different cache files

/git.pokylinux.org/poky-contrib.git > Branch: lke/cache_impl > Browse: > http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=lke/cache_impl > > Thanks, > Liping Ke > --- > > > Liping Ke (4): > This patch introduce new param bitbake_mode into Cache.p

Re: [yocto] [PATCH 1/1] Resend:[Image-Creator]Make bitbake server type configurable (xmlrpc, none)

Hi, Josh Thanks for your very careful review indeed! I will correct them and resend the patch! Regards, criping > -Original Message- > From: Joshua Lock [mailto:j...@linux.intel.com] > Sent: Friday, April 29, 2011 4:32 AM > To: Ke, Liping > Cc: yocto@yoctoproject.or

[yocto] FW: [Yocto] discussion about bug770: Add mechanism to enable UI's to request extra data be stored in the cache

Wed, 2011-04-20 at 16:34 +0800, Ke, Liping wrote: > Hi, Jessica and Josh > > After looking into the cache.py, as well as the bug 770 description, I have > following questions: > > 1. Valid Cache Problem: we only have one cache file, right? > Use scenario 1: If developer firs

Re: [yocto] Remote Debugging with Yocto Project Plugin

Hi, Travaglia 1. Our our java code and eclipse code is in TCF upstream community already (both Agent C code and java code part). Yet the community code is slightly different with our poky-TCF. TCF upstream disable login process, yet our local poky-TCF have login authentication. So if w

Re: [yocto] current status for ADT

2011 8:03 AM > To: Ke, Liping; Lu, Lianhao > Cc: yocto@yoctoproject.org > Subject: RE: current status for ADT > > Liping and Lianhao, > > Attached is the updated 1.0 test template, feel free to add more test > cases. > I think we're building RC3 over the weekend,

[yocto] current status for ADT

Hi, Jessica We use today's latest poky master which includes all our own fixes to build (arm, i586, mips) target fs and cross toolchains. And then we run below test: Test environment: 1. For the available repo, use adt-installer installed toolchain: i686-arm. 2. For meta-toolchainsdk installe

Re: [yocto] About repo

Oh, the correct information is that RC2 will be ready @ this weekend. Thanks& Regards, criping > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Ke, Liping > Sent: Tuesday, March 01, 2011 10:03 AM > To:

[yocto] About repo

Hi, Jessica JiaJun told me that RC2 image will soon come out (Hopefully on Wednesday). So my question is that When will the repo be ready (With RC2 image). Seems we need to have some formal data for adt-installer testing. I want to do a full test asap. Thanks & regards, criping

Re: [yocto] about the repo

> > > Path 2: ADT installer (Not ready yet). Most code should be reused for > > the above two path. I think. > The symlinks are created. > > One gotcha for ADT installer testing is, please completely delete the > toolchain that installed from the toolchain tar ball under /opt/poky. > Since > the

Re: [yocto] about the repo

ready yet). Most code should be reused for the above two path. I think. Only for your info. I will update more details in the weekly meeting. Regards, criping > -Original Message- > From: Zhang, Jessica > Sent: Tuesday, February 22, 2011 12:51 PM > To: Ke, Liping; Lu, Lianhao

[yocto] about the repo

Hi, Jessica I am trying the adt-installer. The temporary repo contains some testing file, yet there're no short symbolic names for them. For example: under adtrepo.yoctoproject.org/1.0/rootfs/qemuarm/ there's no symbolic file of zImage-qemuarm.bin or poky-image-minimal-qemuarm.tar.bz2. All fil

[yocto] FW: fetch_error

Hi, all When I redo bitbake linux-libc-headers today, I repeatedly meet below do_fetch error, anybody could help to have a look? Thanks a lot! criping > -Original Message- > From: Ke, Liping > Sent: Thursday, February 17, 2011 5:07 PM > To: Ke, Liping > Subject: fetch_err

Re: [yocto] Master build error caused a small typo by commit today : fetch2: unpack revision

> >> Does not changing this "%d" to "%s" work? > > > > Yes, this is the correct fix. Nobody has been around today to push > the fix into > > the tree however. > > > > It was a simple typo. > > I managed to catch Richard on IRC about an hour ago and he pushed a fix > to master. > > Scott Hi, Sco

Re: [yocto] Master build error caused a small typo by commit today : fetch2: unpack revision

oproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Ke, Liping > Sent: Saturday, February 12, 2011 1:06 PM > To: richard.pur...@linuxfoundation.org; mark.ha...@windriver.com > Cc: yocto@yoctoproject.org > Subject: [yocto] Master build error caused a small typo by

[yocto] Master build error caused a small typo by commit today : fetch2: unpack revision

Hi, all Just found a small typo which caused built error today. The "%d" (file) should be changed to "%s", otherwise, compile error. Anybody could help to modify the small bug if you're happening sending patches. Thanks a lot for your help! criping author Mark Hatle2011-02-11 17:43:54

[yocto] one build error with latest cs, (Lock problem)

Hi, recently (from this week), I continuously meet build error (x86 and arm). Seems it's a kind of lock problem, eg: complaining that No such file or directory: {POKYBASE}/build-arm/tmp/sysroots/package-output.lock. (not limiting to this, I run into at least four times). Detailed log is pasted

[yocto] About adding sanity test for unfs qemu

Hi, Jiajun since sanity test works fine now, just want to know if there's any possible for adding some test cases for SDK side. 1. We want to know whether unfs qemu could work fine. Since we only support booting unfs qemu in with our SDK plugins (Eclipse, ANJUTA) 2. When our SDK installer is r

Re: [yocto] Setup repository for ADT installer

> -Original Message- > From: Lu, Lianhao > Sent: Thursday, January 06, 2011 10:12 AM > To: Flanagan, Elizabeth; Zhang, Jessica > Cc: Ke, Liping; yocto@yoctoproject.org > Subject: Setup repository for ADT installer > > Hi Beth and Jessica, > > Here is a summa

Re: [yocto] Eclipse Plugin EGit investigation result

Hi, Jessica I verified that if we use git from shell to clone a tree first, create the new project, and then use egit to manage the project, everything is fine. It will detect that .git repository is there and will not repeatedly create one. So egit will not conflict with native command line gi

Re: [yocto] Eclipse Plugin EGit investigation result

and hack the UI code 2) study the code, extract needed code. Both risks have been listed above. Thanks & Regards, criping > -Original Message- > From: Zhang, Jessica > Sent: Thursday, January 06, 2011 12:57 PM > To: Ke, Liping; Lu, Lianhao; Tian, Kevin > Cc: yocto@yoctopr

[yocto] Eclipse Plugin EGit investigation result

Hi, Jessica I have tried the existing egit plugin. It is a true powerful plugin, but I am afraid it can't be communicating well with poky-meta-project plugin. Below is some details advantages: 1. EGIT support all sorts of protocols, including ftp, ssh, git, http, so we can easily pull/push the

[yocto] Biweekly Status Report WW52~53'2010 --OSEL SDK Liping Ke

[Summary] 1. OSEL SDK related jobs 2. Others [Details] SDK related jobs: 1. Modified sdk installer scripts according to Josh's feedback, including a. Folder reorganization per Josh's suggestion, make the structure more user friendly b. Move sudo to a smaller granularity, so that u

[yocto] size of source file opkg and the opkg.tar.gz

Hi, Jessica Opkg source file is not very big. 437kb. And if untar, the folder size will be 1.92M, about four times. Seems not very big. So I will keep using do_unpack facilities. So that the installer script tarball will contain the source file directory. User need not unpack it during install

Re: [yocto] Questions about the name of qemu bin file for different archs

firstly. Thanks & Regards, criping > > On 10-12-14 02:40 AM, Ke, Liping wrote: > > Hi, Jessica > > > > I found qemu bin file name convention is different for different > archs, for example, for x86, it is bzImage-qemuXXX. > > For arm, it is zImage-qemuXXX. M

Re: [yocto] Help to review installer bb class file

tbake will not cause error. Thanks a lot! Regards, criping > -Original Message- > From: Ke, Liping > Sent: Monday, December 20, 2010 10:47 AM > To: Ke, Liping; Zhang, Jessica; Lu, Lianhao; Lock, Joshua > Cc: yocto@yoctoproject.org > Subject: RE: Help to review installe

Re: [yocto] Help to review installer bb class file

Hi, all Apart from Ke's suggestion that I need to add chksum for download file, any other feedbacks? Thanks& Regards, criping > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Ke, Liping > Sent: Frid

[yocto] Biweekly Status Report WW50~51'2010 --OSEL SDK Liping Ke

[Summary] 1. OSEL SDK related jobs 2. Others [Details] SDK related jobs: 1. Modified the first installer script according to Jessica and RP's input, including: 1) all sorts of echo message formalization. 2) Make script could be run anywhere. 3) solve the privilege level problem

[yocto] poweroff tomorrow, so lianhao's repository for testing installer might not be available

Hi, Jessica and all If anyone who want to try installer scripts, we will have a poweroff tomorrow, so I am not sure whether lianhao's repository still works or not. Just for your info! Thanks& Regards, criping ___ yocto mailing list yocto@yoctoproject.

[yocto] Help to review installer bb class file

Hi, Jessica and Josh This is a simple bb class file for generating installer tarball. And thanks for Lianhao/ke/Dexuan...'s help which saves me lots of efforts... It contains below steps: 1. fetch opkg source tarball to download location and copy other six files (opkg conf, scripts, user con

Re: [yocto] Try latest yocto adt script installer

Hi, Jessica Another thing is that after we bitbake the tarball, since bitbake will help us to do_unpack, so untar opkg is not needed actually. After bitbake job is finished, I will change the installer script code to remove untar opkg tarball steps. Thanks& Regards, criping _

Re: [yocto] Try latest yocto adt script installer

-Original Message- > From: Zhang, Jessica > Sent: Thursday, December 16, 2010 12:44 PM > To: Ke, Liping; Lu, Lianhao > Cc: yocto@yoctoproject.org > Subject: RE: [yocto] Try latest yocto adt script installer > > Ke, Liping wrote: > > Hi, Jessica > > > > I have te

Re: [yocto] Try latest yocto adt script installer

> Then can you modify the code before downloading each file, check > whether its > already exist or not, if so, prompt the user to confirm re-download or > skip? > And remove the existing checking for the download directory? Hi, Jessica Sure. I will change it and send you the updated patch a lit

Re: [yocto] Try latest yocto adt script installer

r_new Thanks& Regards, criping > -Original Message- > From: Zhang, Jessica > Sent: Wednesday, December 15, 2010 5:10 PM > To: Ke, Liping; Lu, Lianhao > Cc: yocto@yoctoproject.org > Subject: RE: [yocto] Try latest yocto adt script installer > > Liping, > >

Re: [yocto] Try latest yocto adt script installer

. Any problem, just let me know. Thanks& Regards, criping > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Ke, Liping > Sent: Wednesday, December 15, 2010 1:03 PM > To: Zhang, Jessica > Cc: yocto@yoct

Re: [yocto] Try latest yocto adt script installer

under root. Otherwise, the root folder will have to be changed. It will be not good. Thanks& Regards, criping > > We'll sync later tonight... > > Thanks, > Jessica > Ke, Liping wrote: > > Hi, Jessica > > > > For tracing the file, I temporarily

Re: [yocto] Add extra parameters for qemu script

Hi, Scott Thanks for the review! Sure, I will use the script following distro-team conventions. And also, $MYNAME will be used in the final patch. And the debug line for building will be removed when I send the final patch. Thanks & Regards, criping > One final thing - when you resubmit your

Re: [yocto] Try latest yocto adt script installer

essage----- > From: Ke, Liping > Sent: Tuesday, December 14, 2010 5:20 PM > To: Ke, Liping; Zhang, Jessica > Cc: yocto@yoctoproject.org > Subject: RE: [yocto] Try latest yocto adt script installer > > Hi, Jessica > > I have updated the script and it is still put under

Re: [yocto] Try latest yocto adt script installer

o:yocto- > boun...@yoctoproject.org] On Behalf Of Ke, Liping > Sent: Tuesday, December 14, 2010 2:40 PM > To: Zhang, Jessica > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Try latest yocto adt script installer > > > Why we must run the script under the adt-installer directory? > Actu

Re: [yocto] Questions about the name of qemu bin file for different archs

to:yocto- > boun...@yoctoproject.org] On Behalf Of Ke, Liping > Sent: Tuesday, December 14, 2010 3:41 PM > To: Zhang, Jessica > Cc: yocto@yoctoproject.org > Subject: [yocto] Questions about the name of qemu bin file for > different archs > > Hi, Jessica > > I found qemu bin f

[yocto] Questions about the name of qemu bin file for different archs

Hi, Jessica I found qemu bin file name convention is different for different archs, for example, for x86, it is bzImage-qemuXXX. For arm, it is zImage-qemuXXX. My question is why it is bzXXX or zXXX, is there any reason of such naming convention? Or I must did name translate for each kind of ar

Re: [yocto] Try latest yocto adt script installer

> Why we must run the script under the adt-installer directory? Actually > I > tried to run under $HOME or / but specifying the full path to > yocto_installer, and got the error: > [ADT_INST] script file util is not found! Oh, it's caused by the include grammar. I need to check how to solve the r

Re: [yocto] Add extra parameters for qemu script

Message- > From: Garman, Scott A > Sent: Monday, December 13, 2010 10:16 AM > To: Ke, Liping > Cc: Richard Purdie; Zhang, Jessica; Lu, Lianhao; Cui, Dexuan; > yocto@yoctoproject.org > Subject: Re: Add extra parameters for qemu script > > On 12/12/2010 05:43 PM, Ke,

[yocto] Try latest yocto adt script installer

Hi, Jessica I have put the installer script tar ball in the below links: http://llu-piketon.sh.intel.com/installer.tar You can have a try. Below is some key notes: 1. since now version has problems, we have submit bug 586 http://bugzilla.pokylinux.org/show_bug.cgi?id=586 So currently we have n

[yocto] version problems about SDK

Hi, Jessica & Josh When we are trying to run installer script on lianhao's x86_64 machine, we found if the images are build in two days, according to current version naming convention, some of the packages will be installed to /opt/poky/0.9+snapshot-20101210, some will be to /opt/poky/0.9+snap

Re: [yocto] Add extra parameters for qemu script

> I tend to feel that this approach is more flexible, and scales better > > than having to support each and every qemu option with our own script > > syntax. Is this acceptable, or should we continue to support our own > > custom options in addition to Criping's new approach? > > My gut feeling is

Re: [yocto] PULL] ADT installer script implementation, Liping Ke

Hi, Richard & Jessica Actually I am not sure user requirement about the configuration input UI interactive interface One possible solution is 1) For those can't be changed by users (supported archs, supported os, it is defined by us), I prefer no UI interaction, and hard code in script 2) For

Re: [yocto] PULL] ADT installer script implementation, Liping Ke

> That definitely a bug regarding how to locate .config that we need to > address. As to the different config files, the .config is on purpose > non > user editable that's why we set it as hidden file by default. And the > yocto_installer.conf is the customizable config user should change and > w

Re: [yocto] PULL] ADT installer script implementation, Liping Ke

> > The first thing I read was in the patch was: > > > > +# following are for testing in my machine. it will be moved when > > +# going into code repository > > +export http_proxy="" > > +export HTTP_PROXY="" > > +export HTTPS_PROXY="" > > +export https_proxy="" > > +export ftp_proxy="" > > +export

[yocto] PULL] ADT installer script implementation, Liping Ke

Hi, Saul This pull request includes initial ADT(Yocto Application Development Tools) installer script implementation. Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: lke/adt_installer_initial Browse: http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/commit/?h=lke/adt_installer_init

[yocto] Add extra parameters for qemu script

Hi, Scott The patch is in the attachment for your review. Below is some notes: 1) Basically I wouldn't like to change any logic of the original code. 2) -serial stdio and -nographic options are removed since they're be covered by the extra parameters. 3) User input would be $poky-qemu qemux86 "<

[yocto] FW: [Bug 246987] [tcf] Would be nice to have Shell(Terminal) subsystem over TCF

Hi, Jessica FYI. TCF terminal/shell java code part is now in upstream. Thanks& Regards, criping > -Original Message- > From: bugzilla-dae...@eclipse.org [mailto:bugzilla-dae...@eclipse.org] > Sent: Wednesday, December 08, 2010 11:54 PM > To: Ke, Liping > Subject

Re: [yocto] yocto_installer test script update

And Jessica If you have no rights to modify my branch tree ( I am not sure), you can check it in your own branch. We can merge it later. Thanks a lot! criping > -Original Message- > From: Ke, Liping > Sent: Wednesday, December 08, 2010 5:35 PM > To: Zhang, Jessica; Tia

Re: [yocto] yocto_installer test script update

riginal Message- > From: Zhang, Jessica > Sent: Tuesday, December 07, 2010 1:34 PM > To: Ke, Liping; Tian, Kevin; Lu, Lianhao > Cc: yocto@yoctoproject.org > Subject: RE: yocto_installer test script update > > Ke, Liping wrote: > > the final files a little later. Ju

Re: [yocto] param format about qeme extra options parse in

Thanks scott! I will send you the patch for review after I add the extra parameter. Thanks & Regards, criping > -Original Message- > From: Garman, Scott A > Sent: Tuesday, December 07, 2010 5:04 PM > To: Ke, Liping > Cc: Zhang, Jessica; Lu, Lianhao; yocto@yoctoprojec

[yocto] param format about qeme extra options parse in

Hi, Jessica & Scott I am now look...@the task of User specified qemu config support, desc " We'll provide user an edit box which allows advanced qemu user to specify arbitrary qemu configuration to meet their needs, which the poky-qemu scrip will just append the config list towards the end of t

Re: [yocto] yocto_installer test script update

the final files a little later. Just wait. > > > > why don't you setup a master repo on git.pokylinux.org? anyway we > > need such thing finally and now you have multiple people touching > > same code... > > Yes, realize the issue from today's situation, I'll setup a repo for > the > installer onc

Re: [yocto] yocto_installer test script update

cember 07, 2010 12:39 PM > To: Ke, Liping; Lu, Lianhao > Cc: yocto@yoctoproject.org > Subject: RE: yocto_installer test script update > > Liping, > > It's not new image for each install, I want to download image whether > new or > old for each install period. Reason

Re: [yocto] yocto_installer test script update

Ok, you want to download new image for each install... Ok, no problem. I will change that. Thanks& Regards, criping > -Original Message- > From: Ke, Liping > Sent: Tuesday, December 07, 2010 10:59 AM > To: Zhang, Jessica; Lu, Lianhao > Cc: yocto@yoctoprojec

Re: [yocto] yocto_installer test script update

3. Correct > the problem for qemu image download, now we forcing download images in > a clean directory since wget will change the file ext if the file > already there and which maybe corrupted > Hi, Jessica Have question for this one. Now the code will directly downloading, so the folders might

Re: [yocto] yocto_installer test script update

Ops. Seems I made concurrent changes again Seems I need to redo today's work I will update the final files a little later. Just wait. criping > -Original Message- > From: Zhang, Jessica > Sent: Tuesday, December 07, 2010 9:34 AM > To: Ke, Liping; Lu, Li

Re: [yocto] yocto_installer test script update

Message- > From: Ke, Liping > Sent: Monday, December 06, 2010 6:15 PM > To: Ke, Liping; Zhang, Jessica; Lu, Lianhao; Tian, Kevin > Cc: yocto@yoctoproject.org > Subject: RE: yocto_installer test script update > > Just one thing, if directly tee, check_result will get wron

Re: [yocto] yocto_installer test script update

Just one thing, if directly tee, check_result will get wrong output result. So I did not tee opkg/make related command. I will try to add opkg/make to logfile tomorrow. > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Beh

Re: [yocto] yocto_installer test script update

Hi, Jessica I have updated the script file which modifies all your input (prompts and the discussion result in the weekly meeting such as logfile, go on installing when /var/lib/opkg exists, etc). I have tested with lianhao's repository (x86_64 native sdk has some problem, he's now fixing i

[yocto] [Yocto] Biweekly Status Report WW48~49'2010 --OSEL SDK Liping Ke

[Summary] 1. OSEL SDK related jobs 2. Others [Details] SDK related jobs: 1. Finished a rough shell script ADT(SDK) installer We can now successfully install selected native sdks and tar the select root fs through the testing repository. The flow is now whole and smooth and most

Re: [yocto] yocto_installer test script update

Hi, Jessica Since I got a high fever yesterday so did not come to office in the morning... Please see my reply below... Thanks& Regards, criping > -Original Message- > From: Zhang, Jessica > Sent: Friday, December 03, 2010 8:23 AM > To: Ke, Liping; Lu, Lianhao; Tian, K

Re: [yocto] yocto_installer test script update

Sent: Thursday, December 02, 2010 8:19 AM > To: Ke, Liping; Lu, Lianhao; Tian, Kevin > Cc: yocto@yoctoproject.org > Subject: RE: yocto_installer test script update > > Liping, > > I've modified couple files mainly for the messaging, styling, etc. > Also, globaly chan

Re: [yocto] yocto_installer test script update

> -Original Message- > From: Zhang, Jessica > Sent: Thursday, December 02, 2010 8:19 AM > To: Ke, Liping; Lu, Lianhao; Tian, Kevin > Cc: yocto@yoctoproject.org > Subject: RE: yocto_installer test script update > > Liping, > > I've modified couple file

Re: [yocto] yocto_installer test script update

address all your comments. After finish it, I will post the refined version to you a little later. Thanks a lot! criping > -Original Message- > From: Zhang, Jessica > Sent: Thursday, December 02, 2010 8:19 AM > To: Ke, Liping; Lu, Lianhao; Tian, Kevin > Cc: yocto@yoctoprojec

[yocto] yocto_installer test script update

Hi, Jessica The newer version of the installer is in lianhao's location. You can directly run ./yocto_installer http://llu-piketon.sh.intel.com/ Today we tested both on 32 bit and 64 bit ubuntu host. It's very initial and rough, I will move many non-root required ops into the outer wrapper scr

Re: [yocto] about install shell script privilege problem

> Liping, > > I think this is consistent with the current SDK tarball installation > that by > default going under /opt/poky. Since our installer script will install > things under /opt/poky as well, using sudo to run the script should be > fine > till we can install the host cross toolchain unde

[yocto] about install shell script privilege problem

Hi, Jessica When testing the script, we found some privilege problems if using normal user to install the sdk. Now all those packages must be installed to /opt, which acquire root privilege. So when running opkg-cl, the installation root must be pointed to "/", so opkg-cl needs root privilege t