From: Ulf Samuelsson <openembedded-core@emagii.com>
To: openembedded-core@lists.openembedded.org,
Angstrom-distro-devel@linuxtogo.org
Subject: Using the correct "xserver-xf86-config_0.1.bbappend
Date: Mon, 21 Oct 2013 18:30:41 +0200 [thread overview]
Message-ID: <526556B1.2010908@emagii.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Trying to build a systemd-gnome-image raspberrypi under Angstrom, with a
few extra layers.
This fails on "xserver-xf86-config_0.1.[bb|bbappend]"
The extra layer has BBPRIORITY = 20.
meta-beagleboard has BBPRIORITY = 8
meta-raspberrypi has BBPRIORITY = 6 (later changed to 120)
BBLAYERS are in the order meta-<extra layer> meta-beagleboard
meta-raspberrypi
It looks like bitbake will select the bbappend in the layer with the
highest priority,
even if that contains a COMPATIBLE_MACHINE clause, which does not
include the current MACHINE.
/Is there any way to make bitbake select the correct bbappend file
without modifying the BBPRIORITY? /
--------------------------------------------------------------------------------------------
Looks like the xserver-xf86-config for the raspberry-pi fails on
*SRC_URI_append_raspberrypi = " file://xorg.conf.d/*"**
*
When I change to:
*SRC_URI_append_raspberrypi = " file://xorg.conf.d/10-evdev.conf "*
the raspberry pi version completes.
/Wildcards are not allowed?/
--
Best Regards
Ulf Samuelsson
eMagii
[-- Attachment #2: Type: text/html, Size: 1736 bytes --]
next reply other threads:[~2013-10-21 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 16:30 Ulf Samuelsson [this message]
2013-10-21 20:21 ` Using the correct "xserver-xf86-config_0.1.bbappend Khem Raj
2013-10-21 23:28 ` Ulf Samuelsson
2013-10-22 5:13 ` Paul Eggleton
2013-10-22 5:17 ` Khem Raj
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=526556B1.2010908@emagii.com \
--to=openembedded-core@emagii.com \
--cc=Angstrom-distro-devel@linuxtogo.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ulf@emagii.com \
/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.