[meta-freescale] mfgtool-initramfs-image.bbclass conflict with other layers

[Mirza Krak]

Hi.

My first post on this list, be gentle :).

I am running morty branch and trying to build for "colibri-vf" target.

Here is my setup:
meta
meta-poky
meta-yocto-bsp    = "morty:5aa481dfedfd089f0d6e8a3bae1b84134d5dff4c"
meta-freescale    = "morty:6ec09e6a0f09d1cb9c3761b339590c0a0baeeeb3"
meta-fsl-arm      = "master:154ccf1e8b08e3d6219bd455b7dfe9ff7ab975b0"
meta-fsl-arm-extra = "morty:69ed94bb781a9c1bfbba4fb3026e4cbf3a194878"
meta-toradex-bsp-common = "morty-next:ad286efa19257f83985f5f5844a2d500118e40ef"
meta-toradex-nxp  = "morty-next:06d4bf9c8b936976d2469b50680a2bbb53cb6f54"
meta-mender-core  = "master:10b22602b5a3a8615fcb58b55ae8191712365cf6"
oe-meta-go        = "master:fbd51ce7e5acaf1ec298a384f1b3fb791ee7483a"

And I am running in to a parse error but I can not determain which
layer is to blame.

In meta-mender-core there is a file called mender-image.bbclass that
does following:
IMAGE_CLASSES += "mender-sdimg mender-artifactimg"
IMAGE_FSTYPES_append = " sdimg mender"

But when I run "bitbake <image>" I get the following error:
ERROR: /home/mirzak/project/mender.io/ubifs-support/layers/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb:
No IMAGE_CMD defined for IMAGE_FSTYPES entry 'mender' - possibly
invalid type name or missing support class
ERROR: /home/mirzak/project/mender.io/ubifs-support/layers/meta-freescale/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb:
No IMAGE_CMD defined for IMAGE_FSTYPES entry 'mender' - possibly
invalid type name or missing support class
ERROR: Failed to parse recipe:
/home/mirzak/project/mender.io/ubifs-support/layers/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb

Now looked at fsl-image-mfgtool-initramfs.bb and it does modify IMAGE_CLASSES.

I changed the following line:
    IMAGE_CLASSES = "image_types_uboot"
to
    IMAGE_CLASSES += "image_types_uboot"

And then everything is fine again, no parse error and it starts to build.

I thought that this could be a layer priority issue but it seems that
it is in order for me.