Ulf,
I'm not quite sure what you mean.
I've understood that layers (read layer.conf files) are scanned through
using locations and order found in BBLAYERS variable set in bblayers.conf
file. BBPATH is initialized in bblayers.conf as ${TOPDIR}. Thereafter (my
wild guess) BBPATH is appended (or prepe
Hello.
We are looking at using Angstrom and bitbake. There are several areas
where we could use an expert that could both consult on questions and
approaches as well as help implement some of the customization that we
may need to ship product.
This might start out as a several hour contract, phon
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 (722) 427 437
23 okt 2013 kl. 18:30 skrev Björn Krombholz :
> On 10/20/2013 09:04 PM, Koen Kooi wrote:
>> Then I noticed that the 'genericarmv7a' machine in meta-linaro set
>> the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set
>>
On 10/20/2013 09:04 PM, Koen Kooi wrote:
Then I noticed that the 'genericarmv7a' machine in meta-linaro set
the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set
that variable, but that's a different bug. It turns out that using
that tune we can have a single feed again for all armv7a
You are looking in the wrong file.
In Angstrom, you need to change BBPATH in setup-scripts/conf/bblayers.conf
Not in the layer.conf in your own layer.
Best Regards
Ulf Samuelsson
u...@emagii.com
23 okt 2013 kl. 14:24 skrev matti kaasinen :
> 2013/10/23 matti kaasinen
>
>> for conf and include
2013/10/23 matti kaasinen
> for conf and include files it will use the BBPATH and not priority
>>> which means your layer should appear before meta-beagleboard in BBPATH
>>> order.
>>
>>
> It did not help chnging BBPATH in layer.conf
> It used to be
> BBPATH .= ":${LAYERDIR}"
> and I changed it t
2013/10/23 matti kaasinen
> for conf and include files it will use the BBPATH and not priority
>> which means your layer should appear before meta-beagleboard in BBPATH
>> order.
>
>
It did not help chnging BBPATH in layer.conf
It used to be
BBPATH .= ":${LAYERDIR}"
and I changed it to:
BBPATH =.
2013/10/23 Khem Raj
> > Hi Ulf,
> > Yes, linux.inc seems doing the job as you told - this clears a lot. I had
> > been patching wrong file:${S}/defconfig instead of ${WORKDIR}/defconfig.
> > It seems that I'm not alone with this mistake. ${S}/defconfig seems to be
> > created by two patches:
> >
On Wed, Oct 23, 2013 at 3:07 AM, matti kaasinen
wrote:
> Hi Ulf,
> Yes, linux.inc seems doing the job as you told - this clears a lot. I had
> been patching wrong file:${S}/defconfig instead of ${WORKDIR}/defconfig.
> It seems that I'm not alone with this mistake. ${S}/defconfig seems to be
> crea
Hi Ulf,
Yes, linux.inc seems doing the job as you told - this clears a lot. I had
been patching wrong file:${S}/defconfig instead of ${WORKDIR}/defconfig.
It seems that I'm not alone with this mistake. ${S}/defconfig seems to be
created by two patches:
0002-add-defconfig-file-to-use-as-.config.patc
10 matches
Mail list logo
