Re: How to identify WORKDIR?

[Kang Kai <Kai.Kang@windriver.com>]

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