From: Jian Liu <jian.liu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] archiver.bbclass: fix an exception of the mode configured
Date: Tue, 22 Dec 2015 13:08:33 +0800 [thread overview]
Message-ID: <5678DAD1.9070801@windriver.com> (raw)
In-Reply-To: <564ABBBA.5000408@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Ping
On 2015年11月17日 13:31, Jian Liu wrote:
> Hi Ross,
>
> I check the values of d.getVarFlag('do_configure', 'task') and
> d.getVarFlag('do_unpack', 'task') for gcc-source.
> But it seems that both values are 1.
>
> I use the following command to get the values,
> os.system("echo 'do_unpack=%s, do_configure=%s, noexec=%s, pn=%s' >>
> /tmp/task.txt" %(d.getVarFlag('do_unpack',
> 'task'),d.getVarFlag('do_configure',
> 'task'),d.getVarFlag('do_configure', 'noexec'),pn))
>
> Does I miss something?
>
> I query several people about how to get the current tasks of a recipe.
> But I get nothing more.
>
> Thanks!
> Jian
>
> On 2015年11月16日 23:08, Burton, Ross wrote:
>>
>> On 16 November 2015 at 05:33, Jian Liu <jian.liu@windriver.com
>> <mailto:jian.liu@windriver.com>> wrote:
>>
>> + if d.getVarFlag('do_configure', 'noexec') == '1' or
>> 'do_configure' not in d.getVar('__BBTASKS', False):
>>
>>
>> __BBTASKS is internal so shouldn't beused unless you have an awesome
>> reason. Richard tells me that d.getVarFlag('do_configure', 'task')
>> is probably what you want.
>>
>> Ross
>
>
>
[-- Attachment #2: Type: text/html, Size: 2735 bytes --]
next prev parent reply other threads:[~2015-12-22 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 5:33 [PATCH] archiver.bbclass: fix an exception of the mode configured Jian Liu
2015-11-16 15:08 ` Burton, Ross
2015-11-17 5:31 ` Jian Liu
2015-12-22 5:08 ` Jian Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-13 10:09 Jian Liu
2015-11-16 5:17 ` Jian Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5678DAD1.9070801@windriver.com \
--to=jian.liu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.