* How to identify WORKDIR?
@ 2012-03-14 9:01 Kang Kai
2012-03-14 9:42 ` Richard Purdie
0 siblings, 1 reply; 13+ messages in thread
From: Kang Kai @ 2012-03-14 9:01 UTC (permalink / raw)
To: bitbake-devel; +Cc: Richard Purdie
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
Hi All,
I write a script to clean up WORKDIR that remove the obsoleted packages'
build directories.
The script accept a argument as BUILDDIR and I use this clause to
identify the WORKDIR:
workdir = os.path.join(builddir, 'tmp/work')
Then validate the workdir exists or not. It works for me but hardcode
here as Richard point out.
So is there a better way to get the WORKDIR here? Thanks.
Regards,
Kai
[-- Attachment #2: Type: text/html, Size: 777 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: How to identify WORKDIR? 2012-03-14 9:01 How to identify WORKDIR? Kang Kai @ 2012-03-14 9:42 ` Richard Purdie 2012-03-15 6:55 ` Kang Kai 0 siblings, 1 reply; 13+ messages in thread From: Richard Purdie @ 2012-03-14 9:42 UTC (permalink / raw) To: Kang Kai; +Cc: bitbake-devel On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: > Hi All, > > I write a script to clean up WORKDIR that remove the obsoleted > packages' build directories. > The script accept a argument as BUILDDIR and I use this clause to > identify the WORKDIR: > > workdir = os.path.join(builddir, 'tmp/work') > > Then validate the workdir exists or not. It works for me but hardcode > here as Richard point out. > So is there a better way to get the WORKDIR here? Thanks. I was thinking of something like: bitbake -e | grep ^WORKDIR since you already call into bitbake in the script in question. Cheers, Richard ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-14 9:42 ` Richard Purdie @ 2012-03-15 6:55 ` Kang Kai 2012-03-15 7:40 ` Kang Kai 0 siblings, 1 reply; 13+ messages in thread From: Kang Kai @ 2012-03-15 6:55 UTC (permalink / raw) To: Richard Purdie; +Cc: bitbake-devel On 2012年03月14日 17:42, Richard Purdie wrote: > On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: >> Hi All, >> >> I write a script to clean up WORKDIR that remove the obsoleted >> packages' build directories. >> The script accept a argument as BUILDDIR and I use this clause to >> identify the WORKDIR: >> >> workdir = os.path.join(builddir, 'tmp/work') >> >> Then validate the workdir exists or not. It works for me but hardcode >> here as Richard point out. >> So is there a better way to get the WORKDIR here? Thanks. > I was thinking of something like: > > bitbake -e | grep ^WORKDIR If get WORKDIR in this way, I'll update the script with no argument because the argument is useless to identify the WORKDIR. Regards, Kai > > since you already call into bitbake in the script in question. > > Cheers, > > Richard > > ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-15 6:55 ` Kang Kai @ 2012-03-15 7:40 ` Kang Kai 2012-03-15 8:03 ` Martin Jansa 0 siblings, 1 reply; 13+ messages in thread From: Kang Kai @ 2012-03-15 7:40 UTC (permalink / raw) To: Richard Purdie; +Cc: bitbake-devel On 2012年03月15日 14:55, Kang Kai wrote: > On 2012年03月14日 17:42, Richard Purdie wrote: >> On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: >>> Hi All, >>> >>> I write a script to clean up WORKDIR that remove the obsoleted >>> packages' build directories. >>> The script accept a argument as BUILDDIR and I use this clause to >>> identify the WORKDIR: >>> >>> workdir = os.path.join(builddir, 'tmp/work') >>> >>> Then validate the workdir exists or not. It works for me but hardcode >>> here as Richard point out. >>> So is there a better way to get the WORKDIR here? Thanks. >> I was thinking of something like: >> >> bitbake -e | grep ^WORKDIR And the result is something like that: WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" Is it ok to remove 2 items seperated by slash at the end of string? Right now is: "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" Regards, Kai > > If get WORKDIR in this way, I'll update the script with no argument > because the argument is useless to identify the WORKDIR. > > Regards, > Kai >> >> since you already call into bitbake in the script in question. >> >> Cheers, >> >> Richard >> >> > > > _______________________________________________ > bitbake-devel mailing list > bitbake-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-15 7:40 ` Kang Kai @ 2012-03-15 8:03 ` Martin Jansa 2012-03-15 9:09 ` Kang Kai 0 siblings, 1 reply; 13+ messages in thread From: Martin Jansa @ 2012-03-15 8:03 UTC (permalink / raw) To: Kang Kai; +Cc: bitbake-devel [-- Attachment #1: Type: text/plain, Size: 1904 bytes --] On Thu, Mar 15, 2012 at 03:40:04PM +0800, Kang Kai wrote: > On 2012年03月15日 14:55, Kang Kai wrote: > > On 2012年03月14日 17:42, Richard Purdie wrote: > >> On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: > >>> Hi All, > >>> > >>> I write a script to clean up WORKDIR that remove the obsoleted > >>> packages' build directories. > >>> The script accept a argument as BUILDDIR and I use this clause to > >>> identify the WORKDIR: > >>> > >>> workdir = os.path.join(builddir, 'tmp/work') > >>> > >>> Then validate the workdir exists or not. It works for me but hardcode > >>> here as Richard point out. > >>> So is there a better way to get the WORKDIR here? Thanks. > >> I was thinking of something like: > >> > >> bitbake -e | grep ^WORKDIR > And the result is something like that: > WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" > > Is it ok to remove 2 items seperated by slash at the end of string? > Right now is: > "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" Aren't you looking for ^TMPDIR ? > > Regards, > Kai > > > > > If get WORKDIR in this way, I'll update the script with no argument > > because the argument is useless to identify the WORKDIR. > > > > Regards, > > Kai > >> > >> since you already call into bitbake in the script in question. > >> > >> Cheers, > >> > >> Richard > >> > >> > > > > > > _______________________________________________ > > bitbake-devel mailing list > > bitbake-devel@lists.openembedded.org > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > _______________________________________________ > bitbake-devel mailing list > bitbake-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-15 8:03 ` Martin Jansa @ 2012-03-15 9:09 ` Kang Kai 2012-03-15 9:21 ` Martin Jansa 0 siblings, 1 reply; 13+ messages in thread From: Kang Kai @ 2012-03-15 9:09 UTC (permalink / raw) To: Martin Jansa; +Cc: bitbake-devel On 2012年03月15日 16:03, Martin Jansa wrote: > On Thu, Mar 15, 2012 at 03:40:04PM +0800, Kang Kai wrote: >> On 2012年03月15日 14:55, Kang Kai wrote: >>> On 2012年03月14日 17:42, Richard Purdie wrote: >>>> On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: >>>>> Hi All, >>>>> >>>>> I write a script to clean up WORKDIR that remove the obsoleted >>>>> packages' build directories. >>>>> The script accept a argument as BUILDDIR and I use this clause to >>>>> identify the WORKDIR: >>>>> >>>>> workdir = os.path.join(builddir, 'tmp/work') >>>>> >>>>> Then validate the workdir exists or not. It works for me but hardcode >>>>> here as Richard point out. >>>>> So is there a better way to get the WORKDIR here? Thanks. >>>> I was thinking of something like: >>>> >>>> bitbake -e | grep ^WORKDIR >> And the result is something like that: >> WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" >> >> Is it ok to remove 2 items seperated by slash at the end of string? >> Right now is: >> "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" > Aren't you looking for ^TMPDIR ? If use WORKDIR = TMPDIR/"work", it is still hard coding. >> Regards, >> Kai >> >>> If get WORKDIR in this way, I'll update the script with no argument >>> because the argument is useless to identify the WORKDIR. >>> >>> Regards, >>> Kai >>>> since you already call into bitbake in the script in question. >>>> >>>> Cheers, >>>> >>>> Richard >>>> >>>> >>> >>> _______________________________________________ >>> bitbake-devel mailing list >>> bitbake-devel@lists.openembedded.org >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel >> >> _______________________________________________ >> bitbake-devel mailing list >> bitbake-devel@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-15 9:09 ` Kang Kai @ 2012-03-15 9:21 ` Martin Jansa 2012-03-15 9:34 ` Kang Kai 2012-03-15 18:18 ` Denys Dmytriyenko 0 siblings, 2 replies; 13+ messages in thread From: Martin Jansa @ 2012-03-15 9:21 UTC (permalink / raw) To: Kang Kai; +Cc: bitbake-devel [-- Attachment #1: Type: text/plain, Size: 3006 bytes --] On Thu, Mar 15, 2012 at 05:09:36PM +0800, Kang Kai wrote: > On 2012年03月15日 16:03, Martin Jansa wrote: > > On Thu, Mar 15, 2012 at 03:40:04PM +0800, Kang Kai wrote: > >> On 2012年03月15日 14:55, Kang Kai wrote: > >>> On 2012年03月14日 17:42, Richard Purdie wrote: > >>>> On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: > >>>>> Hi All, > >>>>> > >>>>> I write a script to clean up WORKDIR that remove the obsoleted > >>>>> packages' build directories. > >>>>> The script accept a argument as BUILDDIR and I use this clause to > >>>>> identify the WORKDIR: > >>>>> > >>>>> workdir = os.path.join(builddir, 'tmp/work') > >>>>> > >>>>> Then validate the workdir exists or not. It works for me but hardcode > >>>>> here as Richard point out. > >>>>> So is there a better way to get the WORKDIR here? Thanks. > >>>> I was thinking of something like: > >>>> > >>>> bitbake -e | grep ^WORKDIR > >> And the result is something like that: > >> WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" > >> > >> Is it ok to remove 2 items seperated by slash at the end of string? > >> Right now is: > >> "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" > > Aren't you looking for ^TMPDIR ? > > If use WORKDIR = TMPDIR/"work", it is still hard coding. Assuming 2 items at the end won't work for people using rm_old_work: http://git.openembedded.org/meta-micro/commit/?id=fcf525654915edb9650f1a6c2852f336366f8b2f or slightly different version: http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-shr/classes/rm_old_work.bbclass And I think more people have different "tmp/" part e.g. default would be "tmp-eglibc/" (thanks to TCLIBCAPPEND meta/conf/distro/defaultsetup.conf:TMPDIR .= "${TCLIBCAPPEND}"), but "work" is quite common. meta/conf/bitbake.conf: WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PF}" meta-shr/classes/rm_old_work.bbclass: WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${PF}" meta-micro/classes/rm_old_work.bbclass: WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" Cheers, > > >> Regards, > >> Kai > >> > >>> If get WORKDIR in this way, I'll update the script with no argument > >>> because the argument is useless to identify the WORKDIR. > >>> > >>> Regards, > >>> Kai > >>>> since you already call into bitbake in the script in question. > >>>> > >>>> Cheers, > >>>> > >>>> Richard > >>>> > >>>> > >>> > >>> _______________________________________________ > >>> bitbake-devel mailing list > >>> bitbake-devel@lists.openembedded.org > >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > >> > >> _______________________________________________ > >> bitbake-devel mailing list > >> bitbake-devel@lists.openembedded.org > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-15 9:21 ` Martin Jansa @ 2012-03-15 9:34 ` Kang Kai 2012-03-15 18:18 ` Denys Dmytriyenko 1 sibling, 0 replies; 13+ messages in thread From: Kang Kai @ 2012-03-15 9:34 UTC (permalink / raw) To: Martin Jansa; +Cc: bitbake-devel On 2012年03月15日 17:21, Martin Jansa wrote: > On Thu, Mar 15, 2012 at 05:09:36PM +0800, Kang Kai wrote: >> On 2012年03月15日 16:03, Martin Jansa wrote: >>> On Thu, Mar 15, 2012 at 03:40:04PM +0800, Kang Kai wrote: >>>> On 2012年03月15日 14:55, Kang Kai wrote: >>>>> On 2012年03月14日 17:42, Richard Purdie wrote: >>>>>> On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: >>>>>>> Hi All, >>>>>>> >>>>>>> I write a script to clean up WORKDIR that remove the obsoleted >>>>>>> packages' build directories. >>>>>>> The script accept a argument as BUILDDIR and I use this clause to >>>>>>> identify the WORKDIR: >>>>>>> >>>>>>> workdir = os.path.join(builddir, 'tmp/work') >>>>>>> >>>>>>> Then validate the workdir exists or not. It works for me but hardcode >>>>>>> here as Richard point out. >>>>>>> So is there a better way to get the WORKDIR here? Thanks. >>>>>> I was thinking of something like: >>>>>> >>>>>> bitbake -e | grep ^WORKDIR >>>> And the result is something like that: >>>> WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" >>>> >>>> Is it ok to remove 2 items seperated by slash at the end of string? >>>> Right now is: >>>> "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" >>> Aren't you looking for ^TMPDIR ? >> If use WORKDIR = TMPDIR/"work", it is still hard coding. > Assuming 2 items at the end won't work for people using rm_old_work: > http://git.openembedded.org/meta-micro/commit/?id=fcf525654915edb9650f1a6c2852f336366f8b2f > or slightly different version: > http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-shr/classes/rm_old_work.bbclass Hi Martin, > And I think more people have different "tmp/" part e.g. default would be > "tmp-eglibc/" (thanks to TCLIBCAPPEND > meta/conf/distro/defaultsetup.conf:TMPDIR .= "${TCLIBCAPPEND}"), but "work" is > quite common. > > meta/conf/bitbake.conf: > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PF}" > meta-shr/classes/rm_old_work.bbclass: > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${PF}" > meta-micro/classes/rm_old_work.bbclass: > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" OK. Thanks very much. Regards, Kai > Cheers, > >>>> Regards, >>>> Kai >>>> >>>>> If get WORKDIR in this way, I'll update the script with no argument >>>>> because the argument is useless to identify the WORKDIR. >>>>> >>>>> Regards, >>>>> Kai >>>>>> since you already call into bitbake in the script in question. >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Richard >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> bitbake-devel mailing list >>>>> bitbake-devel@lists.openembedded.org >>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel >>>> _______________________________________________ >>>> bitbake-devel mailing list >>>> bitbake-devel@lists.openembedded.org >>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-15 9:21 ` Martin Jansa 2012-03-15 9:34 ` Kang Kai @ 2012-03-15 18:18 ` Denys Dmytriyenko 2012-03-16 6:41 ` Martin Jansa 1 sibling, 1 reply; 13+ messages in thread From: Denys Dmytriyenko @ 2012-03-15 18:18 UTC (permalink / raw) To: Martin Jansa; +Cc: Kang Kai, bitbake-devel On Thu, Mar 15, 2012 at 10:21:22AM +0100, Martin Jansa wrote: > On Thu, Mar 15, 2012 at 05:09:36PM +0800, Kang Kai wrote: > > On 2012???03???15??? 16:03, Martin Jansa wrote: > > > On Thu, Mar 15, 2012 at 03:40:04PM +0800, Kang Kai wrote: > > >> On 2012???03???15??? 14:55, Kang Kai wrote: > > >>> On 2012???03???14??? 17:42, Richard Purdie wrote: > > >>>> On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: > > >>>>> Hi All, > > >>>>> > > >>>>> I write a script to clean up WORKDIR that remove the obsoleted > > >>>>> packages' build directories. > > >>>>> The script accept a argument as BUILDDIR and I use this clause to > > >>>>> identify the WORKDIR: > > >>>>> > > >>>>> workdir = os.path.join(builddir, 'tmp/work') > > >>>>> > > >>>>> Then validate the workdir exists or not. It works for me but hardcode > > >>>>> here as Richard point out. > > >>>>> So is there a better way to get the WORKDIR here? Thanks. > > >>>> I was thinking of something like: > > >>>> > > >>>> bitbake -e | grep ^WORKDIR > > >> And the result is something like that: > > >> WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" > > >> > > >> Is it ok to remove 2 items seperated by slash at the end of string? > > >> Right now is: > > >> "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" > > > Aren't you looking for ^TMPDIR ? > > > > If use WORKDIR = TMPDIR/"work", it is still hard coding. > > Assuming 2 items at the end won't work for people using rm_old_work: > http://git.openembedded.org/meta-micro/commit/?id=fcf525654915edb9650f1a6c2852f336366f8b2f > or slightly different version: > http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-shr/classes/rm_old_work.bbclass Martin, Can you please point me to more details about this class - any background or discussions... Thanks. -- Denys > And I think more people have different "tmp/" part e.g. default would be > "tmp-eglibc/" (thanks to TCLIBCAPPEND > meta/conf/distro/defaultsetup.conf:TMPDIR .= "${TCLIBCAPPEND}"), but "work" is > quite common. > > meta/conf/bitbake.conf: > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PF}" > meta-shr/classes/rm_old_work.bbclass: > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${PF}" > meta-micro/classes/rm_old_work.bbclass: > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" > > Cheers, > > > > > >> Regards, > > >> Kai > > >> > > >>> If get WORKDIR in this way, I'll update the script with no argument > > >>> because the argument is useless to identify the WORKDIR. > > >>> > > >>> Regards, > > >>> Kai > > >>>> since you already call into bitbake in the script in question. > > >>>> > > >>>> Cheers, > > >>>> > > >>>> Richard > > >>>> > > >>>> > > >>> > > >>> _______________________________________________ > > >>> bitbake-devel mailing list > > >>> bitbake-devel@lists.openembedded.org > > >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > >> > > >> _______________________________________________ > > >> bitbake-devel mailing list > > >> bitbake-devel@lists.openembedded.org > > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > -- > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com > _______________________________________________ > bitbake-devel mailing list > bitbake-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-15 18:18 ` Denys Dmytriyenko @ 2012-03-16 6:41 ` Martin Jansa 2012-03-19 20:32 ` Denys Dmytriyenko 0 siblings, 1 reply; 13+ messages in thread From: Martin Jansa @ 2012-03-16 6:41 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: Kang Kai, bitbake-devel [-- Attachment #1: Type: text/plain, Size: 4244 bytes --] On Thu, Mar 15, 2012 at 02:18:44PM -0400, Denys Dmytriyenko wrote: > On Thu, Mar 15, 2012 at 10:21:22AM +0100, Martin Jansa wrote: > > On Thu, Mar 15, 2012 at 05:09:36PM +0800, Kang Kai wrote: > > > On 2012???03???15??? 16:03, Martin Jansa wrote: > > > > On Thu, Mar 15, 2012 at 03:40:04PM +0800, Kang Kai wrote: > > > >> On 2012???03???15??? 14:55, Kang Kai wrote: > > > >>> On 2012???03???14??? 17:42, Richard Purdie wrote: > > > >>>> On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: > > > >>>>> Hi All, > > > >>>>> > > > >>>>> I write a script to clean up WORKDIR that remove the obsoleted > > > >>>>> packages' build directories. > > > >>>>> The script accept a argument as BUILDDIR and I use this clause to > > > >>>>> identify the WORKDIR: > > > >>>>> > > > >>>>> workdir = os.path.join(builddir, 'tmp/work') > > > >>>>> > > > >>>>> Then validate the workdir exists or not. It works for me but hardcode > > > >>>>> here as Richard point out. > > > >>>>> So is there a better way to get the WORKDIR here? Thanks. > > > >>>> I was thinking of something like: > > > >>>> > > > >>>> bitbake -e | grep ^WORKDIR > > > >> And the result is something like that: > > > >> WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" > > > >> > > > >> Is it ok to remove 2 items seperated by slash at the end of string? > > > >> Right now is: > > > >> "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" > > > > Aren't you looking for ^TMPDIR ? > > > > > > If use WORKDIR = TMPDIR/"work", it is still hard coding. > > > > Assuming 2 items at the end won't work for people using rm_old_work: > > http://git.openembedded.org/meta-micro/commit/?id=fcf525654915edb9650f1a6c2852f336366f8b2f > > or slightly different version: > > http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-shr/classes/rm_old_work.bbclass > > Martin, > > Can you please point me to more details about this class - any background or > discussions... Thanks. Hi, Well it works better then rm_work with sstate and the original class is from meta-micro (so maybe ask pb if you want more details, but the class is quite simple). I've just replaced last directory name because of this issue: http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=0d4c17de1ba7343d82bb10c311754e29d573c485 Cheers, > > -- > Denys > > > > And I think more people have different "tmp/" part e.g. default would be > > "tmp-eglibc/" (thanks to TCLIBCAPPEND > > meta/conf/distro/defaultsetup.conf:TMPDIR .= "${TCLIBCAPPEND}"), but "work" is > > quite common. > > > > meta/conf/bitbake.conf: > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PF}" > > meta-shr/classes/rm_old_work.bbclass: > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${PF}" > > meta-micro/classes/rm_old_work.bbclass: > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" > > > > Cheers, > > > > > > > > >> Regards, > > > >> Kai > > > >> > > > >>> If get WORKDIR in this way, I'll update the script with no argument > > > >>> because the argument is useless to identify the WORKDIR. > > > >>> > > > >>> Regards, > > > >>> Kai > > > >>>> since you already call into bitbake in the script in question. > > > >>>> > > > >>>> Cheers, > > > >>>> > > > >>>> Richard > > > >>>> > > > >>>> > > > >>> > > > >>> _______________________________________________ > > > >>> bitbake-devel mailing list > > > >>> bitbake-devel@lists.openembedded.org > > > >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > >> > > > >> _______________________________________________ > > > >> bitbake-devel mailing list > > > >> bitbake-devel@lists.openembedded.org > > > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > > > > -- > > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com > > > > > _______________________________________________ > > bitbake-devel mailing list > > bitbake-devel@lists.openembedded.org > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-16 6:41 ` Martin Jansa @ 2012-03-19 20:32 ` Denys Dmytriyenko 2012-03-19 21:37 ` Christopher Larson 0 siblings, 1 reply; 13+ messages in thread From: Denys Dmytriyenko @ 2012-03-19 20:32 UTC (permalink / raw) To: Martin Jansa; +Cc: philb, Kang Kai, bitbake-devel On Fri, Mar 16, 2012 at 07:41:52AM +0100, Martin Jansa wrote: > On Thu, Mar 15, 2012 at 02:18:44PM -0400, Denys Dmytriyenko wrote: > > On Thu, Mar 15, 2012 at 10:21:22AM +0100, Martin Jansa wrote: > > > On Thu, Mar 15, 2012 at 05:09:36PM +0800, Kang Kai wrote: > > > > On 2012???03???15??? 16:03, Martin Jansa wrote: > > > > > On Thu, Mar 15, 2012 at 03:40:04PM +0800, Kang Kai wrote: > > > > >> On 2012???03???15??? 14:55, Kang Kai wrote: > > > > >>> On 2012???03???14??? 17:42, Richard Purdie wrote: > > > > >>>> On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: > > > > >>>>> Hi All, > > > > >>>>> > > > > >>>>> I write a script to clean up WORKDIR that remove the obsoleted > > > > >>>>> packages' build directories. > > > > >>>>> The script accept a argument as BUILDDIR and I use this clause to > > > > >>>>> identify the WORKDIR: > > > > >>>>> > > > > >>>>> workdir = os.path.join(builddir, 'tmp/work') > > > > >>>>> > > > > >>>>> Then validate the workdir exists or not. It works for me but hardcode > > > > >>>>> here as Richard point out. > > > > >>>>> So is there a better way to get the WORKDIR here? Thanks. > > > > >>>> I was thinking of something like: > > > > >>>> > > > > >>>> bitbake -e | grep ^WORKDIR > > > > >> And the result is something like that: > > > > >> WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" > > > > >> > > > > >> Is it ok to remove 2 items seperated by slash at the end of string? > > > > >> Right now is: > > > > >> "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" > > > > > Aren't you looking for ^TMPDIR ? > > > > > > > > If use WORKDIR = TMPDIR/"work", it is still hard coding. > > > > > > Assuming 2 items at the end won't work for people using rm_old_work: > > > http://git.openembedded.org/meta-micro/commit/?id=fcf525654915edb9650f1a6c2852f336366f8b2f > > > or slightly different version: > > > http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-shr/classes/rm_old_work.bbclass > > > > Martin, > > > > Can you please point me to more details about this class - any background or > > discussions... Thanks. > > Hi, > > Well it works better then rm_work with sstate and the original class is > from meta-micro (so maybe ask pb if you want more details, but the class > is quite simple). I've just replaced last directory name because of this > issue: > > http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=0d4c17de1ba7343d82bb10c311754e29d573c485 Martin, Hmm, my understanding those are slightly different classes - rm_work cleans WORKDIR after the build to save space, while this rm_old_work seems to clean up before the build. I tried searching for any previous discussions of this class or any other rationale, but even the commit itself doesn't provide much explanation for it... Phil, Do you mind giving a short description of this peculiar rm_old_work class? :) Thanks. -- Denys > > > And I think more people have different "tmp/" part e.g. default would be > > > "tmp-eglibc/" (thanks to TCLIBCAPPEND > > > meta/conf/distro/defaultsetup.conf:TMPDIR .= "${TCLIBCAPPEND}"), but "work" is > > > quite common. > > > > > > meta/conf/bitbake.conf: > > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PF}" > > > meta-shr/classes/rm_old_work.bbclass: > > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${PF}" > > > meta-micro/classes/rm_old_work.bbclass: > > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" > > > > > > Cheers, > > > > > > > > > > > >> Regards, > > > > >> Kai > > > > >> > > > > >>> If get WORKDIR in this way, I'll update the script with no argument > > > > >>> because the argument is useless to identify the WORKDIR. > > > > >>> > > > > >>> Regards, > > > > >>> Kai > > > > >>>> since you already call into bitbake in the script in question. > > > > >>>> > > > > >>>> Cheers, > > > > >>>> > > > > >>>> Richard > > > > >>>> > > > > >>>> > > > > >>> > > > > >>> _______________________________________________ > > > > >>> bitbake-devel mailing list > > > > >>> bitbake-devel@lists.openembedded.org > > > > >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > >> > > > > >> _______________________________________________ > > > > >> bitbake-devel mailing list > > > > >> bitbake-devel@lists.openembedded.org > > > > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > > > > > > > -- > > > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com > > > > > > > > > _______________________________________________ > > > bitbake-devel mailing list > > > bitbake-devel@lists.openembedded.org > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > -- > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-19 20:32 ` Denys Dmytriyenko @ 2012-03-19 21:37 ` Christopher Larson 2012-03-19 21:51 ` Denys Dmytriyenko 0 siblings, 1 reply; 13+ messages in thread From: Christopher Larson @ 2012-03-19 21:37 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: philb, Kang Kai, bitbake-devel, Martin Jansa [-- Attachment #1: Type: text/plain, Size: 6286 bytes --] rm_old_work seems to do exactly what it sounds like. It removes *old* workdirs from previous versions of the recipe to keep it from bloating without bound if you retain the same tmpdir. -- Christopher Larson On Monday, March 19, 2012 at 1:32 PM, Denys Dmytriyenko wrote: > On Fri, Mar 16, 2012 at 07:41:52AM +0100, Martin Jansa wrote: > > On Thu, Mar 15, 2012 at 02:18:44PM -0400, Denys Dmytriyenko wrote: > > > On Thu, Mar 15, 2012 at 10:21:22AM +0100, Martin Jansa wrote: > > > > On Thu, Mar 15, 2012 at 05:09:36PM +0800, Kang Kai wrote: > > > > > On 2012???03???15??? 16:03, Martin Jansa wrote: > > > > > > On Thu, Mar 15, 2012 at 03:40:04PM +0800, Kang Kai wrote: > > > > > > > On 2012???03???15??? 14:55, Kang Kai wrote: > > > > > > > > On 2012???03???14??? 17:42, Richard Purdie wrote: > > > > > > > > > On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > I write a script to clean up WORKDIR that remove the obsoleted > > > > > > > > > > packages' build directories. > > > > > > > > > > The script accept a argument as BUILDDIR and I use this clause to > > > > > > > > > > identify the WORKDIR: > > > > > > > > > > > > > > > > > > > > workdir = os.path.join(builddir, 'tmp/work') > > > > > > > > > > > > > > > > > > > > Then validate the workdir exists or not. It works for me but hardcode > > > > > > > > > > here as Richard point out. > > > > > > > > > > So is there a better way to get the WORKDIR here? Thanks. > > > > > > > > > > > > > > > > > > > > > > > > > > > > I was thinking of something like: > > > > > > > > > > > > > > > > > > bitbake -e | grep ^WORKDIR > > > > > > > And the result is something like that: > > > > > > > WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" > > > > > > > > > > > > > > Is it ok to remove 2 items seperated by slash at the end of string? > > > > > > > Right now is: > > > > > > > "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" > > > > > > > > > > > > > > > > > > > Aren't you looking for ^TMPDIR ? > > > > > > > > > > > > > > > > > > > > > If use WORKDIR = TMPDIR/"work", it is still hard coding. > > > > > > > > Assuming 2 items at the end won't work for people using rm_old_work: > > > > http://git.openembedded.org/meta-micro/commit/?id=fcf525654915edb9650f1a6c2852f336366f8b2f > > > > or slightly different version: > > > > http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-shr/classes/rm_old_work.bbclass > > > > > > > > > > > > > Martin, > > > > > > Can you please point me to more details about this class - any background or > > > discussions... Thanks. > > > > > > > > > Hi, > > > > Well it works better then rm_work with sstate and the original class is > > from meta-micro (so maybe ask pb if you want more details, but the class > > is quite simple). I've just replaced last directory name because of this > > issue: > > > > http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=0d4c17de1ba7343d82bb10c311754e29d573c485 > > Martin, > > Hmm, my understanding those are slightly different classes - rm_work cleans > WORKDIR after the build to save space, while this rm_old_work seems to clean > up before the build. I tried searching for any previous discussions of this > class or any other rationale, but even the commit itself doesn't provide much > explanation for it... > > Phil, > > Do you mind giving a short description of this peculiar rm_old_work class? :) > Thanks. > > -- > Denys > > > > > > And I think more people have different "tmp/" part e.g. default would be > > > > "tmp-eglibc/" (thanks to TCLIBCAPPEND > > > > meta/conf/distro/defaultsetup.conf:TMPDIR .= "${TCLIBCAPPEND}"), but "work" is > > > > quite common. > > > > > > > > meta/conf/bitbake.conf: > > > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PF}" > > > > meta-shr/classes/rm_old_work.bbclass: > > > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${PF}" > > > > meta-micro/classes/rm_old_work.bbclass: > > > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" > > > > > > > > Cheers, > > > > > > > > > > > > > > > > Regards, > > > > > > > Kai > > > > > > > > > > > > > > > If get WORKDIR in this way, I'll update the script with no argument > > > > > > > > because the argument is useless to identify the WORKDIR. > > > > > > > > > > > > > > > > Regards, > > > > > > > > Kai > > > > > > > > > since you already call into bitbake in the script in question. > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > > > > > > > > > Richard > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > bitbake-devel mailing list > > > > > > > > bitbake-devel@lists.openembedded.org (mailto:bitbake-devel@lists.openembedded.org) > > > > > > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > bitbake-devel mailing list > > > > > > > bitbake-devel@lists.openembedded.org (mailto:bitbake-devel@lists.openembedded.org) > > > > > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com (mailto:Martin.Jansa@gmail.com) > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > bitbake-devel mailing list > > > > bitbake-devel@lists.openembedded.org (mailto:bitbake-devel@lists.openembedded.org) > > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > > > > > > > > > > > > > -- > > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com (mailto:Martin.Jansa@gmail.com) > > > > > > > _______________________________________________ > bitbake-devel mailing list > bitbake-devel@lists.openembedded.org (mailto:bitbake-devel@lists.openembedded.org) > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > [-- Attachment #2: Type: text/html, Size: 8267 bytes --] ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: How to identify WORKDIR? 2012-03-19 21:37 ` Christopher Larson @ 2012-03-19 21:51 ` Denys Dmytriyenko 0 siblings, 0 replies; 13+ messages in thread From: Denys Dmytriyenko @ 2012-03-19 21:51 UTC (permalink / raw) To: Christopher Larson; +Cc: philb, Kang Kai, bitbake-devel, Martin Jansa On Mon, Mar 19, 2012 at 02:37:42PM -0700, Christopher Larson wrote: > rm_old_work seems to do exactly what it sounds like. It removes *old* > workdirs from previous versions of the recipe to keep it from bloating > without bound if you retain the same tmpdir. Correct, that's my understanding as well. But it's not meant to replace rm_work, as it can't save space the same way during the build - by the time your build is done, you are using 100% of what WORKDIR would have been w/o this class in the case of a clean build . It prevents the size to grow beyond that point though... I was just trying to clarify this statement, suggesting they both serve the same purpose: > Well it works better then rm_work with sstate -- Denys > On Monday, March 19, 2012 at 1:32 PM, Denys Dmytriyenko wrote: > > > On Fri, Mar 16, 2012 at 07:41:52AM +0100, Martin Jansa wrote: > > > On Thu, Mar 15, 2012 at 02:18:44PM -0400, Denys Dmytriyenko wrote: > > > > On Thu, Mar 15, 2012 at 10:21:22AM +0100, Martin Jansa wrote: > > > > > On Thu, Mar 15, 2012 at 05:09:36PM +0800, Kang Kai wrote: > > > > > > On 2012???03???15??? 16:03, Martin Jansa wrote: > > > > > > > On Thu, Mar 15, 2012 at 03:40:04PM +0800, Kang Kai wrote: > > > > > > > > On 2012???03???15??? 14:55, Kang Kai wrote: > > > > > > > > > On 2012???03???14??? 17:42, Richard Purdie wrote: > > > > > > > > > > On Wed, 2012-03-14 at 17:01 +0800, Kang Kai wrote: > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > > > I write a script to clean up WORKDIR that remove the obsoleted > > > > > > > > > > > packages' build directories. > > > > > > > > > > > The script accept a argument as BUILDDIR and I use this clause to > > > > > > > > > > > identify the WORKDIR: > > > > > > > > > > > > > > > > > > > > > > workdir = os.path.join(builddir, 'tmp/work') > > > > > > > > > > > > > > > > > > > > > > Then validate the workdir exists or not. It works for me but hardcode > > > > > > > > > > > here as Richard point out. > > > > > > > > > > > So is there a better way to get the WORKDIR here? Thanks. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I was thinking of something like: > > > > > > > > > > > > > > > > > > > > bitbake -e | grep ^WORKDIR > > > > > > > > And the result is something like that: > > > > > > > > WORKDIR="/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/x86_64-poky-linux/bblayers-1.0-r0" > > > > > > > > > > > > > > > > Is it ok to remove 2 items seperated by slash at the end of string? > > > > > > > > Right now is: > > > > > > > > "/mnt/sda10/poky-all-platform/build-qemux86_64/tmp/work/" > > > > > > > > > > > > > > > > > > > > > > Aren't you looking for ^TMPDIR ? > > > > > > > > > > > > > > > > > > > > > > > > > If use WORKDIR = TMPDIR/"work", it is still hard coding. > > > > > > > > > > Assuming 2 items at the end won't work for people using rm_old_work: > > > > > http://git.openembedded.org/meta-micro/commit/?id=fcf525654915edb9650f1a6c2852f336366f8b2f > > > > > or slightly different version: > > > > > http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-shr/classes/rm_old_work.bbclass > > > > > > > > > > > > > > > > > Martin, > > > > > > > > Can you please point me to more details about this class - any background or > > > > discussions... Thanks. > > > > > > > > > > > > > Hi, > > > > > > Well it works better then rm_work with sstate and the original class is > > > from meta-micro (so maybe ask pb if you want more details, but the class > > > is quite simple). I've just replaced last directory name because of this > > > issue: > > > > > > http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=0d4c17de1ba7343d82bb10c311754e29d573c485 > > > > Martin, > > > > Hmm, my understanding those are slightly different classes - rm_work cleans > > WORKDIR after the build to save space, while this rm_old_work seems to clean > > up before the build. I tried searching for any previous discussions of this > > class or any other rationale, but even the commit itself doesn't provide much > > explanation for it... > > > > Phil, > > > > Do you mind giving a short description of this peculiar rm_old_work class? :) > > Thanks. > > > > -- > > Denys > > > > > > > > > And I think more people have different "tmp/" part e.g. default would be > > > > > "tmp-eglibc/" (thanks to TCLIBCAPPEND > > > > > meta/conf/distro/defaultsetup.conf:TMPDIR .= "${TCLIBCAPPEND}"), but "work" is > > > > > quite common. > > > > > > > > > > meta/conf/bitbake.conf: > > > > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PF}" > > > > > meta-shr/classes/rm_old_work.bbclass: > > > > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${PF}" > > > > > meta-micro/classes/rm_old_work.bbclass: > > > > > WORKDIR = "${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" > > > > > > > > > > Cheers, > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > Kai > > > > > > > > > > > > > > > > > If get WORKDIR in this way, I'll update the script with no argument > > > > > > > > > because the argument is useless to identify the WORKDIR. > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > Kai > > > > > > > > > > since you already call into bitbake in the script in question. > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > > > > > > > > > > > Richard > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > bitbake-devel mailing list > > > > > > > > > bitbake-devel@lists.openembedded.org (mailto:bitbake-devel@lists.openembedded.org) > > > > > > > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > bitbake-devel mailing list > > > > > > > > bitbake-devel@lists.openembedded.org (mailto:bitbake-devel@lists.openembedded.org) > > > > > > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com (mailto:Martin.Jansa@gmail.com) > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > bitbake-devel mailing list > > > > > bitbake-devel@lists.openembedded.org (mailto:bitbake-devel@lists.openembedded.org) > > > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > > > > > > > > > > > > > > > > > > > -- > > > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com (mailto:Martin.Jansa@gmail.com) > > > > > > > > > > > > > _______________________________________________ > > bitbake-devel mailing list > > bitbake-devel@lists.openembedded.org (mailto:bitbake-devel@lists.openembedded.org) > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel > > > > > > ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2012-03-19 23:01 UTC | newest] Thread overview: 13+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-03-14 9:01 How to identify WORKDIR? Kang Kai 2012-03-14 9:42 ` Richard Purdie 2012-03-15 6:55 ` Kang Kai 2012-03-15 7:40 ` Kang Kai 2012-03-15 8:03 ` Martin Jansa 2012-03-15 9:09 ` Kang Kai 2012-03-15 9:21 ` Martin Jansa 2012-03-15 9:34 ` Kang Kai 2012-03-15 18:18 ` Denys Dmytriyenko 2012-03-16 6:41 ` Martin Jansa 2012-03-19 20:32 ` Denys Dmytriyenko 2012-03-19 21:37 ` Christopher Larson 2012-03-19 21:51 ` Denys Dmytriyenko
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.