All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@emagii.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Discussion of the angstrom distribution development
	<Angstrom-distro-devel@linuxtogo.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Using the correct "xserver-xf86-config_0.1.bbappend
Date: Tue, 22 Oct 2013 01:28:07 +0200	[thread overview]
Message-ID: <5265B887.2060505@emagii.com> (raw)
In-Reply-To: <CAMKF1sqtist2BpszV5AYEids7kYnWxxfu=becBYiAUaQs=PBpg@mail.gmail.com>

On 2013-10-21 22:21, Khem Raj wrote:
> Ulf
>
> On Mon, Oct 21, 2013 at 9:30 AM, Ulf Samuelsson
> <openembedded-core@emagii.com> wrote:
>> 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,
> Not really. All bbappends are selected the order or sequence of them
> is governed by how the layers line up in BBPATH
Hm, it seemed to work if I increased the BBPRIORITY.

Either method seems to be problematic.

If you build for a certain machine, then you want to define which 
bbappend to use
regardless of BBPATH or BBPRIORITY.

Maybe bitbake needs to know which meta-layer contains the <machine>.conf,
and always select a bbappend in that layer, over bbappends in other layers.

Otherwise you have to edit bblayer.conf every time you want to switch to 
a new machine,
which I think is undesirable.




>> 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?
> This is a question of fundamental bitbake semantics/syntax for SRC_URI
> and nothing to do with bbappends. and I dont think wildcards in
> SRC_URI are reliable, so better be explicit about them.

Yes, since this problem occured at the same time,
I thought that I'd mention it as well.
Basically the any image build for raspberry pi involving X is broken then.
/Ulf


>
>> --
>> Best Regards
>> Ulf Samuelsson
>> eMagii
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>


-- 
Best Regards
Ulf Samuelsson
ulf@emagii.com
+46 722 427437



  reply	other threads:[~2013-10-21 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 16:30 Using the correct "xserver-xf86-config_0.1.bbappend Ulf Samuelsson
2013-10-21 20:21 ` Khem Raj
2013-10-21 23:28   ` Ulf Samuelsson [this message]
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=5265B887.2060505@emagii.com \
    --to=ulf@emagii.com \
    --cc=Angstrom-distro-devel@linuxtogo.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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.