MIRRORS/meta-intel
1
0
Fork 0
mirror of git://git.yoctoproject.org/meta-intel.git synced 2025-07-19 12:59:03 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

meta-intel: Change build instructions in README to use BSP tarball

Browse Source 
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>
This commit is contained in:
Tom Zanussi 2011-05-26 15:22:29 -05:00
parent fc719f0cd6
commit b0f4192e67
4 changed files with 48 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
meta-crownbay/README
View File

@ -19,17 +19,11 @@ III. Booting the images in /binary
I. Building the meta-crownbay 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 bernard (1.0), check out
the 'bernard' 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 crownbay
image by adding the location of the meta-crownbay layer to
bblayers.conf e.g.:
@ -61,6 +55,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. Special notes for building the meta-crownbay BSP layer
==========================================================

20
meta-emenlow/README
View File

@ -23,16 +23,11 @@ II. Booting the images in /binary
I. Building the meta-emenlow BSP layer
=======================================
The 'meta-intel' repository contains 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 an emenlow
image by adding the location of the meta-emenlow layer to
bblayers.conf e.g.:
@ -52,6 +47,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
=================================

21
meta-fishriver/README
View File

@ -27,17 +27,11 @@ config changes for:
II. Building the meta-fishriver 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 fishriver
image by adding the location of the meta-fishriver layer to
bblayers.conf e.g.:
@ -57,6 +51,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.
III. Booting the images in /binary
==================================

21
meta-jasperforest/README
View File

@ -18,17 +18,11 @@ Table of Contents
I. Building the meta-jasperforest 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 jasperforest
image by adding the location of the meta-jasperforest layer to
bblayers.conf e.g.:
@ -48,6 +42,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
=================================