[OE-core] Why does building an image for machine X delete the bootloader for machine Y?

[Gary Thomas]

On 2014-11-26 01:19, Mike Looijmans wrote:
> I do a:
>
> MACHINE=X bitbake my-image
>
> This DEPENDS on a virtual bootloader, which will produce a BOOT.BIN file in the deploy directory, which is tmp-glibc/deploy.images/X/
>
> If I then do a:
>
> MACHINE=Y bitbake my-image
>
> the BOOT.BIN in tmp-glibc/deploy.images/X/ is suddenly gone!
>
> If i do a
>
> MACHINE=X bitbake my-image
>
> then the the BOOT.BIN in tmp-glibc/deploy.images/Y/ is suddenly gone, and the one for the X machine appears again. The bootloader recipe is not being rebuilt at all.
>
> The machines have the same MACHINE_ARCH, they differ on only minor points (the FPGA).
>
> What is going on here?
>

What machines are you building for?  I've built for two different
i.MX6 platforms in the same build tree and I don't see this behaviour.
n.b. this was using the latest master Poky/Yocto

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------