[bitbake-devel] [PATCH 1/1] cooker.py: Remove explicit build targets from the ignored list

Peter Seebach peter.seebach at windriver.com
Thu Aug 9 17:44:25 UTC 2012


On Thu, 9 Aug 2012 18:30:57 +0100
Paul Eggleton <paul.eggleton at linux.intel.com> wrote:

> I'd rather we not change it to behave this way - the better approach
> would seem to me to be to just print a warning that the requested
> target is in ASSUME_PROVIDED and then not do anything else; if the
> user really wants to build the thing they can just remove it from
> ASSUME_PROVIDED.

Removing things from ASSUME_PROVIDED can be a bit tricky, because they
can come from more than one place. And it may not be easy to see where
they came from. (In my most convenient build, there are at least two
files setting ASSUME_PROVIDED.)

> If there is a genuine need to be able to force an item in
> ASSUME_PROVIDED to be built I'd probably want to hear a bit more
> background.

I think it's not so much that there's a need, as that an explicit
statement should win over an assumption.

Analogy time!  Which is a better response to "-O2 -fno-inline":
1. Error message explaining that -O2 implied -finline, so you can't
do that.
2. The explicit flag overrides the flags implied by -O2.

I think of ASSUME_PROVIDED as meaning "if something thinks it needs
this, assume it's already available". So don't build it by-implication,
for instance as a dependency. Thus the name "ignored_dependencies".
Things specified by the user on the command line aren't dependencies,
though. They're explicit requests, and I think those should win. That
said... It might make sense to add a:

bb.note("Explicit target '%s' overriding ASSUME_PROVIDED." % foo)

so that people are aware that they are doing something unusual.

The specific case that got me looking at this actually involved the
bitbake -e feature, and on the one hand, seeing no output was
confusing, on the other hand, a diagnostic warning me that Something
Strange was involved would actually have been pretty informative.

-s
-- 
Listen, get this.  Nobody with a good compiler needs to be justified.




More information about the bitbake-devel mailing list