From: Khem Raj <raj.khem@gmail.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] conf/layer.conf: Use .= for BBPATH and += for BBFILES
Date: Thu, 5 May 2011 22:55:35 -0700 [thread overview]
Message-ID: <24D4CC37-BBEC-4725-9EB4-007831040D17@gmail.com> (raw)
In-Reply-To: <iq01ip$n8v$1@dough.gmane.org>
-Khem
On May 5, 2011, at 10:39 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 06-05-11 05:47, raj.khem@gmail.com wrote:
>> From: Khem Raj <raj.khem@gmail.com>
>
>
>> # We have a conf and classes directory, prepend to BBPATH to prefer our versions
>> -BBPATH := "${LAYERDIR}:${BBPATH}"
>> +BBPATH .= ":${LAYERDIR}"
>
> I haven't had my morning coffee yet, but that either doesn't prepend
> LAYERDIR to BBPATH or the colons are in the wrong place.
>
Hmm I have sent similar patch for oe-core, git am that too and for other layers as well
Now bit bake should arrange BBPATH per priority
>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFNw4mZMkyGM64RGpERAsNyAJ9UJ4GJ6blWQaYpCRO6s2v9N55jDQCdHeoR
> gGUq5MZHntHS6d42OzHwjCM=
> =G4SQ
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2011-05-06 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 3:47 [meta-oe][PATCH] conf/layer.conf: Use .= for BBPATH and += for BBFILES raj.khem
2011-05-06 5:39 ` Koen Kooi
2011-05-06 5:55 ` Khem Raj [this message]
2011-05-06 7:29 ` Phil Blundell
2011-05-06 19:59 ` Khem Raj
2011-05-06 21:25 ` Koen Kooi
2011-05-06 23:09 ` Khem Raj
2011-05-07 6:49 ` Koen Kooi
2011-05-07 8:11 ` 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=24D4CC37-BBEC-4725-9EB4-007831040D17@gmail.com \
--to=raj.khem@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 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.