[yocto] Building two initramfs images

[Amol Lad]

Hi,

I want to build two initramfs images when building core-image-minimal. First initramfs gets bundled with kernel and available after build. This is all good.

Now, how to include second initramfs image also in core-image-minimal? It will be standalone initramfs image i.e. it won't be bundled with kernel. If I specify this recipe in local.conf in CORE_IMAGE_EXTRA_INSTALL or IMAGE_INSTALL_append then I get below error:

"Task do_populate_sdk in core-image-minimal.bb rdepends upon non-existent task do_package_write_rpm in second-initramfs-image.bb"

I can build second-initramfs-image.bb with command "bitbake second-initramfs-image" but I want this to get build automatically when I build core-image-minimal. Please advise

second-initramfs-image.bb:

DESCRIPTION = "Second initramfs"

PACKAGE_INSTALL = " \
        base-files \
        base-passwd \
        busybox \
        sysvinit \
        initscripts \
        ${ROOTFS_BOOTSTRAP_INSTALL} \
    "
# Do not pollute the initrd image with rootfs features
# Enable 'debug-tweaks'. This provides empty root password
IMAGE_FEATURES = "debug-tweaks"

export IMAGE_BASENAME = "second-initramfs-image"
IMAGE_LINGUAS = ""

LICENSE = "MIT"

IMAGE_FSTYPES = "cpio.gz"
inherit core-image

IMAGE_ROOTFS_SIZE = "8192"
IMAGE_ROOTFS_EXTRA_SPACE = "0"

BAD_RECOMMENDATIONS += "busybox-syslog"
________________________________
The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180905/5e83da0a/attachment.html>