[yocto] How do you remove an IMAGEFS?

Patrick Ohly patrick.ohly at intel.com
Tue Jun 27 00:58:54 PDT 2017


On Fri, 2017-06-23 at 16:21 -0700, Paul D. DeRocco wrote:
> x86-base.inc adds "live" to IMAGE_FSTYPES. I have no need for a live
> image, or an iso, so I thought adding IMAGE_FSTYPES_remove = "live iso" to
> my image recipe might work, but it complained in do_bootimg that my recipe
> "depends upon non-existent task do_image_ext4". On a hunch, I movved the
> IMAGE_FSTYPES_remove to before inheriting core-image,

That's the only feasible approach at the moment. IMAGE_FSTYPES gets
checked while inheriting the class and then triggers inheriting
image-live.bbclass even when the "live" type gets removed later one.

There's a patch for x86-base.inc which removes this unconditional
extension of IMAGE_FSTYPES, see "[OE-core] [PATCH] x86-base.inc: Don't
add live to IMAGE_FSTYPES, default instead".

>  and then it didn't
> complain, but it didn't build ANY images.

You still need to set some kind of IMAGE_FSTYPES, for example "wic".

Further hacks may be needed depending on your version of OE-core, for
example inheriting the class set by EFI_PROVIDER.

Here's how we solved this in refkit:
https://github.com/intel/intel-iot-refkit/blob/0ec24f348453/meta-refkit-core/classes/refkit-image.bbclass#L219

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.






More information about the yocto mailing list