From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Lianhao Lu <lianhao.lu@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/1] Add new option --environment-more
Date: Thu, 23 Feb 2012 14:57:02 +0000 [thread overview]
Message-ID: <1330009022.32110.61.camel@ted> (raw)
In-Reply-To: <cover.1329986451.git.lianhao.lu@intel.com>
On Thu, 2012-02-23 at 16:49 +0800, Lianhao Lu wrote:
> This patch adds a new option --environment-more to bitbake to display
> additional file dependency information. This kind of information can be used
> by other recipe editors, e.g. the Eclipse bitbake commander plugin, to decide
> when to reparse the recipes.
>
> The following changes since commit d8b3718303c3d56394c722059f1a73bd79131d0a:
> Zhai Edwin (1):
> texi2html: Fix for multilib
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib llu/bitbake_showmore
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=llu/bitbake_showmore
>
> Lianhao Lu (1):
> bitbake: Add new otpion --environment-more
Rather than add a new option specifically for this, I'm tempted just to
add the variables to the -e output...
The trouble is that variables starting "__" are considered internal use
by bitbake. Would it work if we merge __base_depends and __depends and
print this as some specific variable like BBINCLUDES ? I can imagine
that being useful elsewhere too and we don't expose the internal split
of the variable that way...
Cheers,
Richard
next prev parent reply other threads:[~2012-02-23 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 8:49 [PATCH 0/1] Add new option --environment-more Lianhao Lu
2012-02-23 8:49 ` [PATCH 1/1] bitbake: Add new otpion --environment-more Lianhao Lu
2012-02-23 14:57 ` Richard Purdie [this message]
2012-02-24 3:06 ` [PATCH 0/1] Add new option --environment-more Lu, Lianhao
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=1330009022.32110.61.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=lianhao.lu@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.