meta-sugarbay: Change README build instructions to prefer tarballs
cover meta-sugarbay: Change README build instructions to prefer tarballs
From: Tom Zanussi <[email protected]>
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(-)
PATCH 1/1 meta-sugarbay: Change build instructions in README to use BSP tarball
From: Tom Zanussi <[email protected]>
Change the build instructions to use BSP tarballs instead of git clones. The git clone info remains as a mentioned alternative.
Fixes [YOCTO #1103].
--- meta-sugarbay/README | 21 ++++++++++++--------- 1 files changed, 12 insertions(+), 9 deletions(-)
meta-sugarbay/README +12 -9
@@ -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 =================================
Signature · 1 line
1.7.0.4
Re: [PATCH 1/1] meta-sugarbay: Change build instructions in README to use BSP tarball
Thanks, Tom. :-)
Quoted 60 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Thursday, May 26, 2011 10:43 AM
To: Rifenbark, Scott M; Stewart, David C; [email protected]
Cc: Zanussi, Tom
Subject: [PATCH 1/1] meta-sugarbay: Change build instructions in README to use BSP tarballFrom: Tom Zanussi <[email protected]>
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 <[email protected]>--- meta-sugarbay/README | 21 ++++++++++++--------- 1 files changed, 12 insertions(+), 9 deletions(-)meta-sugarbay/README index renamed from meta-sugarbay/README +0
-0bcc46c2..7899205 100644
meta-sugarbay/README +0
-0@@ -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'.meta-sugarbay/README +3
-1+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 byadding the location of the meta-sugarbay layer to bblayers.conf e.g.:
meta-sugarbay/README +0
-0@@ -47,6 +41,15 @@ At the end of a successful build, you should have a liveimage 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').
meta-sugarbay/README +9
-1+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