<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Yocto Project Mega-Manual</title>
<link rel="stylesheet" type="text/css" href="mega-style.css" />
<link rel="stylesheet" href="style.css">
<script src="script.js"></script>
</head>
<body>
<div class="fixtop">
Please go <a href="http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html">to the latest version.</a>
</div>
<div xml:lang="en" class="book" title="Yocto Project Mega-Manual" id="mega-manual" lang="en"><div class="titlepage"><div><div><h1 class="title">
Yocto Project Mega-Manual
</h1></div><div><div class="authorgroup">
<div class="author"><h3 class="author"><span class="firstname">Scott</span> <span class="surname">Rifenbark</span></h3><div class="affiliation">
<span class="orgname">Intel Corporation<br /></span>
</div><code class="email"><<a class="email" href="mailto:srifenbark@gmail.com">srifenbark@gmail.com</a>></code></div>
</div></div><div><p class="copyright">Copyright © 2010-2017 Linux Foundation</p></div><div><div class="legalnotice" title="Legal Notice"><a id="idm45368204301728"></a>
<p>
Permission is granted to copy, distribute and/or modify this document under
the terms of the <a class="ulink" href="http://creativecommons.org/licenses/by-sa/2.0/uk/" target="_top">Creative Commons Attribution-Share Alike 2.0 UK: England & Wales</a> as published by Creative Commons.
</p>
<div class="note" title="Manual Notes" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Manual Notes</h3>
<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
For the latest version of the Yocto Project
Mega-Manual associated with this Yocto Project release
(version 2.3),
see the Yocto Project Mega-Manual from the
<a class="ulink" href="http://www.yoctoproject.org/documentation" target="_top">Yocto Project documentation page</a>.
</p></li><li class="listitem"><p>
This version of the manual is version
2.3.
For later releases of the Yocto Project (if they exist),
go to the
<a class="ulink" href="http://www.yoctoproject.org/documentation" target="_top">Yocto Project documentation page</a>
and use the drop-down "Active Releases" button
and choose the Yocto Project version for which you want
the manual.
</p></li><li class="listitem"><p>
For an in-development version of the Yocto Project
Mega-Manual, see
<a class="ulink" href="http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html" target="_top">http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html</a>.
</p></li></ul></div>
</div>
</div></div><div><div class="revhistory"><table border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="2"><strong>Revision History</strong></th></tr>
<tr><td align="left">Revision 1.8</td><td align="left">April 2015</td></tr><tr><td align="left" colspan="2">Released with the Yocto Project 1.8 Release.</td></tr>
<tr><td align="left">Revision 2.0</td><td align="left">October 2015</td></tr><tr><td align="left" colspan="2">Released with the Yocto Project 2.0 Release.</td></tr>
<tr><td align="left">Revision 2.1</td><td align="left">April 2016</td></tr><tr><td align="left" colspan="2">Released with the Yocto Project 2.1 Release.</td></tr>
<tr><td align="left">Revision 2.2</td><td align="left">October 2016</td></tr><tr><td align="left" colspan="2">Released with the Yocto Project 2.2 Release.</td></tr>
<tr><td align="left">Revision 2.3</td><td align="left">May 2017</td></tr><tr><td align="left" colspan="2">Released with the Yocto Project 2.3 Release.</td></tr>
</table></div></div><div><div class="abstract" title="Abstract"><p class="title"><b>Abstract</b><span class="permalink"><a alt="Permalink" title="Permalink" href="#idm45368186427344">¶</a></span></p>
The Yocto Project Mega-Manual is a concatenation of the published
Yocto Project HTML manuals for the given release.
The manual exists to help users efficiently search for strings
across the entire Yocto Project documentation set.
</div></div></div><hr /></div>
<div class="article" title="Yocto Project Quick Start" id="yocto-project-qs-intro"><div class="titlepage"><div><div><h2 class="title">Yocto Project Quick Start<span class="permalink"><a alt="Permalink" title="Permalink" href="#yocto-project-qs-intro">¶</a></span></h2></div><div><p class="copyright">Copyright © 2010-2017 Linux Foundation</p></div><div><div class="legalnotice" title="Legal Notice"><a id="idm45368202166736"></a><p>
Permission is granted to copy, distribute and/or modify this document under
the terms of the <a class="ulink" href="http://creativecommons.org/licenses/by-sa/2.0/uk/" target="_top">Creative Commons Attribution-Share Alike 2.0 UK: England & Wales</a> as published by Creative Commons.
</p><div class="note" title="Manual Notes" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Manual Notes</h3><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
For the latest version of the Yocto Project Quick
Start associated with this Yocto Project release
(version 2.3),
see the Yocto Project Quick Start from the
<a class="ulink" href="http://www.yoctoproject.org/documentation" target="_top">Yocto Project documentation page</a>.
</p></li><li class="listitem"><p>
This version of the manual is version
2.3.
For later releases of the Yocto Project (if they exist),
go to the
<a class="ulink" href="http://www.yoctoproject.org/documentation" target="_top">Yocto Project documentation page</a>
and use the drop-down "Active Releases" button
and choose the Yocto Project version for which you want
the manual.
</p></li><li class="listitem"><p>
For an in-development version of the Yocto Project
Quick Start, see
<a class="ulink" href="http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html" target="_top">http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html</a>.
</p></li></ul></div></div></div></div><div><div class="abstract" title="Abstract"><p class="title"><b>Abstract</b><span class="permalink"><a alt="Permalink" title="Permalink" href="#idm45368186219536">¶</a></span></p><table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="540"><tr style="height: 90px"><td align="right"><img src="figures/yocto-project-transp.png" align="right" width="135" /></td></tr></table></div></div></div><hr /></div><div class="section" title="1. Welcome!"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="welcome">1. Welcome!<span class="permalink"><a alt="Permalink" title="Permalink" href="#welcome">¶</a></span></h2></div></div></div><p>
Welcome to the Yocto Project!
The Yocto Project is an open-source collaboration project whose
focus is developers of embedded Linux systems.
Among other things, the Yocto Project uses a build host based
on the OpenEmbedded (OE) project, which uses the
<a class="link" href="#bitbake-term" target="_top">BitBake</a>
tool, to construct complete Linux images.
The BitBake and OE components are combined together to form
a reference build host, historically known as
<a class="link" href="#poky" target="_top">Poky</a>.
</p><p>
If you do not have a system that runs Linux and you want to give
the Yocto Project a test run, you might consider using the Yocto
Project Build Appliance.
The Build Appliance allows you to build and boot a custom embedded
Linux image with the Yocto Project using a non-Linux development
system.
See the
<a class="ulink" href="https://www.yoctoproject.org/tools-resources/projects/build-appliance" target="_top">Yocto Project Build Appliance</a>
for more information.
</p><p>
This quick start is written so that you can quickly get a
build host set up to use the Yocto Project and then build some
Linux images.
Rather than go into great detail about the Yocto Project and its
many capabilities, this quick start provides the minimal
information you need to try out the Yocto Project using a
supported Linux build host.
Reading and using the quick start should result in you having a
basic understanding of what the Yocto Project is and how to use
some of its core components.
You will also have worked through steps to produce two images:
one that is suitable for emulation and one that boots on actual
hardware.
The examples highlight the ease with which you can use the
Yocto Project to create images for multiple types of hardware.
</p><p>
For more detailed information on the Yocto Project, you can
reference these resources:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>Website:</em></span>
The
<a class="ulink" href="http://www.yoctoproject.org" target="_top">Yocto Project Website</a>
provides the latest builds, breaking news, full development
documentation, and access to a rich Yocto Project
Development Community into which you can tap.
</p></li><li class="listitem"><p><span class="emphasis"><em>FAQs:</em></span>
Lists commonly asked Yocto Project questions and answers.
You can find two FAQs:
<a class="ulink" href="https://wiki.yoctoproject.org/wiki/FAQ" target="_top">Yocto Project FAQ</a>
on a wiki, and the
"<a class="link" href="#faq" target="_top">FAQ</a>"
chapter in the Yocto Project Reference Manual.
</p></li><li class="listitem"><p><span class="emphasis"><em>Developer Screencast:</em></span>
The
<a class="ulink" href="http://vimeo.com/36450321" target="_top">Getting Started with the Yocto Project - New Developer Screencast Tutorial</a>
provides a 30-minute video created for users unfamiliar
with the Yocto Project but familiar with Linux build
hosts.
While this screencast is somewhat dated, the introductory
and fundamental concepts are useful for the beginner.
</p></li></ul></div><p>
</p></div><div class="section" title="2. Introducing the Yocto Project Development Environment"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="yp-intro">2. Introducing the Yocto Project Development Environment<span class="permalink"><a alt="Permalink" title="Permalink" href="#yp-intro">¶</a></span></h2></div></div></div><p>
The Yocto Project through the OpenEmbedded build system provides an
open source development environment targeting the ARM, MIPS,
PowerPC, and x86 architectures for a variety of platforms
including x86-64 and emulated ones.
You can use components from the Yocto Project to design, develop,
build, debug, simulate, and test the complete software stack using
Linux, the X Window System, GTK+ frameworks, and Qt frameworks.
</p><div class="mediaobject" align="center"><table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="100%"><tr><td align="center"><img src="figures/yocto-environment.png" align="middle" width="100%" /></td></tr></table><div class="caption"><p>The Yocto Project Development Environment</p></div></div><p>
Here are some highlights for the Yocto Project:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
Provides a recent Linux kernel along with a set of system
commands and libraries suitable for the embedded
environment.
</p></li><li class="listitem"><p>
Makes available system components such as X11, GTK+, Qt,
Clutter, and SDL (among others) so you can create a rich user
experience on devices that have display hardware.
For devices that do not have a display or where you wish to
use alternative UI frameworks, these components need not be
installed.
</p></li><li class="listitem"><p>
Creates a focused and stable core compatible with the
OpenEmbedded project with which you can easily and reliably
build and develop.
</p></li><li class="listitem"><p>
Fully supports a wide range of hardware and device emulation
through the Quick EMUlator (QEMU).
</p></li><li class="listitem"><p>
Provides a layer mechanism that allows you to easily extend
the system, make customizations, and keep them organized.
</p></li></ul></div><p>
You can use the Yocto Project to generate images for many kinds
of devices.
As mentioned earlier, the Yocto Project supports creation of
reference images that you can boot within and emulate using QEMU.
The standard example machines target QEMU full-system
emulation for 32-bit and 64-bit variants of x86, ARM, MIPS, and
PowerPC architectures.
Beyond emulation, you can use the layer mechanism to extend
support to just about any platform that Linux can run on and that
a toolchain can target.
</p><p>
Another Yocto Project feature is the Sato reference User
Interface.
This optional UI that is based on GTK+ is intended for devices with
restricted screen sizes and is included as part of the
OpenEmbedded Core layer so that developers can test parts of the
software stack.
</p></div><div class="section" title="3. Setting Up to Use the Yocto Project"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="yp-resources">3. Setting Up to Use the Yocto Project<span class="permalink"><a alt="Permalink" title="Permalink" href="#yp-resources">¶</a></span></h2></div></div></div><p>
The following list shows what you need in order to use a
Linux-based build host to use the Yocto Project to build images:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>Build Host</em></span>
A build host with a minimum of 50 Gbytes of free disk
space that is running a supported Linux distribution (i.e.
recent releases of Fedora, openSUSE, CentOS, Debian, or
Ubuntu).
</p></li><li class="listitem"><p><span class="emphasis"><em>Build Host Packages</em></span>
Appropriate packages installed on the build host.
</p></li><li class="listitem"><p><span class="emphasis"><em>The Yocto Project</em></span>
A release of the Yocto Project.
</p></li></ul></div><div class="section" title="3.1. The Linux Distribution"><div class="titlepage"><div><div><h3 class="title" id="the-linux-distro">3.1. The Linux Distribution<span class="permalink"><a alt="Permalink" title="Permalink" href="#the-linux-distro">¶</a></span></h3></div></div></div><p>
The Yocto Project team verifies each release against recent
versions of the most popular Linux distributions that
provide stable releases.
In general, if you have the current release minus one of the
following distributions, you should have no problems.
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
Ubuntu
</p></li><li class="listitem"><p>
Fedora
</p></li><li class="listitem"><p>
openSUSE
</p></li><li class="listitem"><p>
CentOS
</p></li><li class="listitem"><p>
Debian
</p></li></ul></div><p>
For a more detailed list of distributions that support the
Yocto Project, see the
"<a class="link" href="#detailed-supported-distros" target="_top">Supported Linux Distributions</a>"
section in the Yocto Project Reference Manual.
</p><p>
The OpenEmbedded build system should be able to run on any
modern distribution that has the following versions for
Git, tar, and Python.
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
Git 1.8.3.1 or greater
</p></li><li class="listitem"><p>
tar 1.24 or greater
</p></li><li class="listitem"><p>
Python 3.4.0 or greater.
</p></li></ul></div><p>
If your build host does not meet any of these three listed
version requirements, you can take steps to prepare the
system so that you can still use the Yocto Project.
See the
"<a class="link" href="#required-git-tar-and-python-versions" target="_top">Required Git, tar, and Python Versions</a>"
section in the Yocto Project Reference Manual for information.
</p></div><div class="section" title="3.2. The Build Host Packages"><div class="titlepage"><div><div><h3 class="title" id="packages">3.2. The Build Host Packages<span class="permalink"><a alt="Permalink" title="Permalink" href="#packages">¶</a></span></h3></div></div></div><p>
Required build host packages vary depending on your
build machine and what you want to do with the Yocto Project.
For example, if you want to build an image that can run
on QEMU in graphical mode (a minimal, basic build
requirement), then the build host package requirements
are different than if you want to build an image on a headless
system or build out the Yocto Project documentation set.
</p><p>
Collectively, the number of required packages is large
if you want to be able to cover all cases.
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
In general, you need to have root access and then install
the required packages.
Thus, the commands in the following section may or may
not work depending on whether or not your Linux
distribution has <code class="filename">sudo</code> installed.
</div><p>
</p><p>
The following list shows the required packages needed to build
an image that runs on QEMU in graphical mode (e.g. essential
plus graphics support).
For lists of required packages for other scenarios, see the
"<a class="link" href="#required-packages-for-the-host-development-system" target="_top">Required Packages for the Host Development System</a>"
section in the Yocto Project Reference Manual.
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>Ubuntu and Debian</em></span>
</p><pre class="literallayout">
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python python3 python3-pip python3-expect \
xz which libsdl1.2-dev xterm
</pre><p>
</p></li><li class="listitem"><p><span class="emphasis"><em>Fedora</em></span>
</p><pre class="literallayout">
$ sudo dnf install gawk make wget tar bzip2 gzip python3 unzip perl patch \
diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath \
ccache perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue perl-bignum socat \
findutils which file cpio python python3-pip python3-expect xz which SDL-devel xterm
</pre><p>
</p></li><li class="listitem"><p><span class="emphasis"><em>OpenSUSE</em></span>
</p><pre class="literallayout">
$ sudo zypper install python gcc gcc-c++ git chrpath make wget python-xml \
diffstat makeinfo python-curses patch socat python3 python3-curses tar python3-pip \
python3-expect xz which libSDL-devel xterm
</pre><p>
</p></li><li class="listitem"><p><span class="emphasis"><em>CentOS</em></span>
</p><pre class="literallayout">
$ sudo yum install -y epel-release
$ sudo yum makecache
$ sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \
diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath socat \
perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue python34-pip xz \
which SDL-devel xterm
</pre><p>
</p><div class="note" title="Notes" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Notes</h3><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>
CentOS 6.x users need to ensure that the
required versions of Git, tar and Python
are available.
For details, See the
"<a class="link" href="#required-git-tar-and-python-versions" target="_top">Required Git, tar, and Python Versions</a>"
section in the Yocto Project Reference
Manual for information.
</p></li><li class="listitem"><p>
Extra Packages for Enterprise Linux
(i.e. <code class="filename">epel-release</code>)
is a collection of packages from Fedora
built on RHEL/CentOS for easy installation
of packages not included in enterprise
Linux by default.
You need to install these packages
separately.
</p></li><li class="listitem"><p>
The <code class="filename">makecache</code> command
consumes additional Metadata from
<code class="filename">epel-release</code>.
</p></li></ul></div></div><p>
</p></li></ul></div><p>
</p></div><div class="section" title="3.3. Yocto Project Release"><div class="titlepage"><div><div><h3 class="title" id="releases">3.3. Yocto Project Release<span class="permalink"><a alt="Permalink" title="Permalink" href="#releases">¶</a></span></h3></div></div></div><p>
The last requirement you need to meet before using the
Yocto Project is getting a Yocto Project release.
It is recommended that you get the latest Yocto Project release
by setting up (cloning in
<a class="link" href="#git" target="_top">Git</a> terms) a
local copy of the <code class="filename">poky</code> Git repository on
your build host and then checking out the latest release.
Doing so allows you to easily update to newer Yocto Project
releases as well as contribute back to the Yocto Project.
</p><p>
Here is an example from an Ubuntu build host that clones the
<code class="filename">poky</code> repository and then checks out the
latest Yocto Project Release (i.e. 2.3):
</p><pre class="literallayout">
$ git clone git://git.yoctoproject.org/poky
Cloning into 'poky'...
remote: Counting objects: 226790, done.
remote: Compressing objects: 100% (57465/57465), done.
remote: Total 226790 (delta 165212), reused 225887 (delta 164327)
Receiving objects: 100% (226790/226790), 100.98 MiB | 263 KiB/s, done.
Resolving deltas: 100% (165212/165212), done.
$ git checkout pyro
</pre><p>
You can also get the Yocto Project Files by downloading
Yocto Project releases from the
<a class="ulink" href="http://www.yoctoproject.org" target="_top">Yocto Project website</a>.
</p><p>
For more information on getting set up with the Yocto Project
release, see the
"<a class="link" href="#local-yp-release" target="_top">Yocto Project Release</a>"
item in the Yocto Project Development Manual.
</p></div></div><div class="section" title="4. Building Images"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="qs-building-images">4. Building Images<span class="permalink"><a alt="Permalink" title="Permalink" href="#qs-building-images">¶</a></span></h2></div></div></div><p>
Now that you have your system requirements in order, you can give
Yocto Project a try.
You can try out Yocto Project using either the command-line
interface or using Toaster, which uses a graphical user
interface.
If you want to try out the Yocto Project using a GUI, see the
Toaster User Manual
for information on how to install and set up Toaster.
</p><p>
To use the Yocto Project through the command-line interface,
finish this quick start, which presents steps that let you
do the following:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
Build a <code class="filename">qemux86</code> reference image
and run it in the QEMU emulator.
</p></li><li class="listitem"><p>
Easily change configurations so that you can quickly
create a second image that you can load onto bootable
media and actually boot target hardware.
This example uses the MinnowBoard
MAX-compatible boards.
</p></li></ul></div><p>
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
The steps in the following two sections do not provide detail,
but rather provide minimal, working commands and examples
designed to just get you started.
For more details, see the appropriate manuals in the
<a class="ulink" href="http://www.yoctoproject.org/documentation" target="_top">Yocto Project manual set</a>.
</div><p>
</p><div class="section" title="4.1. Building an Image for Emulation"><div class="titlepage"><div><div><h3 class="title" id="building-an-image-for-emulation">4.1. Building an Image for Emulation<span class="permalink"><a alt="Permalink" title="Permalink" href="#building-an-image-for-emulation">¶</a></span></h3></div></div></div><p>
Use the following commands to build your image.
The OpenEmbedded build system creates an entire Linux
distribution, including the toolchain, from source.
</p><div class="note" title="Note about Network Proxies" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note about Network Proxies</h3><p>
By default, the build process searches for source code
using a pre-determined order through a set of
locations.
If you are working behind a firewall and your build
host is not set up for proxies, you could encounter
problems with the build process when fetching source
code (e.g. fetcher failures or Git failures).
</p><p>
If you do not know your proxy settings, consult your
local network infrastructure resources and get that
information.
A good starting point could also be to check your web
browser settings.
Finally, you can find more information on using the
Yocto Project behind a firewall in the Yocto Project
Reference Manual
<a class="link" href="#how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server" target="_top">FAQ</a>
and on the
"<a class="ulink" href="https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy" target="_top">Working Behind a Network Proxy</a>"
wiki page.
</p></div><p>
</p><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><span class="emphasis"><em>Be Sure Your Build Host is Set Up:</em></span>
The steps to build an image in this section depend on
your build host being properly set up.
Be sure you have worked through the requirements
described in the
"<a class="link" href="#yp-resources" title="3. Setting Up to Use the Yocto Project">Setting Up to Use the Yocto Project</a>"
section.
</p></li><li class="listitem"><p><span class="emphasis"><em>Check Out Your Branch:</em></span>
Be sure you are in the
<a class="link" href="#source-directory" target="_top">Source Directory</a>
(e.g. <code class="filename">poky</code>) and then check out
the branch associated with the latest Yocto Project
Release:
</p><pre class="literallayout">
$ cd ~/poky
$ git checkout -b pyro origin/pyro
</pre><p>
Git's <code class="filename">checkout</code> command checks out
the current Yocto Project release into a local branch
whose name matches the release (i.e.
<code class="filename">pyro</code>).
The local branch tracks the upstream branch of the
same name.
Creating your own branch based on the released
branch ensures you are using the latest files for
that release.
</p></li><li class="listitem"><p><span class="emphasis"><em>Initialize the Build Environment:</em></span>
Run the
<a class="link" href="#structure-core-script" target="_top"><code class="filename">oe-init-build-env</code></a>
environment setup script to define the OpenEmbedded
build environment on your build host.
</p><pre class="literallayout">
$ source oe-init-build-env
</pre><p>
Among other things, the script creates the
<a class="link" href="#build-directory" target="_top">Build Directory</a>,
which is <code class="filename">build</code> in this case
and is located in the
<a class="link" href="#source-directory" target="_top">Source Directory</a>.
After the script runs, your current working directory
is set to the Build Directory.
Later, when the build completes, the Build Directory
contains all the files created during the build.
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
For information on running a memory-resident
<a class="link" href="#usingpoky-components-bitbake" target="_top">BitBake</a>,
see the
<a class="link" href="#structure-memres-core-script" target="_top"><code class="filename">oe-init-build-env-memres</code></a>
setup script.
</div><p>
</p></li><li class="listitem"><p><span class="emphasis"><em>Examine Your Local Configuration File:</em></span>
When you set up the build environment, a local
configuration file named
<code class="filename">local.conf</code> becomes available in
a <code class="filename">conf</code> subdirectory of the
Build Directory.
Before using BitBake to start the build, you can
look at this file and be sure your general
configurations are how you want them:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
To help conserve disk space during builds,
you can add the following statement to your
project's configuration file, which for this
example is
<code class="filename">poky/build/conf/local.conf</code>.
Adding this statement deletes the work
directory used for building a recipe once the
recipe is built.
</p><pre class="literallayout">
INHERIT += "rm_work"
</pre><p>
</p></li><li class="listitem"><p>
By default, the target machine for the build is
<code class="filename">qemux86</code>,
which produces an image that can be used in
the QEMU emulator and is targeted at an
<span class="trademark">Intel</span>®
32-bit based architecture.
Further on in this example, this default is
easily changed through the
<a class="link" href="#var-MACHINE" target="_top"><code class="filename">MACHINE</code></a>
variable so that you can quickly
build an image for a different machine.
</p></li><li class="listitem"><p>
Another consideration before you build is the
package manager used when creating the image.
The default <code class="filename">local.conf</code>
file selects the RPM package manager.
You can control this configuration by using the
<code class="filename"><a class="link" href="#var-PACKAGE_CLASSES" target="_top"><code class="filename">PACKAGE_CLASSES</code></a></code>
variable.</p><p>Selection of the package manager is separate
from whether package management is used at runtime
in the target image.</p><p>For additional package manager selection
information, see the
"<a class="link" href="#ref-classes-package" target="_top"><code class="filename">package.bbclass</code></a>"
section in the Yocto Project Reference Manual.
</p></li></ul></div><p>
</p></li><li class="listitem"><p><span class="emphasis"><em>Start the Build:</em></span>
Continue with the following command to build an OS image
for the target, which is
<code class="filename">core-image-sato</code> in this example:
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
Depending on the number of processors and cores, the
amount of RAM, the speed of your Internet connection
and other factors, the build process could take
several hours the first time you run it.
Subsequent builds run much faster since parts of the
build are cached.
</div><p>
</p><pre class="literallayout">
$ bitbake core-image-sato
</pre><p>
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
If you experience a build error due to resources
temporarily being unavailable and it appears you
should not be having this issue, it might be due
to the combination of a 4.3+ Linux kernel and
<code class="filename">systemd</code> version 228+
(i.e. see this
<a class="ulink" href="http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel" target="_top">link</a>
for information).
</p><p>
To work around this issue, you can try either
of the following:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
Try the build again.
</p></li><li class="listitem"><p>
Modify the "DefaultTasksMax"
<code class="filename">systemd</code> parameter
by uncommenting it and setting it to
"infinity".
You can find this parameter in the
<code class="filename">system.conf</code> file
located in
<code class="filename">/etc/systemd</code>
on most systems.
</p></li></ul></div><p>
</p></div><p>
For information on using the
<code class="filename">bitbake</code> command, see the
"<a class="link" href="#usingpoky-components-bitbake" target="_top">BitBake</a>"
section in the Yocto Project Reference Manual, or see the
"<a class="ulink" href="http://www.yoctoproject.org/docs/2.3/bitbake-user-manual/bitbake-user-manual.html#bitbake-user-manual-command" target="_top">BitBake Command</a>"
section in the BitBake User Manual.
For information on other targets, see the
"<a class="link" href="#ref-images" target="_top">Images</a>"
chapter in the Yocto Project Reference Manual.
</p></li><li class="listitem"><p><span class="emphasis"><em>Simulate Your Image Using QEMU:</em></span>
Once this particular image is built, you can start QEMU
and run the image:
</p><pre class="literallayout">
$ runqemu qemux86
</pre><p>
If you want to learn more about running QEMU, see the
"<a class="link" href="#dev-manual-qemu" target="_top">Using the Quick EMUlator (QEMU)</a>"
chapter in the Yocto Project Development Manual.
</p></li><li class="listitem"><p><span class="emphasis"><em>Exit QEMU:</em></span>
Exit QEMU by either clicking on the shutdown icon or by
opening a terminal, typing
<code class="filename">poweroff</code>, and then pressing "Enter".
</p></li></ol></div><p>
</p></div><div class="section" title="4.2. Building an Image for Hardware"><div class="titlepage"><div><div><h3 class="title" id="building-an-image-for-hardware">4.2. Building an Image for Hardware<span class="permalink"><a alt="Permalink" title="Permalink" href="#building-an-image-for-hardware">¶</a></span></h3></div></div></div><p><a id="qs-minnowboard-example"></a>
The following steps show how easy it is to set up to build an
image for a new machine.
These steps build an image for the MinnowBoard MAX, which is
supported by the Yocto Project and the
<code class="filename">meta-intel</code> <code class="filename">intel-corei7-64</code>
and <code class="filename">intel-core2-32</code> Board Support Packages
(BSPs).
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
The MinnowBoard MAX ships with 64-bit firmware.
If you want to use the board in 32-bit mode, you must
download the
<a class="ulink" href="http://firmware.intel.com/projects/minnowboard-max" target="_top">32-bit firmware</a>.
</div><p>
</p><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><span class="emphasis"><em>Create a Local Copy of the
<code class="filename">meta-intel</code> Repository:</em></span>
Building an image for the MinnowBoard MAX requires the
<code class="filename">meta-intel</code> layer.
Use the <code class="filename">git clone</code> command to create
a local copy of the repository inside your
<a class="link" href="#source-directory" target="_top">Source Directory</a>,
which is <code class="filename">poky</code> in this example:
</p><pre class="literallayout">
$ cd $HOME/poky
$ git clone git://git.yoctoproject.org/meta-intel
Cloning into 'meta-intel'...
remote: Counting objects: 11988, done.
remote: Compressing objects: 100% (3884/3884), done.
Receiving objects: 100% (11988/11988), 2.93 MiB | 2.51 MiB/s, done.
remote: Total 11988 (delta 6881), reused 11752 (delta 6645)
Resolving deltas: 100% (6881/6881), done.
Checking connectivity... done.
</pre><p>
By default when you clone a Git repository, the
"master" branch is checked out.
Before you build your image that uses the
<code class="filename">meta-intel</code> layer, you must be
sure that both repositories
(<code class="filename">meta-intel</code> and
<code class="filename">poky</code>) are using the same releases.
Consequently, you need to checkout out the
"<code class="filename">pyro</code>" release after
cloning <code class="filename">meta-intel</code>:
</p><pre class="literallayout">
$ cd $HOME/poky/meta-intel
$ git checkout pyro
Branch pyro set up to track remote branch pyro from origin.
Switched to a new branch 'pyro'
</pre><p>
</p></li><li class="listitem"><p><span class="emphasis"><em>Configure the Build:</em></span>
To configure the build, you edit the
<code class="filename">bblayers.conf</code> and
<code class="filename">local.conf</code> files, both of which are
located in the <code class="filename">build/conf</code> directory.
</p><p>Here is a quick way to make the edits.
The first command uses the
<code class="filename">bitbake-layers add-layer</code> command
to add the <code class="filename">meta-intel</code>
layer, which contains the <code class="filename">intel-core*</code>
BSPs to the build.
The second command selects the BSP by setting the
<a class="link" href="#var-MACHINE" target="_top"><code class="filename">MACHINE</code></a>
variable.
</p><pre class="literallayout">
$ cd $HOME/poky/build
$ bitbake-layers add-layer "$HOME/poky/meta-intel"
$ echo 'MACHINE = "intel-corei7-64"' >> conf/local.conf
</pre><p>
</p><div class="note" title="Notes" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Notes</h3><p>
If you want a 64-bit build, use the following:
</p><pre class="literallayout">
$ echo 'MACHINE = "intel-corei7-64"' >> conf/local.conf
</pre><p>
</p><p>
If you want 32-bit images, use the following:
</p><pre class="literallayout">
$ echo 'MACHINE = "intel-core2-32"' >> conf/local.conf
</pre><p>
</p></div><p>
</p></li><li class="listitem"><p><span class="emphasis"><em>Build an Image for MinnowBoard MAX:</em></span>
The type of image you build depends on your goals.
For example, the previous build created a
<code class="filename">core-image-sato</code> image, which is an
image with Sato support.
It is possible to build many image types for the
MinnowBoard MAX.
Some possibilities are <code class="filename">core-image-base</code>,
which is a console-only image.
Another choice could be a
<code class="filename">core-image-full-cmdline</code>, which is
another console-only image but has more full-features
Linux system functionality installed.
For types of images you can build using the Yocto
Project, see the
"<a class="link" href="#ref-images" target="_top">Images</a>"
chapter in the Yocto Project Reference Manual.</p><p>Because configuration changes are minimal to set up
for this second build, the OpenEmbedded build system can
re-use files from previous builds as much as possible.
Re-using files means this second build will be much faster
than an initial build.
For this example, the <code class="filename">core-image-base</code>
image is built:
</p><pre class="literallayout">
$ bitbake core-image-base
</pre><p>
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
If you experience a build error due to resources
temporarily being unavailable and it appears you
should not be having this issue, it might be due
to the combination of a 4.3+ Linux kernel and
<code class="filename">systemd</code> version 228+
(i.e. see this
<a class="ulink" href="http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel" target="_top">link</a>
for information).
</p><p>
To work around this issue, you can try either
of the following:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
Try the build again.
</p></li><li class="listitem"><p>
Modify the "DefaultTasksMax"
<code class="filename">systemd</code> parameter
by uncommenting it and setting it to
"infinity".
You can find this parameter in the
<code class="filename">system.conf</code> file
located in
<code class="filename">/etc/systemd</code>
on most systems.
</p></li></ul></div><p>
</p></div><p>
Once the build completes, the resulting console-only image
is located in the Build Directory here:
</p><pre class="literallayout">
tmp/deploy/images/intel-corei7-64/core-image-base-intel-corei7-64.wic
</pre><p>
</p></li><li class="listitem"><p><span class="emphasis"><em>Write the Image:</em></span>
You can write the image just built to a bootable media
(e.g. a USB key, SATA drive, SD card, etc.) using the
<code class="filename">dd</code> utility:
</p><pre class="literallayout">
$ sudo dd if=tmp/deploy/images/intel-corei7-64/core-image-base-intel-corei7-64.wic of=TARGET_DEVICE
</pre><p>
In the previous command, the
<code class="filename">TARGET_DEVICE</code> is the device node in
the host machine (e.g. <code class="filename">/dev/sdc</code>, which
is most likely a USB stick, or
<code class="filename">/dev/mmcblk0</code>, which is most likely an
SD card).
</p></li><li class="listitem"><p><span class="emphasis"><em>Boot the Hardware:</em></span>
With the boot device provisioned, you can insert the
media into the MinnowBoard MAX and boot the hardware.
The board should automatically detect the media and boot to
the bootloader and subsequently the operating system.
</p><p>If the board does not boot automatically, you can
boot it manually from the EFI shell as follows:
</p><pre class="literallayout">
Shell> connect -r
Shell> map -r
Shell> fs0:
Shell> bootx64
</pre><p>
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
For a 32-bit image use the following:
<pre class="literallayout">
Shell> bootia32
</pre></div><p>
</p></li></ol></div><p>
</p></div></div><div class="section" title="5. Next Steps"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="qs-next-steps">5. Next Steps<span class="permalink"><a alt="Permalink" title="Permalink" href="#qs-next-steps">¶</a></span></h2></div></div></div><p>
If you completed all the steps in the previous section then
congratulations!
What now?
</p><p>
Depending on what you primary interests are with the Yocto P
</p>
</div>
</div>
</div>
</body>
</html>
// Code goes here
/* Styles go here */
.element { position:fixed; top:2%; right:2%; }
/*
Generic XHTML / DocBook XHTML CSS Stylesheet.
Browser wrangling and typographic design by
Oyvind Kolas / pippin@gimp.org
Customised for Poky by
Matthew Allum / mallum@o-hand.com
Thanks to:
Liam R. E. Quin
William Skaggs
Jakub Steiner
Structure
---------
The stylesheet is divided into the following sections:
Positioning
Margins, paddings, width, font-size, clearing.
Decorations
Borders, style
Colors
Colors
Graphics
Graphical backgrounds
Nasty IE tweaks
Workarounds needed to make it work in internet explorer,
currently makes the stylesheet non validating, but up until
this point it is validating.
Mozilla extensions
Transparency for footer
Rounded corners on boxes
*/
/*************** /
/ Positioning /
/ ***************/
body {
font-family: Verdana, Sans, sans-serif;
min-width: 640px;
width: 80%;
margin: 0em auto;
padding: 2em 5em 5em 5em;
color: #333;
}
h1,h2,h3,h4,h5,h6,h7 {
font-family: Arial, Sans;
color: #00557D;
clear: both;
}
h1 {
font-size: 2em;
text-align: left;
padding: 0em 0em 0em 0em;
margin: 2em 0em 0em 0em;
}
h2.subtitle {
margin: 0.10em 0em 3.0em 0em;
padding: 0em 0em 0em 0em;
font-size: 1.8em;
padding-left: 20%;
font-weight: normal;
font-style: italic;
}
h2 {
margin: 2em 0em 0.66em 0em;
padding: 0.5em 0em 0em 0em;
font-size: 1.5em;
font-weight: bold;
}
h3.subtitle {
margin: 0em 0em 1em 0em;
padding: 0em 0em 0em 0em;
font-size: 142.14%;
text-align: right;
}
h3 {
margin: 1em 0em 0.5em 0em;
padding: 1em 0em 0em 0em;
font-size: 140%;
font-weight: bold;
}
h4 {
margin: 1em 0em 0.5em 0em;
padding: 1em 0em 0em 0em;
font-size: 120%;
font-weight: bold;
}
h5 {
margin: 1em 0em 0.5em 0em;
padding: 1em 0em 0em 0em;
font-size: 110%;
font-weight: bold;
}
h6 {
margin: 1em 0em 0em 0em;
padding: 1em 0em 0em 0em;
font-size: 110%;
font-weight: bold;
}
.authorgroup {
background-color: transparent;
background-repeat: no-repeat;
padding-top: 256px;
background-image: url("figures/mega-title.png");
background-position: left top;
margin-top: -256px;
padding-right: 50px;
margin-left: 0px;
text-align: right;
width: 740px;
}
h3.author {
margin: 0em 0em 0em 0em;
padding: 0em 0em 0em 0em;
font-weight: normal;
font-size: 100%;
color: #333;
clear: both;
}
.author tt.email {
font-size: 66%;
}
.titlepage hr {
width: 0em;
clear: both;
}
.revhistory {
padding-top: 2em;
clear: both;
}
.toc,
.list-of-tables,
.list-of-examples,
.list-of-figures {
padding: 1.33em 0em 2.5em 0em;
color: #00557D;
}
.toc p,
.list-of-tables p,
.list-of-figures p,
.list-of-examples p {
padding: 0em 0em 0em 0em;
padding: 0em 0em 0.3em;
margin: 1.5em 0em 0em 0em;
}
.toc p b,
.list-of-tables p b,
.list-of-figures p b,
.list-of-examples p b{
font-size: 100.0%;
font-weight: bold;
}
.toc dl,
.list-of-tables dl,
.list-of-figures dl,
.list-of-examples dl {
margin: 0em 0em 0.5em 0em;
padding: 0em 0em 0em 0em;
}
.toc dt {
margin: 0em 0em 0em 0em;
padding: 0em 0em 0em 0em;
}
.toc dd {
margin: 0em 0em 0em 2.6em;
padding: 0em 0em 0em 0em;
}
div.glossary dl,
div.variablelist dl {
}
.glossary dl dt,
.variablelist dl dt,
.variablelist dl dt span.term {
font-weight: normal;
width: 20em;
text-align: right;
}
.variablelist dl dt {
margin-top: 0.5em;
}
.glossary dl dd,
.variablelist dl dd {
margin-top: -1em;
margin-left: 25.5em;
}
.glossary dd p,
.variablelist dd p {
margin-top: 0em;
margin-bottom: 1em;
}
div.calloutlist table td {
padding: 0em 0em 0em 0em;
margin: 0em 0em 0em 0em;
}
div.calloutlist table td p {
margin-top: 0em;
margin-bottom: 1em;
}
div p.copyright {
text-align: left;
}
div.legalnotice p.legalnotice-title {
margin-bottom: 0em;
}
p {
line-height: 1.5em;
margin-top: 0em;
}
dl {
padding-top: 0em;
}
hr {
border: solid 1px;
}
.mediaobject,
.mediaobjectco {
text-align: center;
}
img {
border: none;
}
ul {
padding: 0em 0em 0em 1.5em;
}
ul li {
padding: 0em 0em 0em 0em;
}
ul li p {
text-align: left;
}
table {
width :100%;
}
th {
padding: 0.25em;
text-align: left;
font-weight: normal;
vertical-align: top;
}
td {
padding: 0.25em;
vertical-align: top;
}
p a[id] {
margin: 0px;
padding: 0px;
display: inline;
background-image: none;
}
a {
text-decoration: underline;
color: #444;
}
pre {
overflow: auto;
}
a:hover {
text-decoration: underline;
/*font-weight: bold;*/
}
/* This style defines how the permalink character
appears by itself and when hovered over with
the mouse. */
[alt='Permalink'] { color: #eee; }
[alt='Permalink']:hover { color: black; }
div.informalfigure,
div.informalexample,
div.informaltable,
div.figure,
div.table,
div.example {
margin: 1em 0em;
padding: 1em;
page-break-inside: avoid;
}
div.informalfigure p.title b,
div.informalexample p.title b,
div.informaltable p.title b,
div.figure p.title b,
div.example p.title b,
div.table p.title b{
padding-top: 0em;
margin-top: 0em;
font-size: 100%;
font-weight: normal;
}
.mediaobject .caption,
.mediaobject .caption p {
text-align: center;
font-size: 80%;
padding-top: 0.5em;
padding-bottom: 0.5em;
}
.epigraph {
padding-left: 55%;
margin-bottom: 1em;
}
.epigraph p {
text-align: left;
}
.epigraph .quote {
font-style: italic;
}
.epigraph .attribution {
font-style: normal;
text-align: right;
}
span.application {
font-style: italic;
}
.programlisting {
font-family: monospace;
font-size: 80%;
white-space: pre;
margin: 1.33em 0em;
padding: 1.33em;
}
.tip,
.warning,
.caution,
.note {
margin-top: 1em;
margin-bottom: 1em;
}
/* force full width of table within div */
.tip table,
.warning table,
.caution table,
.note table {
border: none;
width: 100%;
}
.tip table th,
.warning table th,
.caution table th,
.note table th {
padding: 0.8em 0.0em 0.0em 0.0em;
margin : 0em 0em 0em 0em;
}
.tip p,
.warning p,
.caution p,
.note p {
margin-top: 0.5em;
margin-bottom: 0.5em;
padding-right: 1em;
text-align: left;
}
.acronym {
text-transform: uppercase;
}
b.keycap,
.keycap {
padding: 0.09em 0.3em;
margin: 0em;
}
.itemizedlist li {
clear: none;
}
.filename {
font-size: medium;
font-family: Courier, monospace;
}
div.navheader, div.heading{
position: absolute;
left: 0em;
top: 0em;
width: 100%;
background-color: #cdf;
width: 100%;
}
div.navfooter, div.footing{
position: fixed;
left: 0em;
bottom: 0em;
background-color: #eee;
width: 100%;
}
div.navheader td,
div.navfooter td {
font-size: 66%;
}
div.navheader table th {
/*font-family: Georgia, Times, serif;*/
/*font-size: x-large;*/
font-size: 80%;
}
div.navheader table {
border-left: 0em;
border-right: 0em;
border-top: 0em;
width: 100%;
}
div.navfooter table {
border-left: 0em;
border-right: 0em;
border-bottom: 0em;
width: 100%;
}
div.navheader table td a,
div.navfooter table td a {
color: #777;
text-decoration: none;
}
/* normal text in the footer */
div.navfooter table td {
color: black;
}
div.navheader table td a:visited,
div.navfooter table td a:visited {
color: #444;
}
/* links in header and footer */
div.navheader table td a:hover,
div.navfooter table td a:hover {
text-decoration: underline;
background-color: transparent;
color: #33a;
}
div.navheader hr,
div.navfooter hr {
display: none;
}
.qandaset tr.question td p {
margin: 0em 0em 1em 0em;
padding: 0em 0em 0em 0em;
}
.qandaset tr.answer td p {
margin: 0em 0em 1em 0em;
padding: 0em 0em 0em 0em;
}
.answer td {
padding-bottom: 1.5em;
}
.emphasis {
font-weight: bold;
}
/************* /
/ decorations /
/ *************/
.titlepage {
}
.part .title {
}
.subtitle {
border: none;
}
/*
h1 {
border: none;
}
h2 {
border-top: solid 0.2em;
border-bottom: solid 0.06em;
}
h3 {
border-top: 0em;
border-bottom: solid 0.06em;
}
h4 {
border: 0em;
border-bottom: solid 0.06em;
}
h5 {
border: 0em;
}
*/
.programlisting {
border: solid 1px;
}
div.figure,
div.table,
div.informalfigure,
div.informaltable,
div.informalexample,
div.example {
border: 1px solid;
}
.tip,
.warning,
.caution,
.note {
border: 1px solid;
}
.tip table th,
.warning table th,
.caution table th,
.note table th {
border-bottom: 1px solid;
}
.question td {
border-top: 1px solid black;
}
.answer {
}
b.keycap,
.keycap {
border: 1px solid;
}
div.navheader, div.heading{
border-bottom: 1px solid;
}
div.navfooter, div.footing{
border-top: 1px solid;
}
/********* /
/ colors /
/ *********/
body {
color: #333;
background: white;
}
a {
background: transparent;
}
a:hover {
background-color: #dedede;
}
h1,
h2,
h3,
h4,
h5,
h6,
h7,
h8 {
background-color: transparent;
}
hr {
border-color: #aaa;
}
.tip, .warning, .caution, .note {
border-color: #fff;
}
.tip table th,
.warning table th,
.caution table th,
.note table th {
border-bottom-color: #fff;
}
.warning {
background-color: #f0f0f2;
}
.caution {
background-color: #f0f0f2;
}
.tip {
background-color: #f0f0f2;
}
.note {
background-color: #f0f0f2;
}
.glossary dl dt,
.variablelist dl dt,
.variablelist dl dt span.term {
color: #044;
}
div.figure,
div.table,
div.example,
div.informalfigure,
div.informaltable,
div.informalexample {
border-color: #aaa;
}
pre.programlisting {
color: black;
background-color: #fff;
border-color: #aaa;
border-width: 2px;
}
.guimenu,
.guilabel,
.guimenuitem {
background-color: #eee;
}
b.keycap,
.keycap {
background-color: #eee;
border-color: #999;
}
div.navheader {
border-color: black;
}
div.navfooter {
border-color: black;
}
/*********** /
/ graphics /
/ ***********/
/*
body {
background-image: url("images/body_bg.jpg");
background-attachment: fixed;
}
.navheader,
.note,
.tip {
background-image: url("images/note_bg.jpg");
background-attachment: fixed;
}
.warning,
.caution {
background-image: url("images/warning_bg.jpg");
background-attachment: fixed;
}
.figure,
.informalfigure,
.example,
.informalexample,
.table,
.informaltable {
background-image: url("images/figure_bg.jpg");
background-attachment: fixed;
}
*/
h1,
h2,
h3,
h4,
h5,
h6,
h7{
}
/*
Example of how to stick an image as part of the title.
div.article .titlepage .title
{
background-image: url("figures/white-on-black.png");
background-position: center;
background-repeat: repeat-x;
}
*/
div.preface .titlepage .title,
div.colophon .title,
div.chapter .titlepage .title,
div.article .titlepage .title
{
}
div.section div.section .titlepage .title,
div.sect2 .titlepage .title {
background: none;
}
h1.title {
background-color: transparent;
background-repeat: no-repeat;
height: 256px;
text-indent: -9000px;
overflow:hidden;
}
h2.subtitle {
background-color: transparent;
text-indent: -9000px;
overflow:hidden;
width: 0px;
display: none;
}
/*************************************** /
/ pippin.gimp.org specific alterations /
/ ***************************************/
/*
div.heading, div.navheader {
color: #777;
font-size: 80%;
padding: 0;
margin: 0;
text-align: left;
position: absolute;
top: 0px;
left: 0px;
width: 100%;
height: 50px;
background: url('/gfx/heading_bg.png') transparent;
background-repeat: repeat-x;
background-attachment: fixed;
border: none;
}
div.heading a {
color: #444;
}
div.footing, div.navfooter {
border: none;
color: #ddd;
font-size: 80%;
text-align:right;
width: 100%;
padding-top: 10px;
position: absolute;
bottom: 0px;
left: 0px;
background: url('/gfx/footing_bg.png') transparent;
}
*/
/****************** /
/ nasty ie tweaks /
/ ******************/
/*
div.heading, div.navheader {
width:expression(document.body.clientWidth + "px");
}
div.footing, div.navfooter {
width:expression(document.body.clientWidth + "px");
margin-left:expression("-5em");
}
body {
padding:expression("4em 5em 0em 5em");
}
*/
/**************************************** /
/ mozilla vendor specific css extensions /
/ ****************************************/
/*
div.navfooter, div.footing{
-moz-opacity: 0.8em;
}
div.figure,
div.table,
div.informalfigure,
div.informaltable,
div.informalexample,
div.example,
.tip,
.warning,
.caution,
.note {
-moz-border-radius: 0.5em;
}
b.keycap,
.keycap {
-moz-border-radius: 0.3em;
}
*/
div.fixtop { position:fixed; top:2%; right:2%; }
table tr td table tr td {
display: none;
}
hr {
display: none;
}
table {
border: 0em;
}
.photo {
float: right;
margin-left: 1.5em;
margin-bottom: 1.5em;
margin-top: 0em;
max-width: 17em;
border: 1px solid gray;
padding: 3px;
background: white;
}
.seperator {
padding-top: 2em;
clear: both;
}
#validators {
margin-top: 5em;
text-align: right;
color: #777;
}
@media print {
body {
font-size: 8pt;
}
.noprint {
display: none;
}
}
.tip,
.note {
background: #f0f0f2;
color: #333;
padding: 20px;
margin: 20px;
}
.tip h3,
.note h3 {
padding: 0em;
margin: 0em;
font-size: 2em;
font-weight: bold;
color: #333;
}
.tip a,
.note a {
color: #333;
text-decoration: underline;
}
.footnote {
font-size: small;
color: #333;
}
/* Changes the announcement text */
.tip h3,
.warning h3,
.caution h3,
.note h3 {
font-size:large;
color: #00557D;
}