Re: [yocto] In consistancy in the defition of BBFILE_COLLECTIONS in layer.conf
On Wed, May 25, 2011 at 10:37:45PM -0500, Tom Zanussi wrote: > On Wed, 2011-05-25 at 18:17 -0700, Jeremy Puhlman wrote: > > Opps sent from wrong account. > > > > I was working with some layerinfo code, and I noticed that the values of > > BBFILE_COLLECTIONS in layer.conf in the meta-intel repo are kind of all > > over the map: > > > > for each in */conf/layer.conf; do cat $each; done | grep BBFILE_COLLECTIONS > > BBFILE_COLLECTIONS_crownbay += "crownbay" > > BBFILE_COLLECTIONS_crownbay-noemgd += "crownbay-noemgd" > > BBFILE_COLLECTIONS_fishriver += "fishriver" > > BBFILE_COLLECTIONS_jasperforest += "jasperforest" > > BBFILE_COLLECTIONS_sugarbay += "sugarbay" > > > > For the above layers when I just list out oe-core and one of the above, > > the results from BBFILE_COLLECTIONS ends up > > just being what ever was set above. > > > > BBFILE_COLLECTIONS += "n450" > > BBFILE_COLLECTIONS += "emenlow" > > > > When using these layers, the final BBFILE_COLLECTIONS is the list of all > > the layers as expected. > > > > Was just curious if there was a intentional reason why the > > difference(i.e. is there some code that I am missing that fixes this up)? > > No, not intentional - looks like a case of an overzealous overriding > typo that propagated. I'll cook up a patch to make them all just > 'BBFILE_COLLECTIONS += ' Using machine override has one small benefit when I have meta-nokia layer which has only recipes with COMPATIBLE_MACHINE = "nokia900" and I'm building different machine (like om-gta02) I get this warning: WARNING: No bb files matched BBFILE_PATTERN_nokia-layer '^/OE/shr-core/meta-smartphone/meta-nokia/' because all bb files from this layer are ignored because of COMPATIBLE_MACHINE if I change it like this -BBFILE_COLLECTIONS += "nokia-layer" +BBFILE_COLLECTIONS_nokia900 += "nokia-layer" maybe with more overrides per layer.conf if it supports multiple machines, the warning is gone, but seems like sstate checksums are different again, because during test I changed only this and another gcc rebuild is in runqueue now :/. -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com pgpMAFVBxnBAY.pgp Description: PGP signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] In consistancy in the defition of BBFILE_COLLECTIONS in layer.conf
On Thu, 2011-05-26 at 09:39 +0200, Martin Jansa wrote: > Using machine override has one small benefit > > when I have meta-nokia layer which has only recipes with > COMPATIBLE_MACHINE = "nokia900" and I'm building different machine (like > om-gta02) I get this warning: > WARNING: No bb files matched BBFILE_PATTERN_nokia-layer > '^/OE/shr-core/meta-smartphone/meta-nokia/' > because all bb files from this layer are ignored because of > COMPATIBLE_MACHINE I think there is a change on bitbake master which should fix some of the cases where this warning was appearing (where a layer only contained .bbappend files). > if I change it like this > -BBFILE_COLLECTIONS += "nokia-layer" > +BBFILE_COLLECTIONS_nokia900 += "nokia-layer" > maybe with more overrides per layer.conf if it supports multiple > machines, the warning is gone, but seems like sstate checksums are > different again, because during test I changed only this and another gcc > rebuild is in runqueue now :/. Ouch. If you can figure out what changed we can try and fix that. FWIW, I also merged the signature generation data writing at stamp creation time (with fixes). Cheers, Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] meta-intel BBFILE_COLLECTIONS fixups
From: Tom Zanussi This fixes a problem with BBFILE_COLLECTIONS reported by Jeremy Puhlman. The following changes since commit 1b227f8ed2df529cc13f7169b0c08ff3d0f8c812: Tom Zanussi (1): meta-sugarbay: remove xserver-xf86-dri-lite bbappend are available in the git repository at: git://git.pokylinux.org/meta-intel.git tzanussi/bbfile-collections-fix http://git.pokylinux.org/cgit.cgi//log/?h=tzanussi/bbfile-collections-fix Tom Zanussi (1): meta-intel: fix BBFILE_COLLECTIONS overrides meta-crownbay/conf/layer.conf |4 ++-- meta-fishriver/conf/layer.conf|2 +- meta-jasperforest/conf/layer.conf |2 +- meta-sugarbay/conf/layer.conf |2 +- 4 files changed, 5 insertions(+), 5 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] meta-intel: fix BBFILE_COLLECTIONS overrides
From: Tom Zanussi
Several BBFILE_COLLECTIONS assignments in the layer.confs for these
meta-intel layers added unwanted machine overrides, resulting in
truncated values for this variable - remove them.
Signed-off-by: Tom Zanussi
---
meta-crownbay/conf/layer.conf |4 ++--
meta-fishriver/conf/layer.conf|2 +-
meta-jasperforest/conf/layer.conf |2 +-
meta-sugarbay/conf/layer.conf |2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta-crownbay/conf/layer.conf b/meta-crownbay/conf/layer.conf
index cee4ba2..d15579d 100644
--- a/meta-crownbay/conf/layer.conf
+++ b/meta-crownbay/conf/layer.conf
@@ -5,10 +5,10 @@ BBPATH := "${BBPATH}:${LAYERDIR}"
BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
-BBFILE_COLLECTIONS_crownbay += "crownbay"
+BBFILE_COLLECTIONS_append_crownbay += "crownbay"
BBFILE_PATTERN_crownbay := "^${LAYERDIR}/"
BBFILE_PRIORITY_crownbay = "6"
-BBFILE_COLLECTIONS_crownbay-noemgd += "crownbay-noemgd"
+BBFILE_COLLECTIONS_append_crownbay-noemgd += "crownbay-noemgd"
BBFILE_PATTERN_crownbay-noemgd := "^${LAYERDIR}/"
BBFILE_PRIORITY_crownbay-noemgd = "6"
diff --git a/meta-fishriver/conf/layer.conf b/meta-fishriver/conf/layer.conf
index 595bbe3..9162b5e 100644
--- a/meta-fishriver/conf/layer.conf
+++ b/meta-fishriver/conf/layer.conf
@@ -5,6 +5,6 @@ BBPATH := "${BBPATH}:${LAYERDIR}"
BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
-BBFILE_COLLECTIONS_fishriver += "fishriver"
+BBFILE_COLLECTIONS += "fishriver"
BBFILE_PATTERN_fishriver := "^${LAYERDIR}/"
BBFILE_PRIORITY_fishriver = "6"
diff --git a/meta-jasperforest/conf/layer.conf
b/meta-jasperforest/conf/layer.conf
index 564bb1d..8125659 100644
--- a/meta-jasperforest/conf/layer.conf
+++ b/meta-jasperforest/conf/layer.conf
@@ -7,6 +7,6 @@ BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/../common/recipes-*/*/*.bb \
${LAYERDIR}/../common/recipes-*/*/*.bbappend"
-BBFILE_COLLECTIONS_jasperforest += "jasperforest"
+BBFILE_COLLECTIONS += "jasperforest"
BBFILE_PATTERN_jasperforest := "^${LAYERDIR}/"
BBFILE_PRIORITY_jasperforest = "6"
diff --git a/meta-sugarbay/conf/layer.conf b/meta-sugarbay/conf/layer.conf
index e23d123..d5f78e1 100644
--- a/meta-sugarbay/conf/layer.conf
+++ b/meta-sugarbay/conf/layer.conf
@@ -7,6 +7,6 @@ BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/../common/recipes-*/*/*.bb \
${LAYERDIR}/../common/recipes-*/*/*.bbappend"
-BBFILE_COLLECTIONS_sugarbay += "sugarbay"
+BBFILE_COLLECTIONS += "sugarbay"
BBFILE_PATTERN_sugarbay := "^${LAYERDIR}/"
BBFILE_PRIORITY_sugarbay = "6"
--
1.7.0.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] meta-sugarbay: Change README build instructions to prefer tarballs
From: Tom Zanussi This changes the build instructions in the README for the Sugar Bay BSP to use tarballs instead of git clones. This fixes the issue reported for YOCTO 1103 at least as far as the README in the BSP for the Sugar Bay goes. The release notes on the Yocto website would still need to be updated to reflect this as well. The other meta-intel BSPs have the same README text - they'll be updated as well with the same text, once it's clear no further changes are needed. The following changes since commit f113449eb132df7c8a4c45ad8719ecc3ec84a6b5: Tom Zanussi (1): meta-intel: fix BBFILE_COLLECTIONS overrides are available in the git repository at: git://git.pokylinux.org/meta-intel.git tzanussi/yocto-1103 http://git.pokylinux.org/cgit.cgi//log/?h=tzanussi/yocto-1103 Tom Zanussi (1): meta-sugarbay: Change build instructions in README to use BSP tarball meta-sugarbay/README | 21 - 1 files changed, 12 insertions(+), 9 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] meta-sugarbay: Change build instructions in README to use BSP tarball
From: Tom Zanussi Change the build instructions to use BSP tarballs instead of git clones. The git clone info remains as a mentioned alternative. Fixes [YOCTO #1103]. Signed-off-by: Tom Zanussi --- meta-sugarbay/README | 21 - 1 files changed, 12 insertions(+), 9 deletions(-) diff --git a/meta-sugarbay/README b/meta-sugarbay/README index bcc46c2..7899205 100644 --- a/meta-sugarbay/README +++ b/meta-sugarbay/README @@ -17,17 +17,11 @@ III. Booting the images in /binary I. Building the meta-sugarbay BSP layer === -For each BSP in the 'meta-intel' repository, there are multiple -branches, one corresponding to each major release starting with -'laverne' (0.90), in addition to the latest code which tracks the -current master. - In order to build an image with BSP support for a given release, you -need to check out the 'meta-intel' branch corresponding to the release -you're building against e.g. to build for laverne (0.90), check out -the 'laverne' branch of both poky and 'meta-intel'. +need to download the corresponding BSP tarball from the 'Board Support +Package (BSP) Downloads' page of the Yocto Project website. -Having done that, and assuming you cloned the 'meta-intel' repository +Having done that, and assuming you extracted the BSP tarball contents at the top-level of your yocto build tree, you can build a sugarbay image by adding the location of the meta-sugarbay layer to bblayers.conf e.g.: @@ -47,6 +41,15 @@ At the end of a successful build, you should have a live image that you can boot from a USB flash drive (see instructions on how to do that below, in the section 'Booting the images from /binary'). +As an alternative to downloading the BSP tarball, you can also work +directly from the meta-intel git repository. For each BSP in the +'meta-intel' repository, there are multiple branches, one +corresponding to each major release starting with 'laverne' (0.90), in +addition to the latest code which tracks the current master. Instead +of extracting a BSP tarball at the top level of your yocto build tree, +you can equivalently check out the appropriate branch from the +meta-intel repository at the same location. + II. Booting the images in /binary = -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] meta-sugarbay: Change build instructions in README to use BSP tarball
Thanks, Tom. :-) > -Original Message- > From: Zanussi, Tom > Sent: Thursday, May 26, 2011 10:43 AM > To: Rifenbark, Scott M; Stewart, David C; yocto@yoctoproject.org > Cc: Zanussi, Tom > Subject: [PATCH 1/1] meta-sugarbay: Change build instructions in README to > use BSP tarball > > From: Tom Zanussi > > Change the build instructions to use BSP tarballs instead of git clones. The > git > clone info remains as a mentioned alternative. > > Fixes [YOCTO #1103]. > > Signed-off-by: Tom Zanussi > --- > meta-sugarbay/README | 21 - > 1 files changed, 12 insertions(+), 9 deletions(-) > > diff --git a/meta-sugarbay/README b/meta-sugarbay/README index > bcc46c2..7899205 100644 > --- a/meta-sugarbay/README > +++ b/meta-sugarbay/README > @@ -17,17 +17,11 @@ III. Booting the images in /binary I. Building the meta- > sugarbay BSP layer === > > -For each BSP in the 'meta-intel' repository, there are multiple -branches, > one corresponding to each major release starting with -'laverne' (0.90), in > addition to the latest code which tracks the -current master. > - > In order to build an image with BSP support for a given release, you -need to > check out the 'meta-intel' branch corresponding to the release -you're > building against e.g. to build for laverne (0.90), check out -the 'laverne' > branch of both poky and 'meta-intel'. > +need to download the corresponding BSP tarball from the 'Board Support > +Package (BSP) Downloads' page of the Yocto Project website. > > -Having done that, and assuming you cloned the 'meta-intel' repository > +Having done that, and assuming you extracted the BSP tarball contents > at the top-level of your yocto build tree, you can build a sugarbay image by > adding the location of the meta-sugarbay layer to bblayers.conf e.g.: > @@ -47,6 +41,15 @@ At the end of a successful build, you should have a live > image that you can boot from a USB flash drive (see instructions on how to > do that below, in the section 'Booting the images from /binary'). > > +As an alternative to downloading the BSP tarball, you can also work > +directly from the meta-intel git repository. For each BSP in the > +'meta-intel' repository, there are multiple branches, one corresponding > +to each major release starting with 'laverne' (0.90), in addition to > +the latest code which tracks the current master. Instead of extracting > +a BSP tarball at the top level of your yocto build tree, you can > +equivalently check out the appropriate branch from the meta-intel > +repository at the same location. > + > > II. Booting the images in /binary > = > -- > 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] 1.1_M1.rc2 Reminder.
I will be ready to roll a second release candidate for M1 on Friday, May 27th at 7pm Pacific. If you have fixes for the 1.1_M1 branch for rc2, please be sure to call them out in your pull requests. Thanks. --- Elizabeth Flanagan Yocto Project Release Engineer ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Bug Triage call for action
Hi All, The Yocto bug triage team did bug scrub and the following 2 bugs are identified as critical major which means they need to be fixed ASAP for the upcoming 1.1 M1 release. 1100 - [emenlow/crownbay-noemgd] X window could not start up with sato-sdk image (Tom, Dexuan, Darren) 1108 - keyboard could not work in qemux86/x86-64 (Saul, Ke) So people that are working on these bugs , please make sure leave enough information for your current investigation/debugging by EOD your time so the next person in a different time zone can easily pickup the context and continue working on the fix. Thanks, Jessica ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
