From: "Eric Bénard" <eric@eukrea.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: SRC_URI computing order
Date: Mon, 4 Nov 2013 09:33:59 +0100 [thread overview]
Message-ID: <20131104093359.4d958b8b@e6520eb> (raw)
In-Reply-To: <CAAQYJAvvqEByKQRPKRZviqPJmSrDqYt1PvnYPxeJuOSuKO-HaA@mail.gmail.com>
Hi Andrea,
Le Sun, 3 Nov 2013 23:16:09 +0100,
Andrea Adami <andrea.adami@gmail.com> a écrit :
> 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.
>
isn't that problem fixed by cherry-picking commit
92cbf7eeea553bfa24c7081473fa8bc4ebc1f552 in oe-core ?
Eric
next prev parent reply other threads:[~2013-11-04 8:34 UTC|newest]
Thread overview: 20+ 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-04 22:13 ` [OE-core] " Andrea Adami
2013-11-06 8:45 ` Andrea Adami
2013-11-06 8:45 ` [OE-core] " Andrea Adami
2013-11-07 23:20 ` Richard Purdie
2013-11-07 23:20 ` [OE-core] " Richard Purdie
2013-11-08 11:55 ` Otavio Salvador
2013-11-08 11:55 ` [OE-core] " Otavio Salvador
2013-11-04 8:33 ` Eric Bénard [this message]
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=20131104093359.4d958b8b@e6520eb \
--to=eric@eukrea.com \
--cc=andrea.adami@gmail.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 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.