Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: making a list of the *fundamental* variables used by image.bbclass
Date: Wed, 7 Jan 2015 09:43:04 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1501070930210.16973@localhost> (raw)


  for class purposes, i want to make a *short* list of the really
fundamental variables used to define the final content of an image as
used by image.bbclass, and i want to know if there's anything i've
missed from this list.

  first, the obvious ones:

  * IMAGE_FEATURES (image features, processed by image.bbclass)
  * IMAGE_INSTALL (names of individual packages)

as i read it, those two variables pretty much define the final content
of the image. i *don't* include things like EXTRA_IMAGE_FEATURES as
that variable is already processed by bitbake.conf before image
processing starts; that is, image.bbclass makes no reference to that
variable, so it's not relevant here.

  other variables that make a smaller difference but still processed
by image.bbclass:

  * ROOTFS_PKGMANAGE
  * SPLASH

  there are also all those *_PROCESS_COMMAND variables (preprocess,
postprocess), but i haven't checked yet which of those are simply
processed within image.bbclass based on the contents of
IMAGE_FEATURES, or possibly something else.

  ah, here's another one:

  * DISTRO_FEATURES

which is tested for processing of systemd/sysvinit. (for similar
reasons, MACHINE_FEATURES is not listed here as all of its processing
is done outside the file.)

  i'm still perusing the file but are there any variables i've
overlooked that are treated as *input* to image.bbclass that control
the final image content? (i'm also ignoring things like fstype-related
variables, not interested in the *format* of the final image, just the
content.)

  so what have i missed?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


                 reply	other threads:[~2015-01-07 14:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.1501070930210.16973@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@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