From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: the awkwardness of using core-image.bbclass
Date: Fri, 11 Jul 2014 18:30:19 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407111829140.7344@localhost> (raw)
In-Reply-To: <CA+gsK-qzcd3fa=N1pUw3z46mP8DjP0V7sW3k8z79id2o3AtLsw@mail.gmail.com>
On Fri, 11 Jul 2014, Rudolf Streif wrote:
> Hi Robert,
>
>
>
> > some observations/questions on core-image.bbclass, and whether it
> > can be used more understandably. this is being written from the
> > perspective of someone who has had the occasional student ask, "why
> > was it done *that* way?"
> >
> > so here's the important part of core-image.bbclass:
> >
> > CORE_IMAGE_BASE_INSTALL = '\
> > packagegroup-core-boot \
> > packagegroup-base-extended \
> > \
> > ${CORE_IMAGE_EXTRA_INSTALL} \
> > '
> >
> > CORE_IMAGE_EXTRA_INSTALL ?= ""
> >
> > IMAGE_INSTALL ?= "${CORE_IMAGE_BASE_INSTALL}"
> >
> > inherit image
> >
> > whose job is obviously to define the final contents in IMAGE_INSTALL
> > to be handed off to image.bbclass. so far, so good. but notice first
> > that while IMAGE_INSTALL and CORE_IMAGE_EXTRA_INSTALL are weakly
> > assigned, CORE_IMAGE_BASE_INSTALL is *not*, which -- if one is
> > perusing that file -- strongly suggests that if you're inheriting
> > from this class file, you really should use that value. but it doesn't
> > work that way.
> >
> > Consider CORE_IMAGE_BASE_INSTALL as a default value for IMAGE_INSTALL.
> It's internal to the core-image class only. Hence, it makes sense for it to
> be directly assigned. It is not meant to be used by any other classes or
> recipes. With the default value the most simple recipe you can write to use
> the core-image class is:
>
> myimage.bb:
> inherit core-image
>
> which will produce an image that boots to the console and include
> hardware support if so defined by machine and distro features.
>
> IMAGE_INSTALL and CORE_IMAGE_EXTRA_INSTALL are meant to be
> overwritten by image recipes and configuration files.
i know, which is exactly what is so counter-intuitive with the way
the above is done. you can override those two variables, but not
CORE_IMAGE_BASE_INSTALL directly, it just seems silly.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-07-11 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 16:51 the awkwardness of using core-image.bbclass Robert P. J. Day
2014-07-11 17:56 ` Rudolf Streif
2014-07-11 22:30 ` Robert P. J. Day [this message]
2014-07-12 5:06 ` Khem Raj
2014-07-12 9:53 ` Robert P. J. Day
2014-07-14 9:34 ` Paul Eggleton
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=alpine.LFD.2.11.1407111829140.7344@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox