* [PATCH 0/1] meta-sugarbay: Change README build instructions to prefer tarballs
@ 2011-05-26 17:42 tom.zanussi
2011-05-26 17:42 ` [PATCH 1/1] meta-sugarbay: Change build instructions in README to use BSP tarball tom.zanussi
0 siblings, 1 reply; 3+ messages in thread
From: tom.zanussi @ 2011-05-26 17:42 UTC (permalink / raw)
To: scott.m.rifenbark, david.c.stewart, yocto
From: Tom Zanussi <tom.zanussi@intel.com>
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(-)
^ permalink raw reply [flat|nested] 3+ messages in thread* [PATCH 1/1] meta-sugarbay: Change build instructions in README to use BSP tarball 2011-05-26 17:42 [PATCH 0/1] meta-sugarbay: Change README build instructions to prefer tarballs tom.zanussi @ 2011-05-26 17:42 ` tom.zanussi 2011-05-26 18:24 ` Stewart, David C 0 siblings, 1 reply; 3+ messages in thread From: tom.zanussi @ 2011-05-26 17:42 UTC (permalink / raw) To: scott.m.rifenbark, david.c.stewart, yocto From: Tom Zanussi <tom.zanussi@intel.com> 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 <tom.zanussi@intel.com> --- 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 ^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 1/1] meta-sugarbay: Change build instructions in README to use BSP tarball 2011-05-26 17:42 ` [PATCH 1/1] meta-sugarbay: Change build instructions in README to use BSP tarball tom.zanussi @ 2011-05-26 18:24 ` Stewart, David C 0 siblings, 0 replies; 3+ messages in thread From: Stewart, David C @ 2011-05-26 18:24 UTC (permalink / raw) To: Zanussi, Tom, Rifenbark, Scott M, yocto@yoctoproject.org 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 <tom.zanussi@intel.com> > > 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 <tom.zanussi@intel.com> > --- > 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-05-26 18:24 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-05-26 17:42 [PATCH 0/1] meta-sugarbay: Change README build instructions to prefer tarballs tom.zanussi 2011-05-26 17:42 ` [PATCH 1/1] meta-sugarbay: Change build instructions in README to use BSP tarball tom.zanussi 2011-05-26 18:24 ` Stewart, David C
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.