From: Richard Purdie <rpurdie@rpsys.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: how to properly use "EXTRA_ASSUME_PROVIDED"?
Date: Wed, 25 Jul 2012 22:21:01 +0100 [thread overview]
Message-ID: <1343251261.29991.4.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1207251558160.15120@oneiric>
On Wed, 2012-07-25 at 16:06 -0400, Robert P. J. Day wrote:
> what is the proper way to use EXTRA_ASSUME_PROVIDED, and is the
> effect of that visible in the bitbake environment?
>
> as in, based on the current version of bitbake.conf, i can see this
> with "bitbake -e":
>
> ASSUME_PROVIDED="bzip2-native git-native grep-native diffstat-native
> patch-native perl-native-runtime python-native-runtime tar-native
> virtual/libintl-native"
>
> if i add the following silliness to my local.conf,
>
> ASSUME_PROVIDED += "rday-native"
>
> i can see that in the env as well:
>
> ASSUME_PROVIDED="bzip2-native git-native grep-native diffstat-native
> patch-native perl-native-runtime python-native-runtime tar-native
> virtual/libintl-native rday-native"
>
> but is it correct to run the following:
>
> $ bitbake -I EXTRA_ASSUME_PROVIDED="rday-native" -e core-image-minimal
>
> and if it is, should i be able to verify that anywhere in the
> environment? doesn't seem so. from bitbake/lib/bb/cooker.py, it
> looks like whatever i put there is being processed thusly:
>
> ignore = self.configuration.data.getVar("ASSUME_PROVIDED", True) or ""
> self.status.ignored_dependencies = set(ignore.split())
>
> for dep in self.configuration.extra_assume_provided:
> self.status.ignored_dependencies.add(dep)
>
> so is there any way to see that? thanks.
Where did you come to believe EXTRA_ASSUME_PROVIDED did anything?
Cheers,
Richard
next prev parent reply other threads:[~2012-07-25 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 20:06 how to properly use "EXTRA_ASSUME_PROVIDED"? Robert P. J. Day
2012-07-25 21:21 ` Richard Purdie [this message]
2012-07-26 0:10 ` Robert P. J. Day
2012-07-26 7:37 ` Richard Purdie
2012-07-26 10:57 ` Robert P. J. Day
2012-07-26 11:18 ` Richard Purdie
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=1343251261.29991.4.camel@ted \
--to=rpurdie@rpsys.net \
--cc=openembedded-core@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.