From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>,
openembedded-core <Openembedded-core@lists.openembedded.org>
Subject: Re: SRC_URI computing order
Date: Thu, 07 Nov 2013 23:20:18 +0000 [thread overview]
Message-ID: <1383866418.6271.288.camel@ted> (raw)
In-Reply-To: <CAAQYJAttXLv8jQczSLU=8C9iw6z9JS6xbOrOiB7ahaowzLWx8g@mail.gmail.com>
On Wed, 2013-11-06 at 09:45 +0100, Andrea Adami wrote:
> On Mon, Nov 4, 2013 at 11:13 PM, Andrea Adami <andrea.adami@gmail.com> wrote:
> > On Mon, Nov 4, 2013 at 12:10 AM, Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> >> On Sun, 2013-11-03 at 23:16 +0100, Andrea Adami wrote:
> >>> I have to report an undesiderate behavior:
> >>>
> >>> the formfactor files in our .bbappend are not considered :/
> >>> DEBUG: Searching for machconfig in paths:....
> >>> /oe/oe-core/meta/recipes-bsp/formfactor/formfactor-0.0/
> >>> /oe/oe-core/meta/recipes-bsp/formfactor/formfactor/
> >>> /oe/oe-core/meta/recipes-bsp/formfactor/files/
> >>> /oe/meta-handheld/recipes-bsp/formfactor/files/poodle
> >>>
> >>> so we end up with the empty machconfig of
> >>> /oe/oe-core/meta/recipes-bsp/formfactor/files/
> >>>
> >>> Surely this didn't happen when we tested the recipe.
> >>
> >> With which revision of OE-Core? Was this with the dora release tag,
> >> current dora head or master?
> >>
> >> Cheers,
> >>
> >> Richard
> >>
> >>
> >
> > This was with fresh master:
> >
> > Build Configuration:
> > BB_VERSION = "1.21.0"
> > BUILD_SYS = "i686-linux"
> > NATIVELSBSTRING = "Gentoo"
> > TARGET_SYS = "arm-oe-linux-gnueabi"
> > MACHINE = "poodle"
> > DISTRO_VERSION = "oe-core.0"
> > TUNE_FEATURES = "armv5 thumb dsp"
> > TARGET_FPU = "soft"
> > meta = "master:511b4194165ed7a5645169e09c27db280d5a5316"
> > meta-initramfs = "master:4d62e7f575e2a87197c74ab4639561b45eec0e60"
> > meta-handheld = "master:55a310666b543e6beca47fa3c197492d5a6cf8ff"
> >
> > Cheers
> FYI
> In the hurry for a solution for fixing formfactor and ipaq-boot-params
> my quick hack was to revert
>
> http://cgit.openembedded.org/openembedded-core/commit/meta?id=92cbf7eeea553bfa24c7081473fa8bc4ebc1f552
>
> That appears to fix the specific issue...
Its a hacky workaround. The real issue is that you don't set DISTRO and
this puts a :: into FILESOVERRIDES (and OVERRIDES). I've sent a patch
out which sets a default for DISTRO since its the nicer way I could find
to fix this. The behaviour in the above patch is correct.
Cheers,
Richard
next prev parent reply other threads:[~2013-11-07 23:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 22:42 [PATCH] utils.bbclass: Fix override ordering for FILESPATH Richard Purdie
2013-10-28 14:10 ` SRC_URI computing order Eric Bénard
2013-10-29 3:45 ` Khem Raj
2013-10-29 7:28 ` Eric Bénard
2013-10-30 15:15 ` Richard Purdie
2013-11-02 8:47 ` Eric Bénard
2013-11-03 22:16 ` Andrea Adami
2013-11-03 23:10 ` Richard Purdie
2013-11-04 22:13 ` Andrea Adami
2013-11-06 8:45 ` Andrea Adami
2013-11-07 23:20 ` Richard Purdie [this message]
2013-11-08 11:55 ` Otavio Salvador
2013-11-04 8:33 ` Eric Bénard
2013-11-01 15:36 ` Eric Bénard
2013-11-01 18:16 ` Richard Purdie
2013-11-02 8:45 ` Eric Bénard
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=1383866418.6271.288.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=andrea.adami@gmail.com \
--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