From: Patrick Ohly <patrick.ohly@intel.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: yocto@yoctoproject.org
Subject: Re: How do you remove an IMAGEFS?
Date: Tue, 27 Jun 2017 09:58:54 +0200 [thread overview]
Message-ID: <1498550334.7464.21.camel@intel.com> (raw)
In-Reply-To: <E68186D16557413C961C4DA89EF49E84@PAULD>
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.
next prev parent reply other threads:[~2017-06-27 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 23:21 How do you remove an IMAGEFS? Paul D. DeRocco
2017-06-27 7:58 ` Patrick Ohly [this message]
2017-06-27 19:08 ` Paul D. DeRocco
2017-06-27 19:28 ` Patrick Ohly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1498550334.7464.21.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=pderocco@ix.netcom.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.