Re: [OE-core] why would ASSUME_PROVIDED recipes be built anyway?

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Wed, 2026-04-08 at 06:33 -0700, Robert P. J. Day via lists.openembedded.org wrote:
> 
>   puzzled by something i just noticed ... the documentation for
> "ASSUME_PROVIDED":"
> 
> https://docs.yoctoproject.org/ref-manual/variables.html#term-ASSUME_PROVIDED
> 
> clearly suggests that these represent recipes that would not be built
> as they are already on the host, the example given there is
> "git-native".
> 
>   however, in a walnascar-based build i just built, native recipes
> that were listed in ASSUME_PROVIDED were built anyway, even though
> they are clearly on my Debian 13 host, "git-native" among them. in
> fact, a number of recipes i checked appear to all have been built from
> scratch, despite being listed in ASSUME_PROVIDED.
> 
>   as a test, if i then tried to "cleanall" such a recipe, i got the
> perfectly reasonable:
> 
> 
> $ bitbake -c cleanall git-native
> ... snip ...
> WARNING: Explicit target "git-native" is in ASSUME_PROVIDED, ignoring
> 
> 
> is there some reason that something listed in ASSUME_PROVIDED will be
> fetched and built anyway? is it a version thing?

Some of the recipes have a PROVIDES for XXX-replacement-native and you
can build/depend on that.

Cheers,

Richard