[yocto] How to generate cpio.gz AND cpio.gz.u-boot image from single recipe?

[Khem Raj]

Please open a bugzilla entry for it

On Mon, Aug 14, 2017 at 6:11 AM Michal Vokáč <michal.vokac at ysoft.com> wrote:

> On 11.8.2017 18:31, Khem Raj wrote:
> > On Fri, Aug 11, 2017 at 5:52 AM, Vokáč Michal <Michal.Vokac at ysoft.com>
> wrote:
> >> Hi,
> >>
> >> I am in a process of upgrading our project from Jethro to Morty.
> >> For a while I am trying to solve an issue with generating initramfs
> images.
> >>
> >> We have an image recipe that says:
> >>
> >> IMAGE_FSTYPES = "tar.bz2 cpio.gz cpio.gz.u-boot"
> >> inherit core-image
> >> inherit image_types_uboot
> >>
> >> With the Jethro branch of the openembedded-core layer all thee defined
> image types are generated.
> >>
> >> After upgrade to Morty, the cpio.gz image is deleted somewhere in the
> process of generating
> >> the cpio.gz.u-boot image (which is probably the right behavior of
> image_types_uboot.bbclass).
> >>
> >> I wonder why it worked before and how to make it work again, properly.
> >
> > it is intentional. See
> >
> https://github.com/01org/luv-yocto/commit/09a5cb0cca109395a4835e25d483019ddd5e773c
> >
>
> Thank you Raj, that explain why the gziped image is being removed.
>
> I still need to figure out, how to produce both image types from one
> recipe.
> Lets imagine I went through these steps.
>
>    1. I set up the recipe so that the tar.bz2 and cpio.gz images are
> generated.
>
>    IMAGE_FSTYPES = "tar.bz2 cpio.gz"
>    inherit core-image
>
>    The tar is just for development debugging and the cpio.gz is packed into
>    a FIT image that goes into production.
>
>    2. After some unspecified time a need arose to produce also
>    the cpio.gz.u-boot image that can be loaded manually in U-Boot during
> development.
>
>    I changed the recipe like this:
>
>    IMAGE_FSTYPES = "tar.bz2 cpio.gz cpio.gz.u-boot"
>    inherit core-image
>    inherit image_types_uboot
>
>  From my point of view, the image_types_uboot class is removing
> the cpio.gz image that was generated by someone else.
> In my situation it is not "a middle file" as the commit you referenced
> says.
>
> I would understand that the cpio.gz is removed when it is not stated in
> the IMAGE_FSTYPES variable.
>
>  From reading the IMAGE_FSTYPES variable documentation a user/developer
> can never
> get the idea that some image types can not be generated simultaneously.
> IMHO a proper behavior would be to generate and preserve all supported
> image
> types stated in the IMAGE_FSTYPES variable.
>
> Any ideas how to achieve that?
>
> ________________________________
>
> CONFIDENTIALITY NOTICE
> This message is for the named person's use only. It may contain
> confidential, proprietary or legally privileged information.
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to info at ysoft.com with a copy of this message. You must not,
> directly or indirectly, use, disclose, distribute, print or copy any part
> of this message if you are not the intended recipient. Y Soft and any of
> its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
> Y Soft is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection Y Soft does not accept liability.
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170814/e853d91d/attachment.html>