diff options
author | Tom Zanussi <tom.zanussi@intel.com> | 2011-05-26 15:22:29 -0500 |
---|---|---|
committer | Tom Zanussi <tom.zanussi@intel.com> | 2011-05-26 15:22:29 -0500 |
commit | b0f4192e67e3140e41870b967977a2440a415c93 (patch) | |
tree | fd235b68fe5222177d42f3d8ebea760ea416dd79 /meta-crownbay/README | |
parent | fc719f0cd6530ce15148b4aa274f1644b461b298 (diff) | |
download | meta-intel-b0f4192e67e3140e41870b967977a2440a415c93.tar.gz |
meta-intel: Change build instructions in README to use BSP tarball
Change the build instructions to use BSP tarballs instead of git
clones. The git clone info remains as a mentioned alternative.
The original bug report was for Sugar Bay, but the others had the same
problem - this fixes those up.
Fixes [YOCTO #1103].
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-crownbay/README')
-rw-r--r-- | meta-crownbay/README | 21 |
1 files changed, 12 insertions, 9 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README index 11770246..bb1e0c3f 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README | |||
@@ -19,17 +19,11 @@ III. Booting the images in /binary | |||
19 | I. Building the meta-crownbay BSP layer | 19 | I. Building the meta-crownbay BSP layer |
20 | ======================================= | 20 | ======================================= |
21 | 21 | ||
22 | For each BSP in the 'meta-intel' repository, there are multiple | ||
23 | branches, one corresponding to each major release starting with | ||
24 | 'laverne' (0.90), in addition to the latest code which tracks the | ||
25 | current master. | ||
26 | |||
27 | In order to build an image with BSP support for a given release, you | 22 | In order to build an image with BSP support for a given release, you |
28 | need to check out the 'meta-intel' branch corresponding to the release | 23 | need to download the corresponding BSP tarball from the 'Board Support |
29 | you're building against e.g. to build for bernard (1.0), check out | 24 | Package (BSP) Downloads' page of the Yocto Project website. |
30 | the 'bernard' branch of both poky and 'meta-intel'. | ||
31 | 25 | ||
32 | Having done that, and assuming you cloned the 'meta-intel' repository | 26 | Having done that, and assuming you extracted the BSP tarball contents |
33 | at the top-level of your yocto build tree, you can build a crownbay | 27 | at the top-level of your yocto build tree, you can build a crownbay |
34 | image by adding the location of the meta-crownbay layer to | 28 | image by adding the location of the meta-crownbay layer to |
35 | bblayers.conf e.g.: | 29 | bblayers.conf e.g.: |
@@ -61,6 +55,15 @@ At the end of a successful build, you should have a live image that | |||
61 | you can boot from a USB flash drive (see instructions on how to do | 55 | you can boot from a USB flash drive (see instructions on how to do |
62 | that below, in the section 'Booting the images from /binary'). | 56 | that below, in the section 'Booting the images from /binary'). |
63 | 57 | ||
58 | As an alternative to downloading the BSP tarball, you can also work | ||
59 | directly from the meta-intel git repository. For each BSP in the | ||
60 | 'meta-intel' repository, there are multiple branches, one | ||
61 | corresponding to each major release starting with 'laverne' (0.90), in | ||
62 | addition to the latest code which tracks the current master. Instead | ||
63 | of extracting a BSP tarball at the top level of your yocto build tree, | ||
64 | you can equivalently check out the appropriate branch from the | ||
65 | meta-intel repository at the same location. | ||
66 | |||
64 | 67 | ||
65 | II. Special notes for building the meta-crownbay BSP layer | 68 | II. Special notes for building the meta-crownbay BSP layer |
66 | ========================================================== | 69 | ========================================================== |