From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] bitbake-layers: stop the warning "not been run using the bitbake wrapper..."
Date: Fri, 10 Jun 2011 13:45:11 +0100 [thread overview]
Message-ID: <201106101345.11050.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <1307708964.15712.210.camel@rex>
On Friday 10 June 2011 13:29:24 Richard Purdie wrote:
> We can't add implementation specific information to bitbake I'm afraid
> so we'll need to find a different way to handle this...
Perhaps we could just change sanity.bbclass to check argv[0] somehow (or some
equivalent way to get the current process name) and skip the check if it isn't
"bitbake"? This would have the added bonus of solving the problem for future
tools that use bitbake code in a similar way to bitbake-layers.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-10 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 8:18 [PATCH 0/1] bitbake-layers: stop the warning 'not been run using the bitbake wrapper...' Dexuan Cui
2011-06-10 8:18 ` [PATCH 1/1] bitbake-layers: stop the warning "not been run using the bitbake wrapper..." Dexuan Cui
2011-06-10 12:29 ` Richard Purdie
2011-06-10 12:45 ` Paul Eggleton [this message]
2011-06-20 4:26 ` Cui, Dexuan
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=201106101345.11050.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
/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.