On Mon, Jul 22, 2019 at 2:05 AM Gabriele Zampieri
wrote:
>
> Hi Patrick,
>
> thank you for the clarification.
> I have no idea on how to encapsulate the output of bitbake into another image
> in a nice and clean way. I'm pretty sure that you must run two separate
> bitbake, one per MACHINE.
>
On Fri, Jul 19, 2019 at 10:03 AM Gabriele Zampieri
wrote:
>> 2. My new image going to be used as an installation image for my
>> production image. So I need to include the production image (for
>> MACHINE="mymachine")) deploy products in the image for my installation
>> image. How can I do that
Hi Patrick,
Do I have to replicate (and maintain) all of the references to
> mymachine to also refer to my newly defined "installationmachine"? Or
> can I tell Bitbake that "installationmachine" is the same as
> "mymachine", and just add/change new stuff for "installationmachine"?
>
I would
On Fri, Jul 19, 2019 at 1:58 AM Gabriele Zampieri
wrote:
>
> Hi,
>
> you could define two machines, where the manufacturing one is just an overlay
> of the production one. If the two kernels differs only for their config, you
> can specify different defconfig based on machine. If you need a
Hi,
you could define two machines, where the manufacturing one is just an
overlay of the production one. If the two kernels differs only for their
config, you can specify different defconfig based on machine. If you need a
completely different kernel, just specify
Hello All,
I have a situation where I need to build an image for my machine with
a different kernel than is specified by
PREFERRED_PROVIDER_virtual/kernel. But I also need to build the
default kernel. This is for a "manufacturing" image which will
include the full production image, and then some
