On Sun, 2021-07-04 at 10:59 +0200, Peter Bergin wrote:

On 2021-07-03 16:55, Mittal, Anuj wrote:

quoted

On Fri, 2021-07-02 at 13:59 +0200, Peter Bergin wrote:

quoted

This reverts commit 10aa1291979fb90bed1beb49be4d406ed0e1e4d5.

As there is no build dependency between libubootenv and the
configuration
of u-boot there is no reason to check for UBOOT_CONFIG or UBOOT_MACHINE
by adding the class uboot-config. Revert this in order to remove
useless
workaround in bsp layer (meta-freescale).

This was added to address failures in world builds:

https://lists.openembedded.org/g/openembedded-core/message/141757

If this is not required, then I think we'd need to address those
failures.

Thanks for the pointer about the reason for this patch. I searched a bit 
but could not find it.

Can you please help me define 'world builds'?

"bitbake world"

i.e. build everything

By reading the mail thread my thoughts are that the obvious thing is 
that the build has a bad configuration as u-boot is skipped. This should 
be the thing to solve.

Not every MACHINE will support u-boot or have a configuration for it.

Do we have other examples in oe-core where we have a RRECOMMENDS and a 
requirement that another package is built. Isn't RDEPENDS used for that 
case?

RDEPENDS is a hard requirement, RRECOMMENDS is a "soft" one. Bitbake
treats them the same in the sense it will always follow them, the destinction
is left to the package manager at the root filesystem creation time.

Cheers,

Richard