From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: RFC: Using formfactor data in other recipes
Date: Wed, 16 Oct 2013 14:50:27 +0100 [thread overview]
Message-ID: <2444253.vL4HTbpqxr@helios> (raw)
Hi all,
Andrea has been doing some cleanup on meta-handheld, and he and I have come
across what seems to be a bit of a shortcoming with formfactor over the
variable-based alternative that was used in OE-Classic (MACHINE_GUI_CLASS,
MACHINE_DISPLAY_WIDTH_PIXELS, MACHINE_DISPLAY_HEIGHT_PIXELS etc.). In
meta-opie, the latter variables are still being used in a machine-specific
packagegroup recipe to select the appropriate set of pixmaps to be installed
for each machine based on the screen resolution, so you don't have to have
pixmaps installed that you're never going to use (which would waste storage
space).
formfactor is the current method supported in OE-Core for representing
differences in machine display/input characteristics, however it seems only
queryable at runtime since its files are not written into the sysroot. We could
change it to stage to the sysroot, and therefore the data could be queried at
least at packaging time in other recipes that depend on formfactor. Does this
sound like a reasonable solution for this kind of problem, or is there a
better solution?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2013-10-16 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 13:50 Paul Eggleton [this message]
2013-10-16 13:58 ` RFC: Using formfactor data in other recipes Richard Purdie
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=2444253.vL4HTbpqxr@helios \
--to=paul.eggleton@linux.intel.com \
--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