Integrate yocto documentation into eclipse

new file mode 100644
index 0000000..bc74aab
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6"/>
+	<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
+	<classpathentry kind="output" path="bin"/>
+</classpath>

new file mode 100644
index 0000000..d361cd4
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>org.yocto.sdk.doc.user</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+		<buildCommand>
+			<name>org.eclipse.jdt.core.javabuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+		<buildCommand>
+			<name>org.eclipse.pde.ManifestBuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+		<buildCommand>
+			<name>org.eclipse.pde.SchemaBuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+	</buildSpec>
+	<natures>
+		<nature>org.eclipse.pde.PluginNature</nature>
+		<nature>org.eclipse.jdt.core.javanature</nature>
+	</natures>
+</projectDescription>

new file mode 100644
index 0000000..f90fa9c
@@ -0,0 +1,8 @@
+#Fri Mar 04 13:59:33 CET 2011
+eclipse.preferences.version=1
+org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
+org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.6
+org.eclipse.jdt.core.compiler.compliance=1.6
+org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
+org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
+org.eclipse.jdt.core.compiler.source=1.6

new file mode 100644
index 0000000..6bece6b
@@ -0,0 +1,7 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %plugin.name
+Bundle-SymbolicName: org.yocto.sdk.doc.user;singleton:=true
+Bundle-Version: 1.2.0.qualifier
+Bundle-Vendor: %plugin.provider
+Bundle-RequiredExecutionEnvironment: JavaSE-1.6

new file mode 100644
index 0000000..61e70de
@@ -0,0 +1,3 @@
+#Properties file for org.yocto.sdk.doc.user
+Bundle-Vendor = yoctoproject.org
+Bundle-Name = Yocto Project Documentation

new file mode 100644
index 0000000..31e0140
@@ -0,0 +1,4 @@
+bin.includes = plugin.xml,\
+               .,\
+               META-INF/,\
+               OSGI-INF/

new file mode 100644
index 0000000..f422d55
@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.4"?>
+<plugin>
+</plugin>

index 6bece6b..b28168f 100644
@@ -5,3 +5,4 @@ Bundle-SymbolicName: org.yocto.sdk.doc.user;singleton:=true
 Bundle-Version: 1.2.0.qualifier
 Bundle-Vendor: %plugin.provider
 Bundle-RequiredExecutionEnvironment: JavaSE-1.6
+Require-Bundle: org.eclipse.help

index 31e0140..cc18fce 100644
@@ -1,4 +1,6 @@
 bin.includes = plugin.xml,\
                .,\
                META-INF/,\
+               toc.xml,\
                OSGI-INF/
+src.includes = toc.xml

index f422d55..367962c 100644
@@ -1,4 +1,11 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <?eclipse version="3.4"?>
 <plugin>
+ <extension
+       point="org.eclipse.help.toc">
+    <toc
+          file="toc.xml"
+          primary="true">
+    </toc>
+ </extension>
 </plugin>

new file mode 100644
index 0000000..4d30d0d
@@ -0,0 +1,3 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<toc label="The Yocto Project Documentation">
+</toc>

new file mode 100644
index 0000000..7418615
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>org.yocto.sdk.doc</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+		<buildCommand>
+			<name>org.eclipse.pde.FeatureBuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+	</buildSpec>
+	<natures>
+		<nature>org.eclipse.pde.FeatureNature</nature>
+	</natures>
+</projectDescription>

new file mode 100644
index 0000000..b0439e2
@@ -0,0 +1,5 @@
+bin.includes = feature.xml,\
+               feature.properties,\
+               license.html
+
[email protected]=org.yocto.sdk.doc

208 lines not on this page · raw message

new file mode 100644
index 0000000..f4b7605
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feature
+      id="org.yocto.sdk.doc"
+      label="%featureName"
+      version="1.2.0.qualifier"
+      provider-name="%providerName">
+
+   <description>
+      %description
+   </description>
+
+   <copyright>
+      %copyright
+   </copyright>
+
+   <license url="%licenseURL">
+      %license
+   </license>
+
+   <url>
+      <update label="%updateSiteName" url="http://yoctoproject.org/downloads/eclipse-plugin/"/>
+   </url>
+
+   <includes
+         id="org.yocto.sdk.doc.source"
+         version="0.0.0"/>
+
+   <requires>
+      <import plugin="org.eclipse.ui.cheatsheets"/>
+      <import plugin="org.eclipse.help"/>
+   </requires>
+</feature>

237 lines not on this page · raw message

208 lines not on this page · raw message

237 lines not on this page · raw message

index f4b7605..1300f55 100644
@@ -29,4 +29,12 @@
       <import plugin="org.eclipse.ui.cheatsheets"/>
       <import plugin="org.eclipse.help"/>
    </requires>
+
+   <plugin
+         id="org.yocto.sdk.doc.user"
+         download-size="0"
+         install-size="0"
+         version="0.0.0"
+         unpack="false"/>
+
 </feature>

index 785a7be..94ad007 100644
@@ -8,6 +8,7 @@
    
     Contributors:
         Intel - initial API and implementation
+        BMW Car IT GmbH - added yocto documentation feature
  -->
 <feature
       id="org.yocto.sdk"

@@ -34,6 +35,10 @@
    <includes
          id="org.yocto.sdk.source"/>
 
+   <includes
+         id="org.yocto.sdk.doc"
+         version="0.0.0"/>
+
    <requires>
       <import plugin="org.eclipse.core.runtime"/>
       <import plugin="org.eclipse.osgi"/>

index 9fb50b2..e21f3fb 100644
@@ -6,5 +6,11 @@
    <feature url="features/org.yocto.sdk.source_@[email protected]" id="org.yocto.sdk.source" version="@featureVerion@">
       <category name="Yocto SDK"/>
    </feature>
+   <feature url="features/org.yocto.sdk.doc_@[email protected]" id="org.yocto.sdk.doc" version="@featureVerion@">
+      <category name="Yocto SDK"/>
+   </feature>
+   <feature url="features/org.yocto.sdk.doc.source_@[email protected]" id="org.yocto.sdk.doc.source" version="@featureVerion@">
+      <category name="Yocto SDK"/>
+   </feature>
    <category-def name="Yocto SDK" label="Development tools &amp; SDKs for Yocto Linux"/>
 </site>

index 59ebbd5..e33e91a 100644
@@ -6,5 +6,8 @@
    <feature url="features/org.yocto.sdk_@[email protected]" id="org.yocto.sdk" version="@genVerion@">
       <category name="Yocto SDK"/>
    </feature>
+   <feature url="features/org.yocto.sdk.doc_@[email protected]" id="org.yocto.sdk.doc" version="@genVerion@">
+      <category name="Yocto SDK"/>
+   </feature>
    <category-def name="Yocto SDK" label="Development tools &amp; SDKs for Yocto Linux"/>
 </site>

new file mode 100644
index 0000000..d62c5d1
@@ -0,0 +1,58 @@
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+	"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<title>About</title>
+</head>
+<body lang="EN-US">
+	<h2>About This Content</h2>
+
+	<p>
+		<em>July 3, 2012</em>
+	</p>
+	<h3>License</h3>
+
+	<p>
+		Copyright (c) 2010 Intel, Inc. and others. <br />
+		All rights reserved. This program and the accompanying materials
+		are made available under the terms of the Creative Commons Attribution-Share
+		Alike 2.0 UK: England & Wales which accompanies this distribution,
+		and is available at <br />
+		<a href="http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode">
+			http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode
+		</a>
+	</p>
+
+	<h3>Third Party Content</h3>
+	<p>The Content includes items that have been sourced from the Yocto project
+		as set out below. If you did not receive this Content directly
+		from the Linux Foundation, the following is provided for
+		informational purposes only, and you should look to the
+		Redistributor's license for terms and conditions of use.</p>
+	<p>
+		<strong>
+			Yocto Project Quick Start
+		</strong>
+		<br />
+		<br />
+			This short document lets you get started with the Yocto Project
+			quickly and start building an image.
+		<br />
+		<br />
+			<em>License:</em>
+			<a href="http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode">
+				http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode
+			</a>
+		<br />
+			<em>Source Code Repository:</em>
+			<a href="git://git.yoctoproject.org/yocto-docs">
+				git://git.yoctoproject.org/yocto-docs
+			</a>
+		<br />
+			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
+	</p>
+</body>
+</html>
+

index cc18fce..546b6fd 100644
@@ -1,6 +1,12 @@
 bin.includes = plugin.xml,\
                .,\
                META-INF/,\
+               html/,\
                toc.xml,\
+               yocto-project-qs-toc.xml,\
+               about.html,\
                OSGI-INF/
-src.includes = toc.xml
+src.includes = toc.xml, \
+               html/,\
+               yocto-project-qs-toc.xml,\
+               about.html

new file mode 100644
index 0000000..e4e0117
@@ -0,0 +1 @@
+@import "PLUGINS_ROOT/PRODUCT_PLUGIN/book.css";
\ No newline at end of file

new file mode 100755
index 0000000000000000000000000000000000000000..1fbea5ab008e1dc864105851173e7ed64edd4b71
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..b03130d123963ffe0a07c523d4772973887b9679
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..82b7a55a35c097c8f9104d5d960e19fb200fb4c8
GIT binary patch

new file mode 100755
index 0000000000000000000000000000000000000000..31d2b147fdb5e23f84d64652faf9528d83be7d8d
GIT binary patch

863 lines not on this page · raw message

index 367962c..e211b6a 100644
@@ -7,5 +7,9 @@
           file="toc.xml"
           primary="true">
     </toc>
+    <toc
+          file="yocto-project-qs-toc.xml"
+          primary="false">
+    </toc>
  </extension>
 </plugin>

index 4d30d0d..9be9cf5 100644
@@ -1,3 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <toc label="The Yocto Project Documentation">
+   <topic label="The Yocto Project Quick Start">
+      <link toc="yocto-project-qs-toc.xml"/>
+   </topic>
 </toc>

new file mode 100644
index 0000000..5e62311
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="utf-8" standalone="no"?>
+<toc label="The Yocto Project Quick Start" topic="html/yocto-project-qs/index.html">
+  <topic label="The Yocto Project Quick Start" href="html/yocto-project-qs/index.html#fake-title"/>
+  <topic label="Welcome!" href="html/yocto-project-qs/index.html#welcome"/>
+  <topic label="Introducing the Yocto Project Development Environment" href="html/yocto-project-qs/index.html#yp-intro"/>
+  <topic label="What You Need and How You Get It" href="html/yocto-project-qs/index.html#yp-resources">
+    <topic label="The Linux Distribution" href="html/yocto-project-qs/index.html#the-linux-distro"/>
+    <topic label="The Packages" href="html/yocto-project-qs/index.html#packages">
+      <topic label="Ubuntu" href="html/yocto-project-qs/index.html#ubuntu"/>
+      <topic label="Fedora" href="html/yocto-project-qs/index.html#fedora"/>
+      <topic label="openSUSE" href="html/yocto-project-qs/index.html#opensuse"/>
+      <topic label="CentOS" href="html/yocto-project-qs/index.html#centos"/>
+    </topic>
+    <topic label="Yocto Project Release" href="html/yocto-project-qs/index.html#releases"/>
+  </topic>
+  <topic label="A Quick Test Run" href="html/yocto-project-qs/index.html#test-run">
+    <topic label="Building an Image" href="html/yocto-project-qs/index.html#building-image"/>
+    <topic label="Using Pre-Built Binaries and QEMU" href="html/yocto-project-qs/index.html#using-pre-built">
+      <topic label="Installing the Toolchain" href="html/yocto-project-qs/index.html#installing-the-toolchain"/>
+      <topic label="Downloading the Pre-Built Linux Kernel" href="html/yocto-project-qs/index.html#downloading-the-pre-built-linux-kernel"/>
+      <topic label="Downloading the Filesystem" href="html/yocto-project-qs/index.html#downloading-the-filesystem"/>
+      <topic label="Setting Up the Environment and Starting the QEMU Emulator" href="html/yocto-project-qs/index.html#setting-up-the-environment-and-starting-the-qemu-emulator"/>
+    </topic>
+  </topic>
+  <topic label="Super User" href="html/yocto-project-qs/index.html#super-user">
+    <topic label="Getting the Yocto Project" href="html/yocto-project-qs/index.html#getting-yocto"/>
+    <topic label="Setting Up Your Host" href="html/yocto-project-qs/index.html#setting-up-your-host"/>
+    <topic label="Initializing the Build Environment" href="html/yocto-project-qs/index.html#initializing-the-build-environment"/>
+    <topic label="Configuring the local.conf File" href="html/yocto-project-qs/index.html#configuring-the-local.conf-file"/>
+    <topic label="Building the Image" href="html/yocto-project-qs/index.html#building-the-image"/>
+  </topic>
+</toc>

index d62c5d1..303a3a6 100644
@@ -52,6 +52,29 @@
 			</a>
 		<br />
 			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
+		<br />
+		<br />
+		<strong>
+			The Yocto Project Application Developer's Guide:
+		</strong>
+		<br />
+		<br />
+			This manual shows you how to setup and use the Application Development
+			Toolkit (ADT) and stand-alone cross-development toolchains so you can
+			develop user-space applications.
+		<br />
+		<br />
+			<em>License:</em>
+			<a href="http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode">
+				http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode
+			</a>
+		<br />
+			<em>Source Code Repository:</em>
+			<a href="git://git.yoctoproject.org/yocto-docs">
+				git://git.yoctoproject.org/yocto-docs
+			</a>
+		<br />
+			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
 	</p>
 </body>
 </html>

new file mode 100644
index 0000000..651bf07
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="utf-8" standalone="no"?>
+<toc label="The Yocto Project Application Developer's Guide" topic="html/adt-manual/index.html">
+  <topic label="Introduction" href="html/adt-manual/adt-intro.html">
+    <topic label="The Application Development Toolkit (ADT)" href="html/adt-manual/adt-intro-section.html">
+      <topic label="The Cross-Toolchain" href="html/adt-manual/the-cross-toolchain.html"/>
+      <topic label="Sysroot" href="html/adt-manual/sysroot.html"/>
+      <topic label="Eclipse Yocto Plug-in" href="html/adt-manual/eclipse-overview.html"/>
+      <topic label="The QEMU Emulator" href="html/adt-manual/the-qemu-emulator.html"/>
+      <topic label="User-Space Tools" href="html/adt-manual/user-space-tools.html"/>
+    </topic>
+  </topic>
+  <topic label="Preparing for Application Development" href="html/adt-manual/adt-prepare.html">
+    <topic label="Installing the ADT and Toolchains" href="html/adt-manual/installing-the-adt.html">
+      <topic label="Using the ADT Installer" href="html/adt-manual/using-the-adt-installer.html">
+        <topic label="Getting the ADT Installer Tarball" href="html/adt-manual/getting-the-adt-installer-tarball.html"/>
+        <topic label="Configuring and Running the ADT Installer Script" href="html/adt-manual/configuring-and-running-the-adt-installer-script.html"/>
+      </topic>
+      <topic label="Using a Cross-Toolchain Tarball" href="html/adt-manual/using-an-existing-toolchain-tarball.html"/>
+      <topic label="Using BitBake and the Build Directory" href="html/adt-manual/using-the-toolchain-from-within-the-build-tree.html"/>
+    </topic>
+    <topic label="Setting Up the Cross-Development Environment" href="html/adt-manual/setting-up-the-cross-development-environment.html"/>
+    <topic label="Securing Kernel and Filesystem Images" href="html/adt-manual/securing-kernel-and-filesystem-images.html">
+      <topic label="Getting the Images" href="html/adt-manual/getting-the-images.html"/>
+      <topic label="Extracting the Root Filesystem" href="html/adt-manual/extracting-the-root-filesystem.html"/>
+    </topic>
+  </topic>
+  <topic label="Optionally Customizing the Development Packages Installation" href="html/adt-manual/adt-package.html">
+    <topic label="Package Management Systems" href="html/adt-manual/package-management-systems.html"/>
+    <topic label="Configuring the PMS" href="html/adt-manual/configuring-the-pms.html"/>
+  </topic>
+  <topic label="Using the Command Line" href="html/adt-manual/using-the-command-line.html">
+    <topic label="Autotools-Based Projects" href="html/adt-manual/autotools-based-projects.html"/>
+    <topic label="Makefile-Based Projects" href="html/adt-manual/makefile-based-projects.html"/>
+  </topic>
+</toc>

index 546b6fd..b1659fe 100644
@@ -5,8 +5,10 @@ bin.includes = plugin.xml,\
                toc.xml,\
                yocto-project-qs-toc.xml,\
                about.html,\
+               adt-manual-toc.xml,\
                OSGI-INF/
 src.includes = toc.xml, \
                html/,\
                yocto-project-qs-toc.xml,\
-               about.html
+               about.html,\
+               adt-manual-toc.xml

new file mode 100644
index 0000000..4082048
@@ -0,0 +1,39 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.1.�The Application Development Toolkit (ADT)</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="adt-intro.html" title="Chapter�1.�Introduction">
+<link rel="prev" href="adt-intro.html" title="Chapter�1.�Introduction">
+<link rel="next" href="the-cross-toolchain.html" title="1.1.1.�The Cross-Toolchain">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.1.�The Application Development Toolkit (ADT)">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="adt-intro-section"></a>1.1.�The Application Development Toolkit (ADT)</h2></div></div></div>
+<p>
+        Part of the Yocto Project development solution is an Application Development 
+        Toolkit (ADT).
+        The ADT provides you with a custom-built, cross-development 
+        platform suited for developing a user-targeted product application.
+    </p>
+<p>
+        Fundamentally, the ADT consists of the following:
+        </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>An architecture-specific cross-toolchain and matching 
+                sysroot both built by the OpenEmbedded build system, which uses Poky.
+                The toolchain and sysroot are based on a metadata configuration and extensions, 
+                which allows you to cross-develop on the host machine for the target hardware.
+                </p></li>
+<li class="listitem"><p>The Eclipse IDE Yocto Plug-in.</p></li>
+<li class="listitem"><p>The Quick EMUlator (QEMU), which lets you simulate target hardware.
+                </p></li>
+<li class="listitem"><p>Various user-space tools that greatly enhance your application 
+                development experience.</p></li>
+</ul></div>
+<p>
+    </p>
+</div></body>
+</html>

44 lines not on this page · raw message

new file mode 100644
index 0000000..0a6f5a6
@@ -0,0 +1,30 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter�3.�Optionally Customizing the Development Packages Installation</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="prev" href="extracting-the-root-filesystem.html" title="2.3.2.�Extracting the Root Filesystem">
+<link rel="next" href="package-management-systems.html" title="3.1.�Package Management Systems">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter�3.�Optionally Customizing the Development Packages Installation">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="adt-package"></a>Chapter�3.�Optionally Customizing the Development Packages Installation</h2></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="package-management-systems.html">3.1. Package Management Systems</a></span></dt>
+<dt><span class="section"><a href="configuring-the-pms.html">3.2. Configuring the PMS</a></span></dt>
+</dl>
+</div>
+<p>
+        Because the Yocto Project is suited for embedded Linux development, it is 
+        likely that you will need to customize your development packages installation.  
+        For example, if you are developing a minimal image, then you might not need 
+        certain packages (e.g. graphics support packages).  
+        Thus, you would like to be able to remove those packages from your target sysroot.
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..8d9ffdd
@@ -0,0 +1,39 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter�2.�Preparing for Application Development</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="prev" href="user-space-tools.html" title="1.1.5.�User-Space Tools">
+<link rel="next" href="installing-the-adt.html" title="2.1.�Installing the ADT and Toolchains">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter�2.�Preparing for Application Development">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="adt-prepare"></a>Chapter�2.�Preparing for Application Development</h2></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="installing-the-adt.html">2.1. Installing the ADT and Toolchains</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="using-the-adt-installer.html">2.1.1. Using the ADT Installer</a></span></dt>
+<dt><span class="section"><a href="using-an-existing-toolchain-tarball.html">2.1.2. Using a Cross-Toolchain Tarball</a></span></dt>
+<dt><span class="section"><a href="using-the-toolchain-from-within-the-build-tree.html">2.1.3. Using BitBake and the Build Directory</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="setting-up-the-cross-development-environment.html">2.2. Setting Up the Cross-Development Environment</a></span></dt>
+<dt><span class="section"><a href="securing-kernel-and-filesystem-images.html">2.3. Securing Kernel and Filesystem Images</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="getting-the-images.html">2.3.1. Getting the Images</a></span></dt>
+<dt><span class="section"><a href="extracting-the-root-filesystem.html">2.3.2. Extracting the Root Filesystem</a></span></dt>
+</dl></dd>
+</dl>
+</div>
+<p>
+    In order to develop applications, you need set up your host development system.
+    Several ways exist that allow you to install cross-development tools, QEMU, the  
+    Eclipse Yocto Plug-in, and other tools.
+    This chapter describes how to prepare for application development.
+</p>
+</div></body>
+</html>

53 lines not on this page · raw message

130 lines not on this page · raw message

68 lines not on this page · raw message

new file mode 100644
index 0000000..cd874f7
@@ -0,0 +1,37 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.1.3.�Eclipse Yocto Plug-in</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="adt-intro-section.html" title="1.1.�The Application Development Toolkit (ADT)">
+<link rel="prev" href="sysroot.html" title="1.1.2.�Sysroot">
+<link rel="next" href="the-qemu-emulator.html" title="1.1.4.�The QEMU Emulator">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.1.3.�Eclipse Yocto Plug-in">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="eclipse-overview"></a>1.1.3.�Eclipse Yocto Plug-in</h3></div></div></div>
+<p>
+            The Eclipse IDE is a popular development environment and it fully supports 
+            development using the Yocto Project.  
+            When you install and configure the Eclipse Yocto Project Plug-in into 
+            the Eclipse IDE, you maximize your Yocto Project experience.  
+            Installing and configuring the Plug-in results in an environment that 
+            has extensions specifically designed to let you more easily develop software.  
+            These extensions allow for cross-compilation, deployment, and execution of 
+            your output into a QEMU emulation session.  
+            You can also perform cross-debugging and profiling.  
+            The environment also supports a suite of tools that allows you to perform 
+            remote profiling, tracing, collection of power data, collection of 
+            latency data, and collection of performance data.
+        </p>
+<p>
+            For information about the application development workflow that uses the Eclipse
+            IDE and for a detailed example of how to install and configure the Eclipse
+            Yocto Project Plug-in, see the 
+            "<a class="link" href="../dev-manual/adt-eclipse.html" target="_self">Working Within Eclipse</a>" section
+            of the Yocto Project Development Manual.
+        </p>
+</div></body>
+</html>

45 lines not on this page · raw message

new file mode 100644
index 0000000000000000000000000000000000000000..6e71e41f1a90e50e45a296613a5498deb331ea66
GIT binary patch

50 lines not on this page · raw message

100 lines not on this page · raw message

130 lines not on this page · raw message

59 lines not on this page · raw message

new file mode 100644
index 0000000..e977aaa
@@ -0,0 +1,28 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>4.2.�Makefile-Based Projects</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="using-the-command-line.html" title="Chapter�4.�Using the Command Line">
+<link rel="prev" href="autotools-based-projects.html" title="4.1.�Autotools-Based Projects">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.2.�Makefile-Based Projects">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="makefile-based-projects"></a>4.2.�Makefile-Based Projects</h2></div></div></div>
+<p>
+        For a Makefile-based project, you use the cross-toolchain by making sure 
+        the tools are used.  
+        You can do this as follows:
+        </p>
+<pre class="literallayout">
+     CC=arm-poky-linux-gnueabi-gcc
+     LD=arm-poky-linux-gnueabi-ld
+     CFLAGS=&#8221;${CFLAGS} --sysroot=&lt;sysroot-dir&gt;&#8221;
+     CXXFLAGS=&#8221;${CXXFLAGS} --sysroot=&lt;sysroot-dir&gt;&#8221;
+        </pre>
+<p>
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..c77a163
@@ -0,0 +1,40 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.1.�Package Management Systems</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="adt-package.html" title="Chapter�3.�Optionally Customizing the Development Packages Installation">
+<link rel="prev" href="adt-package.html" title="Chapter�3.�Optionally Customizing the Development Packages Installation">
+<link rel="next" href="configuring-the-pms.html" title="3.2.�Configuring the PMS">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.1.�Package Management Systems">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="package-management-systems"></a>3.1.�Package Management Systems</h2></div></div></div>
+<p>
+        The OpenEmbedded build system supports the generation of sysroot files using 
+        three different Package Management Systems (PMS):
+        </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p><span class="emphasis"><em>OPKG:</em></span> A less well known PMS whose use 
+                originated in the OpenEmbedded and OpenWrt embedded Linux projects.  
+                This PMS works with files packaged in an <code class="filename">.ipk</code> format.
+                See <a class="ulink" href="http://en.wikipedia.org/wiki/Opkg" target="_self">http://en.wikipedia.org/wiki/Opkg</a> for more 
+                information about OPKG.</p></li>
+<li class="listitem"><p><span class="emphasis"><em>RPM:</em></span> A more widely known PMS intended for GNU/Linux 
+                distributions.  
+                This PMS works with files packaged in an <code class="filename">.rms</code> format.
+                The build system currently installs through this PMS by default.  
+                See <a class="ulink" href="http://en.wikipedia.org/wiki/RPM_Package_Manager" target="_self">http://en.wikipedia.org/wiki/RPM_Package_Manager</a>
+                for more information about RPM.</p></li>
+<li class="listitem"><p><span class="emphasis"><em>Debian:</em></span> The PMS for Debian-based systems 
+                is built on many PMS tools.  
+                The lower-level PMS tool <code class="filename">dpkg</code> forms the base of the Debian PMS.  
+                For information on dpkg see 
+                <a class="ulink" href="http://en.wikipedia.org/wiki/Dpkg" target="_self">http://en.wikipedia.org/wiki/Dpkg</a>.</p></li>
+</ul></div>
+<p>
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..8a24629
@@ -0,0 +1,22 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.3.�Securing Kernel and Filesystem Images</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="adt-prepare.html" title="Chapter�2.�Preparing for Application Development">
+<link rel="prev" href="setting-up-the-cross-development-environment.html" title="2.2.�Setting Up the Cross-Development Environment">
+<link rel="next" href="getting-the-images.html" title="2.3.1.�Getting the Images">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.�Securing Kernel and Filesystem Images">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="securing-kernel-and-filesystem-images"></a>2.3.�Securing Kernel and Filesystem Images</h2></div></div></div>
+<p>
+        You will need to have a kernel and filesystem image to boot using your 
+        hardware or the QEMU emulator.
+        Furthermore, if you plan on booting your image using NFS or you want to use the root filesystem
+        as the target sysroot, you need to extract the root filesystem.
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..c209ef8
@@ -0,0 +1,40 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.2.�Setting Up the Cross-Development Environment</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="adt-prepare.html" title="Chapter�2.�Preparing for Application Development">
+<link rel="prev" href="using-the-toolchain-from-within-the-build-tree.html" title="2.1.3.�Using BitBake and the Build Directory">
+<link rel="next" href="securing-kernel-and-filesystem-images.html" title="2.3.�Securing Kernel and Filesystem Images">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.2.�Setting Up the Cross-Development Environment">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="setting-up-the-cross-development-environment"></a>2.2.�Setting Up the Cross-Development Environment</h2></div></div></div>
+<p>
+        Before you can develop using the cross-toolchain, you need to set up the 
+        cross-development environment by sourcing the toolchain's environment setup script.  
+        If you used the ADT Installer or hand-installed cross-toolchain,
+        then you can find this script in the <code class="filename">/opt/poky/1.3</code>
+        directory.  
+        If you installed the toolchain in the 
+        <a class="link" href="../dev-manual/build-directory.html" target="_self">build directory</a>, 
+        you can find the environment setup 
+        script for the toolchain in the build directory's <code class="filename">tmp</code> directory.
+    </p>
+<p> 
+        Be sure to run the environment setup script that matches the architecture for 
+        which you are developing.  
+        Environment setup scripts begin with the string &#8220;<code class="filename">environment-setup</code>&#8221;
+        and include as part of their name the architecture.  
+        For example, the toolchain environment setup script for a 64-bit IA-based architecture would 
+        be the following: 
+        </p>
+<pre class="literallayout">
+     /opt/poky/1.3/environment-setup-x86_64-poky-linux
+        </pre>
+<p>
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..0bc6423
@@ -0,0 +1,23 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.1.2.�Sysroot</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="adt-intro-section.html" title="1.1.�The Application Development Toolkit (ADT)">
+<link rel="prev" href="the-cross-toolchain.html" title="1.1.1.�The Cross-Toolchain">
+<link rel="next" href="eclipse-overview.html" title="1.1.3.�Eclipse Yocto Plug-in">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.1.2.�Sysroot">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="sysroot"></a>1.1.2.�Sysroot</h3></div></div></div>
+<p>
+            The matching target sysroot contains needed headers and libraries for generating 
+            binaries that run on the target architecture.  
+            The sysroot is based on the target root filesystem image that is built by 
+            the OpenEmbedded build system Poky and uses the same metadata configuration 
+            used to build the cross-toolchain.
+        </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..d40992b
@@ -0,0 +1,24 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.1.1.�The Cross-Toolchain</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="adt-intro-section.html" title="1.1.�The Application Development Toolkit (ADT)">
+<link rel="prev" href="adt-intro-section.html" title="1.1.�The Application Development Toolkit (ADT)">
+<link rel="next" href="sysroot.html" title="1.1.2.�Sysroot">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.1.1.�The Cross-Toolchain">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="the-cross-toolchain"></a>1.1.1.�The Cross-Toolchain</h3></div></div></div>
+<p>
+            The cross-toolchain consists of a cross-compiler, cross-linker, and cross-debugger 
+            that are used to develop user-space applications for targeted hardware.
+            This toolchain is created either by running the ADT Installer script, a toolchain installer
+            script, or through a build directory that is based on your metadata 
+            configuration or extension for your targeted device.  
+            The cross-toolchain works with a matching target sysroot.
+        </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..55f90a2
@@ -0,0 +1,34 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.1.4.�The QEMU Emulator</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="adt-intro-section.html" title="1.1.�The Application Development Toolkit (ADT)">
+<link rel="prev" href="eclipse-overview.html" title="1.1.3.�Eclipse Yocto Plug-in">
+<link rel="next" href="user-space-tools.html" title="1.1.5.�User-Space Tools">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.1.4.�The QEMU Emulator">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="the-qemu-emulator"></a>1.1.4.�The QEMU Emulator</h3></div></div></div>
+<p>
+            The QEMU emulator allows you to simulate your hardware while running your 
+            application or image.
+            QEMU is made available a number of ways:
+            </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>If you use the ADT Installer script to install ADT, you can 
+                    specify whether or not to install QEMU.</p></li>
+<li class="listitem"><p>If you have downloaded a Yocto Project release and unpacked 
+                    it to create a source directory and you have sourced  
+                    the environment setup script, QEMU is installed and automatically 
+                    available.</p></li>
+<li class="listitem"><p>If you have installed the cross-toolchain 
+                    tarball and you have sourcing the toolchain's setup environment script, QEMU
+                    is also installed and automatically available.</p></li>
+</ul></div>
+<p>
+        </p>
+</div></body>
+</html>

55 lines not on this page · raw message

90 lines not on this page · raw message

new file mode 100644
index 0000000..1433f17
@@ -0,0 +1,20 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.1.1.�Using the ADT Installer</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Application Developer's Guide">
+<link rel="up" href="installing-the-adt.html" title="2.1.�Installing the ADT and Toolchains">
+<link rel="prev" href="installing-the-adt.html" title="2.1.�Installing the ADT and Toolchains">
+<link rel="next" href="getting-the-adt-installer-tarball.html" title="2.1.1.1.�Getting the ADT Installer Tarball">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.1.1.�Using the ADT Installer">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="using-the-adt-installer"></a>2.1.1.�Using the ADT Installer</h3></div></div></div>
+<p>
+            To run the ADT Installer, you need to first get the ADT Installer tarball and then run the ADT
+            Installer Script.
+        </p>
+</div></body>
+</html>

42 lines not on this page · raw message

75 lines not on this page · raw message

index e211b6a..352cfd6 100644
@@ -8,6 +8,10 @@
           primary="true">
     </toc>
     <toc
+          file="adt-manual-toc.xml"
+          primary="false">
+    </toc>
+    <toc
           file="yocto-project-qs-toc.xml"
           primary="false">
     </toc>

index 9be9cf5..1287575 100644
@@ -3,4 +3,7 @@
    <topic label="The Yocto Project Quick Start">
       <link toc="yocto-project-qs-toc.xml"/>
    </topic>
+   <topic label="The·Yocto·Project·Application·Developer&apos;s·Guide">
+      <link toc="adt-manual-toc.xml"/>
+   </topic>
 </toc>

index 303a3a6..b0e3dac 100644
@@ -75,6 +75,29 @@
 			</a>
 		<br />
 			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
+		<br />
+		<br />
+		<strong>
+			The Yocto Project Development Manual:
+		</strong>
+		<br />
+		<br />
+			This manual describes how to use the Yocto Project to develop
+			embedded Linux images and user-space applications to run on
+			targeted devices.
+		<br />
+		<br />
+			<em>License:</em>
+			<a href="http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode">
+				http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode
+			</a>
+		<br />
+			<em>Source Code Repository:</em>
+			<a href="git://git.yoctoproject.org/yocto-docs">
+				git://git.yoctoproject.org/yocto-docs
+			</a>
+		<br />
+			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
 	</p>
 </body>
 </html>

index b1659fe..5f29d87 100644
@@ -6,9 +6,11 @@ bin.includes = plugin.xml,\
                yocto-project-qs-toc.xml,\
                about.html,\
                adt-manual-toc.xml,\
-               OSGI-INF/
-src.includes = toc.xml, \
+               OSGI-INF/,\
+               dev-manual-toc.xml
+src.includes = toc.xml,\
                html/,\
                yocto-project-qs-toc.xml,\
                about.html,\
-               adt-manual-toc.xml
+               adt-manual-toc.xml,\
+               dev-manual-toc.xml

176 lines not on this page · raw message

new file mode 100644
index 0000000..4a76677
@@ -0,0 +1,24 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.3.�Adding Kernel Recipes</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="dev-manual-kernel-appendix.html" title="Appendix�2.�Kernel Modification Example">
+<link rel="prev" href="recompiling-the-kernel-and-testing-the-new-configuration.html" title="2.2.4.�Recompiling the Kernel and Testing the New Configuration">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.�Adding Kernel Recipes">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="adding-kernel-recipes"></a>2.3.�Adding Kernel Recipes</h2></div></div></div>
+<p>
+            A future release of this manual will present an example that adds kernel recipes, which provide 
+            new functionality to the kernel.
+        </p>
+<p>
+            </p>
+<table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="180"><tr style="height: 270px"><td align="center"><img src="figures/wip.png" align="middle" width="180"></td></tr></table>
+<p>
+        </p>
+</div></body>
+</html>

67 lines not on this page · raw message

43 lines not on this page · raw message

new file mode 100644
index 0000000..1b5a232
@@ -0,0 +1,34 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>5.2.�Application Development Workflow</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="dev-manual-model.html" title="Chapter�5.�Common Development Models">
+<link rel="prev" href="kernel-modification-workflow.html" title="5.1.2.2.�Kernel Modification Workflow">
+<link rel="next" href="workflow-using-the-adt-and-eclipse.html" title="5.2.1.�Workflow Using the ADT and Eclipse&#8482;">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.�Application Development Workflow">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="application-development-workflow"></a>5.2.�Application Development Workflow</h2></div></div></div>
+<p>
+        Application development involves creating an application that you want 
+        to run on your target hardware, which is running a kernel image created using the 
+        OpenEmbedded build system.
+        The Yocto Project provides an Application Development Toolkit (ADT) and 
+        stand-alone cross-development toolchains that 
+        facilitate quick development and integration of your application into its run-time environment. 
+        Using the ADT and toolchains, you can compile and link your application. 
+        You can then deploy your application to the actual hardware or to the QEMU emulator for testing.
+        If you are familiar with the popular Eclipse IDE, you can use an Eclipse Yocto Plug-in to 
+        allow you to develop, deploy, and test your application all from within Eclipse.
+    </p>
+<p>
+        While we strongly suggest using the ADT to develop your application, this option might not 
+        be best for you.  
+        If this is the case, you can still use pieces of the Yocto Project for your development process. 
+        However, because the process can vary greatly, this manual does not provide detail on the process.
+    </p>
+</div></body>
+</html>

98 lines not on this page · raw message

new file mode 100644
index 0000000..0b1a051
@@ -0,0 +1,30 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.5.3.�BSP Recipe Change Summary</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="making-changes-to-your-bsp-app.html" title="1.5.�Making Changes to Your BSP">
+<link rel="prev" href="changing-recipes-kernel.html" title="1.5.2.3.�Changing��recipes-kernel">
+<link rel="next" href="preparing-for-the-build-app.html" title="1.6.�Preparing for the Build">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.5.3.�BSP Recipe Change Summary">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="bsp-recipe-change-summary"></a>1.5.3.�BSP Recipe Change Summary</h3></div></div></div>
+<p>
+            In summary, the edits to the layer&#8217;s recipe files result in removal of any files and 
+            statements that do not support your targeted hardware in addition to the inclusion 
+            of any new recipes you might need.  
+            In this example, it was simply a matter of ridding the new layer 
+            <code class="filename">meta-mymachine</code> of any code that supported the EMGD features
+            and making sure we were identifying the kernel that supports our example, which
+            is the <code class="filename">atom-pc-standard</code> kernel.  
+            We did not introduce any new recipes to the layer. 
+        </p>
+<p>
+            Finally, it is also important to update the layer&#8217;s <code class="filename">README</code>
+            file so that the information in it reflects your BSP.
+        </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..81d6ead
@@ -0,0 +1,31 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>5.2.2.8.3.�Building and Customizing the Image</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="customizing-an-image-using-a-bitbake-commander-project-and-hob.html" title="5.2.2.8.�Customizing an Image Using a BitBake Commander Project and Hob">
+<link rel="prev" href="editing-the-metadata-files.html" title="5.2.2.8.2.�Editing the Metadata Files">
+<link rel="next" href="workflow-using-stand-alone-cross-development-toolchains.html" title="5.2.3.�Workflow Using Stand-alone Cross-development Toolchains">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.2.8.3.�Building and Customizing the Image">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="buiding-and-customizing-the-image"></a>5.2.2.8.3.�Building and Customizing the Image</h5></div></div></div>
+<p>
+                    To build and customize the image in Eclipse, follow these steps:
+                    </p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>Select your Yocto Bitbake Commander project.</p></li>
+<li class="listitem"><p>Select <code class="filename">Project -&gt; Launch HOB</code>.</p></li>
+<li class="listitem"><p>Enter the build directory where you want to put your final images.</p></li>
+<li class="listitem"><p>Click <code class="filename">OK</code> to launch Hob.</p></li>
+<li class="listitem"><p>Use Hob to customize and build your own images. 
+                            For information on Hob, see the 
+                            <a class="ulink" href="http://www.yoctoproject.org/projects/hob" target="_self">Hob Project Page</a> on the 
+                            Yocto Project website.</p></li>
+</ol></div>
+<p>
+                </p>
+</div></body>
+</html>

102 lines not on this page · raw message

77 lines not on this page · raw message

51 lines not on this page · raw message

44 lines not on this page · raw message

65 lines not on this page · raw message

101 lines not on this page · raw message

new file mode 100644
index 0000000..b7e3fd4
@@ -0,0 +1,22 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>5.2.2.4.�Building the Project</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="adt-eclipse.html" title="5.2.2.�Working Within Eclipse">
+<link rel="prev" href="configuring-the-cross-toolchains.html" title="5.2.2.3.�Configuring the Cross-Toolchains">
+<link rel="next" href="starting-qemu-in-user-space-nfs-mode.html" title="5.2.2.5.�Starting QEMU in User Space NFS Mode">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.2.4.�Building the Project">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="building-the-project"></a>5.2.2.4.�Building the Project</h4></div></div></div>
+<p>
+                To build the project in Juno, right click on the project in the navigator pane and select
+                <code class="filename">Build Project</code>.
+                If you are not running Juno, select <code class="filename">Project -&gt; Build Project</code>.  
+                The console should update and you can note the cross-compiler you are using.
+            </p>
+</div></body>
+</html>

104 lines not on this page · raw message

new file mode 100644
index 0000000..bbac711
@@ -0,0 +1,31 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.5.2.1.�Changing��recipes-bsp</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="changing-the-recipes-in-your-bsp.html" title="1.5.2.�Changing the Recipes in Your BSP">
+<link rel="prev" href="changing-the-recipes-in-your-bsp.html" title="1.5.2.�Changing the Recipes in Your BSP">
+<link rel="next" href="changing-recipes-graphics.html" title="1.5.2.2.�Changing��recipes-graphics">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.5.2.1.�Changing��recipes-bsp">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="changing-recipes-bsp"></a>1.5.2.1.�Changing��<code class="filename">recipes-bsp</code>
+</h4></div></div></div>
+<p>
+                First, let's look at <code class="filename">recipes-bsp</code>.
+                For this example we are not adding any new BSP recipes.  
+                And, we only need to remove the formfactor we do not want and change the name of 
+                the remaining one that doesn't support EMGD.  
+                These commands take care of the <code class="filename">recipes-bsp</code> recipes:
+                </p>
+<pre class="literallayout">
+     $ rm -rf meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay
+     $ mv meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay-noemgd/ \
+     meta-mymachine/recipes-bsp/formfactor/formfactor/mymachine
+                </pre>
+<p>
+            </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..f4cf89a
@@ -0,0 +1,34 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.5.2.2.�Changing��recipes-graphics</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="changing-the-recipes-in-your-bsp.html" title="1.5.2.�Changing the Recipes in Your BSP">
+<link rel="prev" href="changing-recipes-bsp.html" title="1.5.2.1.�Changing��recipes-bsp">
+<link rel="next" href="changing-recipes-kernel.html" title="1.5.2.3.�Changing��recipes-kernel">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.5.2.2.�Changing��recipes-graphics">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="changing-recipes-graphics"></a>1.5.2.2.�Changing��<code class="filename">recipes-graphics</code>
+</h4></div></div></div>
+<p>
+                Now let's look at <code class="filename">recipes-graphics</code>.
+                For this example we want to remove anything that supports EMGD and 
+                be sure to rename remaining directories appropriately.  
+                The following commands clean up the <code class="filename">recipes-graphics</code> directory:
+                </p>
+<pre class="literallayout">
+     $ rm -rf meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay
+     $ mv meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay-noemgd \
+        meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/mymachine   
+                </pre>
+<p>
+            </p>
+<p>
+                At this point the <code class="filename">recipes-graphics</code> directory just has files that 
+                support Video Electronics Standards Association (VESA) graphics modes and not EMGD.  
+            </p>
+</div></body>
+</html>

175 lines not on this page · raw message

87 lines not on this page · raw message

108 lines not on this page · raw message

new file mode 100644
index 0000000..435485e
@@ -0,0 +1,21 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.2.�Changing the Kernel Configuration</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="dev-manual-kernel-appendix.html" title="Appendix�2.�Kernel Modification Example">
+<link rel="prev" href="building-and-booting-the-modified-qemu-kernel-image.html" title="2.1.8.�Building and Booting the Modified QEMU Kernel Image">
+<link rel="next" href="getting-set-up-to-run-this-example.html" title="2.2.1.�Getting Set Up to Run this Example">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.2.�Changing the Kernel Configuration">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="changing-the-kernel-configuration"></a>2.2.�Changing the Kernel Configuration</h2></div></div></div>
+<p>
+            This example changes the default behavior, which is "on", of the Symmetric 
+            Multi-processing Support (<code class="filename">CONFIG_SMP</code>) to "off".  
+            It is a simple example that demonstrates how to reconfigure the kernel.
+        </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..bd834ef
@@ -0,0 +1,29 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.5.2.�Changing the Recipes in Your BSP</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="making-changes-to-your-bsp-app.html" title="1.5.�Making Changes to Your BSP">
+<link rel="prev" href="changing-the-bsp-configuration.html" title="1.5.1.�Changing the BSP Configuration">
+<link rel="next" href="changing-recipes-bsp.html" title="1.5.2.1.�Changing��recipes-bsp">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.5.2.�Changing the Recipes in Your BSP">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="changing-the-recipes-in-your-bsp"></a>1.5.2.�Changing the Recipes in Your BSP</h3></div></div></div>
+<p>
+            Now we will take a look at the recipes in your new layer.  
+            The standard BSP structure has areas for BSP, graphics, core, and kernel recipes.  
+            When you create a BSP, you use these areas for appropriate recipes and append files.  
+            Recipes take the form of <code class="filename">.bb</code> files, while append files take
+            the form of <code class="filename">.bbappend</code> files.  
+            If you want to leverage the existing recipes the OpenEmbedded build system uses
+            but change those recipes, you can use <code class="filename">.bbappend</code> files.  
+            All new recipes and append files for your layer must go in the layer&#8217;s 
+            <code class="filename">recipes-bsp</code>, <code class="filename">recipes-kernel</code>, 
+            <code class="filename">recipes-core</code>, and 
+            <code class="filename">recipes-graphics</code> directories.    
+        </p>
+</div></body>
+</html>

88 lines not on this page · raw message

new file mode 100644
index 0000000..a7bb0ba
@@ -0,0 +1,31 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.2.�Choosing a Base BSP</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="dev-manual-bsp-appendix.html" title="Appendix�1.�BSP Development Example">
+<link rel="prev" href="getting-local-yocto-project-files-and-bsp-files.html" title="1.1.�Getting Local Source Files and BSP Files">
+<link rel="next" href="getting-your-base-bsp-app.html" title="1.3.�Getting Your Base BSP">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.2.�Choosing a Base BSP">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="choosing-a-base-bsp-app"></a>1.2.�Choosing a Base BSP</h2></div></div></div>
+<p>
+        For this example, the base BSP is the <span class="trademark">Intel</span>�
+        <span class="trademark">Atom</span>&#8482; Processor E660 with Intel Platform 
+        Controller Hub EG20T Development Kit, which is otherwise referred to as "Crown Bay."
+        The BSP layer is <code class="filename">meta-crownbay</code>.  
+        The base BSP is simply the BSP
+        we will be using as a starting point, so don't worry if you don't actually have Crown Bay
+        hardware.
+        The remainder of the example transforms the base BSP into a BSP that should be
+        able to boot on generic atom-pc (netbook) hardware.
+    </p>
+<p>
+        For information on how to choose a base BSP, see
+        "<a class="link" href="developing-a-board-support-package-bsp.html" title="5.1.1.�Developing a Board Support Package (BSP)">Developing a Board Support Package (BSP)</a>".
+    </p>
+</div></body>
+</html>

100 lines not on this page · raw message

54 lines not on this page · raw message

71 lines not on this page · raw message

55 lines not on this page · raw message

new file mode 100644
index 0000000..8bb0d03
@@ -0,0 +1,33 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>5.2.2.1.5.�Configuring the Eclipse Yocto Plug-in</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="setting-up-the-eclipse-ide.html" title="5.2.2.1.�Setting Up the Eclipse IDE">
+<link rel="prev" href="yocto-project-source.html" title="5.2.2.1.4.3.�Importing the Plug-in Project into the Eclipse Environment">
+<link rel="next" href="configuring-the-cross-compiler-options.html" title="5.2.2.1.5.1.�Configuring the Cross-Compiler Options">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.2.1.5.�Configuring the Eclipse Yocto Plug-in">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="configuring-the-eclipse-yocto-plug-in"></a>5.2.2.1.5.�Configuring the Eclipse Yocto Plug-in</h5></div></div></div>
+<p>
+                    Configuring the Eclipse Yocto Plug-in involves setting the Cross 
+                    Compiler options and the Target options.  
+                    The configurations you choose become the default settings for all projects.  
+                    You do have opportunities to change them later when 
+                    you configure the project (see the following section).  
+                </p>
+<p>
+                    To start, you need to do the following from within the Eclipse IDE:
+                    </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>Choose <code class="filename">Windows -&gt; Preferences</code> to display 
+                            the <code class="filename">Preferences</code> Dialog</p></li>
+<li class="listitem"><p>Click <code class="filename">Yocto Project ADT</code></p></li>
+</ul></div>
+<p>
+                </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..74abea4
@@ -0,0 +1,30 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>4.6.�Configuring the Kernel</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="extendpoky.html" title="Chapter�4.�Common Tasks">
+<link rel="prev" href="additional-implementation-details.html" title="4.5.3.�Additional Implementation Details">
+<link rel="next" href="using-menuconfig.html" title="4.6.1.�Using��menuconfig">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.6.�Configuring the Kernel">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="configuring-the-kernel"></a>4.6.�Configuring the Kernel</h2></div></div></div>
+<p>
+            Configuring the Yocto Project kernel consists of making sure the <code class="filename">.config</code>
+            file has all the right information in it for the image you are building.
+            You can use the <code class="filename">menuconfig</code> tool and configuration fragments to 
+            make sure your <code class="filename">.config</code> file is just how you need it. 
+            This section describes how to use <code class="filename">menuconfig</code>, create and use 
+            configuration fragments, and how to interactively tweak your <code class="filename">.config</code>
+            file to create the leanest kernel configuration file possible.
+        </p>
+<p>
+            For concepts on kernel configuration, see the
+            "<a class="link" href="../kernel-manual/kernel-configuration.html" target="_self">Kernel Configuration</a>"
+            section in the Yocto Project Kernel Architecture and Use Manual.
+        </p>
+</div></body>
+</html>

59 lines not on this page · raw message

74 lines not on this page · raw message

50 lines not on this page · raw message

new file mode 100644
index 0000000..7e24e00
@@ -0,0 +1,39 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>5.2.2.8.1.�Creating the Yocto BitBake Commander Project</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="customizing-an-image-using-a-bitbake-commander-project-and-hob.html" title="5.2.2.8.�Customizing an Image Using a BitBake Commander Project and Hob">
+<link rel="prev" href="customizing-an-image-using-a-bitbake-commander-project-and-hob.html" title="5.2.2.8.�Customizing an Image Using a BitBake Commander Project and Hob">
+<link rel="next" href="editing-the-metadata-files.html" title="5.2.2.8.2.�Editing the Metadata Files">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.2.8.1.�Creating the Yocto BitBake Commander Project">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="creating-the-yocto-bitbake-commander-project"></a>5.2.2.8.1.�Creating the Yocto BitBake Commander Project</h5></div></div></div>
+<p>
+                    To create a Yocto BitBake Commander project, follow these steps:
+                    </p>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p>Select <code class="filename">Window -&gt; Open Perspective -&gt; Other</code>
+                            and then choose <code class="filename">Bitbake Commander</code>.</p></li>
+<li class="listitem"><p>Click <code class="filename">OK</code> to change the Eclipse perspective into the 
+                            Bitbake Commander perspective.</p></li>
+<li class="listitem"><p>Select <code class="filename">File -&gt; New -&gt; Project</code> to create a new Yocto 
+                            Bitbake Commander project.</p></li>
+<li class="listitem"><p>Choose <code class="filename">Yocto Project Bitbake Commander -&gt; New Yocto Project</code>
+                            and click <code class="filename">Next</code>.</p></li>
+<li class="listitem"><p>Enter the Project Name and choose the Project Location. 
+                            The Yocto project's metadata files will be put under the directory 
+                            <code class="filename">&lt;project_location&gt;/&lt;project_name&gt;</code>. 
+                            If that directory does not exist, you need to check 
+                            the "Clone from Yocto Git Repository" box, which would execute a 
+                            <code class="filename">git clone</code> command to get the project's metadata files.
+                            </p></li>
+<li class="listitem"><p>Select <code class="filename">Finish</code> to create the project.</p></li>
+</ol></div>
+<p>
+                </p>
+</div></body>
+</html>

159 lines not on this page · raw message

new file mode 100644
index 0000000..3178f52
@@ -0,0 +1,22 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>5.2.2.8.�Customizing an Image Using a BitBake Commander Project and Hob</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="adt-eclipse.html" title="5.2.2.�Working Within Eclipse">
+<link rel="prev" href="running-user-space-tools.html" title="5.2.2.7.�Running User-Space Tools">
+<link rel="next" href="creating-the-yocto-bitbake-commander-project.html" title="5.2.2.8.1.�Creating the Yocto BitBake Commander Project">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.2.8.�Customizing an Image Using a BitBake Commander Project and Hob">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="customizing-an-image-using-a-bitbake-commander-project-and-hob"></a>5.2.2.8.�Customizing an Image Using a BitBake Commander Project and Hob</h4></div></div></div>
+<p>
+                Within Eclipse, you can create a Yocto BitBake Commander project, 
+                edit the metadata, and then use the 
+                <a class="ulink" href="http://www.yoctoproject.org/projects/hob" target="_self">Hob</a> to build a customized 
+                image all within one IDE.
+            </p>
+</div></body>
+</html>

50 lines not on this page · raw message

50 lines not on this page · raw message

new file mode 100644
index 0000000..1fa3c36
@@ -0,0 +1,25 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter�1.�The Yocto Project Development Manual</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="index.html" title="The Yocto Project Development Manual">
+<link rel="prev" href="index.html" title="The Yocto Project Development Manual">
+<link rel="next" href="intro.html" title="1.1.�Introduction">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter�1.�The Yocto Project Development Manual">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="dev-manual-intro"></a>Chapter�1.�The Yocto Project Development Manual</h2></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="intro.html">1.1. Introduction</a></span></dt>
+<dt><span class="section"><a href="what-this-manual-provides.html">1.2. What this Manual Provides</a></span></dt>
+<dt><span class="section"><a href="what-this-manual-does-not-provide.html">1.3. What this Manual Does Not Provide</a></span></dt>
+<dt><span class="section"><a href="other-information.html">1.4. Other Information</a></span></dt>
+</dl>
+</div>
+</div></body>
+</html>

47 lines not on this page · raw message

78 lines not on this page · raw message

47 lines not on this page · raw message

new file mode 100644
index 0000000..501de54
@@ -0,0 +1,35 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter�2.�Getting Started with the Yocto Project</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Development Manual">
+<link rel="up" href="index.html" title="The Yocto Project Development Manual">
+<link rel="prev" href="other-information.html" title="1.4.�Other Information">
+<link rel="next" href="introducing-the-yocto-project.html" title="2.1.�Introducing the Yocto Project">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter�2.�Getting Started with the Yocto Project">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="dev-manual-start"></a>Chapter�2.�Getting Started with the Yocto Project</h2></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="introducing-the-yocto-project.html">2.1. Introducing the Yocto Project</a></span></dt>
+<dt><span class="section"><a href="getting-setup.html">2.2. Getting Set Up</a></span></dt>
+<dt><span class="section"><a href="building-images.html">2.3. Building Images</a></span></dt>
+<dt><span class="section"><a href="using-pre-built-binaries-and-qemu.html">2.4. Using Pre-Built Binaries and QEMU</a></span></dt>
+</dl>
+</div>
+<p>
+    This chapter introduces the Yocto Project and gives you an idea of what you need to get started.  
+    You can find enough information to set up your development host and build or use images for 
+    hardware supported by the Yocto Project by reading the 
+    <a class="link" href="../yocto-project-qs/index.html" target="_self">Yocto Project Quick Start</a>.
+</p>
+<p>
+    The remainder of this chapter summarizes what is in the Yocto Project Quick Start and provides 
+    some higher-level concepts you might want to consider.
+</p>
+</div></body>
+</html>

173 lines not on this page · raw message

33 lines not on this page · raw message

44 lines not on this page · raw message

59 lines not on this page · raw message

new file mode 100644
index 0000000..450f051

Lines of this file are not shown. View the raw message.

89 lines not on this page · raw message

new file mode 100644
index 0000000000000000000000000000000000000000..4927b93d67f7ba9d6a189b62d033ba14a7d25573
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..b20ee19223becb8ecc44fd929adf759a63087f11
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..d3cac4a7e58ad6219d790d1c3da6fae1100c0c5e
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..4fdf42f89c81bc5a30c2e179135c0a52882571fa
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..c907997db2ba697b93ed098f3f60d3eedcce8369
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..f200af633815f2efdf0aa7579e9e64ac9c3f46fb
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..79fc60698b11a4bcb5165980419416ddecb5e2cc
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..116c0b9bd4d10dfe086ef4583a54bcce03996cee
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..5fee847c66c4cc22fe8a48a585d57f28e7facbd9
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..5f2ea0578966cac0c8c004b3c1a156ff1e4af071
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..65c5f29a4331ced50ce27c31c2a00def598439fe
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..88116374a195c7d5ffa3684a57bc71caa1f2a2d0
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..a10b2e2b200a064c087cc99f78c299c81836f733
GIT binary patch

100 lines not on this page · raw message

94 lines not on this page · raw message

106 lines not on this page · raw message

119 lines not on this page · raw message

251 lines not on this page · raw message

78 lines not on this page · raw message

new file mode 100644
index 0000000..b172e2a

Lines of this file are not shown. View the raw message.

146 lines not on this page · raw message

52 lines not on this page · raw message

68 lines not on this page · raw message

246 lines not on this page · raw message

75 lines not on this page · raw message

new file mode 100644
index 0000000..d8f9b5f

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..ae6b311

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..4966a82

Lines of this file are not shown. View the raw message.

150 lines not on this page · raw message

186 lines not on this page · raw message

73 lines not on this page · raw message

new file mode 100644
index 0000000..a6ae5be

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..db38c79

Lines of this file are not shown. View the raw message.

103 lines not on this page · raw message

new file mode 100644
index 0000000..8a06389

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..f9d37c6

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..0c63871

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..57072e0

Lines of this file are not shown. View the raw message.

46 lines not on this page · raw message

124 lines not on this page · raw message

82 lines not on this page · raw message

new file mode 100644
index 0000000..d7f6b27

Lines of this file are not shown. View the raw message.

44 lines not on this page · raw message

76 lines not on this page · raw message

51 lines not on this page · raw message

new file mode 100644
index 0000000..ff780d5

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..80360fe

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..c226352

Lines of this file are not shown. View the raw message.

73 lines not on this page · raw message

53 lines not on this page · raw message

51 lines not on this page · raw message

53 lines not on this page · raw message

new file mode 100644
index 0000000..f26f884

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..cc1d71f

Lines of this file are not shown. View the raw message.

101 lines not on this page · raw message

new file mode 100644
index 0000000..696c599

Lines of this file are not shown. View the raw message.

76 lines not on this page · raw message

49 lines not on this page · raw message

81 lines not on this page · raw message

44 lines not on this page · raw message

46 lines not on this page · raw message

56 lines not on this page · raw message

61 lines not on this page · raw message

148 lines not on this page · raw message

113 lines not on this page · raw message

43 lines not on this page · raw message

new file mode 100644
index 0000000..8817ca7

Lines of this file are not shown. View the raw message.

49 lines not on this page · raw message

new file mode 100644
index 0000000..07718d8

Lines of this file are not shown. View the raw message.

63 lines not on this page · raw message

new file mode 100644
index 0000000..56f5ac4

Lines of this file are not shown. View the raw message.

113 lines not on this page · raw message

new file mode 100644
index 0000000..28724e6

Lines of this file are not shown. View the raw message.

62 lines not on this page · raw message

new file mode 100644
index 0000000..9bfe950

Lines of this file are not shown. View the raw message.

120 lines not on this page · raw message

172 lines not on this page · raw message

121 lines not on this page · raw message

118 lines not on this page · raw message

47 lines not on this page · raw message

57 lines not on this page · raw message

100 lines not on this page · raw message

71 lines not on this page · raw message

72 lines not on this page · raw message

new file mode 100644
index 0000000..bf93b93

Lines of this file are not shown. View the raw message.

56 lines not on this page · raw message

48 lines not on this page · raw message

101 lines not on this page · raw message

67 lines not on this page · raw message

59 lines not on this page · raw message

new file mode 100644
index 0000000..a32a692

Lines of this file are not shown. View the raw message.

48 lines not on this page · raw message

72 lines not on this page · raw message

50 lines not on this page · raw message

68 lines not on this page · raw message

new file mode 100644
index 0000000..d50996b

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..4693482

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..9c8200a

Lines of this file are not shown. View the raw message.

64 lines not on this page · raw message

111 lines not on this page · raw message

138 lines not on this page · raw message

new file mode 100644
index 0000000..1167095

Lines of this file are not shown. View the raw message.

91 lines not on this page · raw message

52 lines not on this page · raw message

222 lines not on this page · raw message

99 lines not on this page · raw message

index 352cfd6..5d678c1 100644

Lines of this file are not shown. View the raw message.

index 1287575..4e642ec 100644

Lines of this file are not shown. View the raw message.

index b0e3dac..a41e016 100644
@@ -98,6 +98,28 @@
 			</a>
 		<br />
 			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
+		<br />
+		<br />
+		<strong>
+			The Yocto Project Reference Manual:
+		</strong>
+		<br />
+		<br />
+			This manual is the complete reference guide to the Poky component.
+			It also contains a chapter on Board Support Package (BSP) development.
+		<br />
+		<br />
+			<em>License:</em>
+			<a href="http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode">
+				http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode
+			</a>
+		<br />
+			<em>Source Code Repository:</em>
+			<a href="git://git.yoctoproject.org/yocto-docs">
+				git://git.yoctoproject.org/yocto-docs
+			</a>
+		<br />
+			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
 	</p>
 </body>
 </html>

index 5f29d87..3350a45 100644
@@ -7,10 +7,12 @@ bin.includes = plugin.xml,\
                about.html,\
                adt-manual-toc.xml,\
                OSGI-INF/,\
-               dev-manual-toc.xml
+               dev-manual-toc.xml,\
+               poky-ref-manual-toc.xml
 src.includes = toc.xml,\
                html/,\
                yocto-project-qs-toc.xml,\
                about.html,\
                adt-manual-toc.xml,\
-               dev-manual-toc.xml
+               dev-manual-toc.xml,\
+               poky-ref-manual-toc.xml

61 lines not on this page · raw message

new file mode 100644
index 0000000..237b8dd
@@ -0,0 +1,23 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.1.2.�Building an Image Using GPL Components</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="usingpoky-build.html" title="2.1.�Running a Build">
+<link rel="prev" href="build-overview.html" title="2.1.1.�Build Overview">
+<link rel="next" href="usingpoky-install.html" title="2.2.�Installing and Using the Result">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.1.2.�Building an Image Using GPL Components">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="building-an-image-using-gpl-components"></a>2.1.2.�Building an Image Using GPL Components</h3></div></div></div>
+<p>
+            When building an image using GPL components, you need to maintain your original 
+            settings and not switch back and forth applying different versions of the GNU
+            Public License.  
+            If you rebuild using different versions of GPL, dependency errors might occur
+            due to some components not being rebuilt.
+        </p>
+</div></body>
+</html>

164 lines not on this page · raw message

43 lines not on this page · raw message

85 lines not on this page · raw message

821 lines not on this page · raw message

new file mode 100644
index 0000000000000000000000000000000000000000..2893d84620d74e5c3318c03fbb44bcf60853ae44
GIT binary patch

new file mode 100644
index 0000000..cd09ff8
@@ -0,0 +1,33 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.3.2.�Future Development and Limitations</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="x32.html" title="3.3.�x32">
+<link rel="prev" href="support.html" title="3.3.1.�Support">
+<link rel="next" href="using-x32-right-now.html" title="3.3.3.�Using x32 Right Now">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.3.2.�Future Development and Limitations">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="future-development-and-limitations"></a>3.3.2.�Future Development and Limitations</h3></div></div></div>
+<p>
+            As of this Yocto Project release, the x32 psABI kernel and library interfaces 
+            specifications are not finalized.
+        </p>
+<p>
+            Future Plans for the x32 psABI in the Yocto Project include the following:
+            </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>Enhance and fix the few remaining recipes so they  
+                    work with and support x32 toolchains.</p></li>
+<li class="listitem"><p>Enhance RPM Package Manager (RPM) support for x32 binaries.</p></li>
+<li class="listitem"><p>Support larger images.</p></li>
+<li class="listitem"><p>Integrate x32 recipes, toolchain, and kernel changes from 
+                    <code class="filename">experimental/meta-x32</code> into OE-core.</p></li>
+</ul></div>
+<p>
+        </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..7cc5c24
@@ -0,0 +1,25 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>4.1.3.�documentation</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="structure-core.html" title="4.1.�Top level core components">
+<link rel="prev" href="structure-core-build.html" title="4.1.2.�build/">
+<link rel="next" href="structure-core-meta.html" title="4.1.4.�meta/">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.3.�documentation">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="handbook"></a>4.1.3.�<code class="filename">documentation</code>
+</h3></div></div></div>
+<p>
+            This directory holds the source for the Yocto Project documentation
+            as well as templates and tools that allow you to generate PDF and HTML
+            versions of the manuals.  
+            Each manual is contained in a sub-folder.  
+            For example, the files for this manual reside in 
+            <code class="filename">poky-ref-manual</code>.
+        </p>
+</div></body>
+</html>

301 lines not on this page · raw message

new file mode 100644
index 0000000..625693b
@@ -0,0 +1,26 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.5.�Development Checkouts</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="intro.html" title="Chapter�1.�Introduction">
+<link rel="prev" href="intro-getit.html" title="1.4.�Obtaining the Yocto Project">
+<link rel="next" href="usingpoky.html" title="Chapter�2.�Using the Yocto Project">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.5.�Development Checkouts">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="intro-getit-dev"></a>1.5.�Development Checkouts</h2></div></div></div>
+<p>
+        Development using the Yocto Project requires a local 
+        <a class="link" href="../dev-manual/source-directory.html" target="_self">source directory</a>. 
+        You can set up the source directory by downloading a Yocto Project release tarball and unpacking it,  
+        or by cloning a copy of the upstream
+        <a class="link" href="../dev-manual/poky.html" target="_self">Poky</a> Git repository.
+        For information on both these methods, see the
+        "<a class="link" href="../dev-manual/getting-setup.html" target="_self">Getting Setup</a>" 
+        section in the Yocto Project Development Manual.
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..eea7414
@@ -0,0 +1,35 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.4.�Obtaining the Yocto Project</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="intro.html" title="Chapter�1.�Introduction">
+<link rel="prev" href="intro-requirements.html" title="1.3.�System Requirements">
+<link rel="next" href="intro-getit-dev.html" title="1.5.�Development Checkouts">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.4.�Obtaining the Yocto Project">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="intro-getit"></a>1.4.�Obtaining the Yocto Project</h2></div></div></div>
+<p>
+        The Yocto Project development team makes the Yocto Project available through a number 
+        of methods:
+        </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p><span class="emphasis"><em>Releases:</em></span> Stable, tested releases are available through 
+                <a class="ulink" href="http://downloads.yoctoproject.org/releases/yocto/" target="_self">http://downloads.yoctoproject.org/releases/yocto/</a>.</p></li>
+<li class="listitem"><p><span class="emphasis"><em>Nightly Builds:</em></span> These releases are available at
+                <a class="ulink" href="http://autobuilder.yoctoproject.org/nightly" target="_self">http://autobuilder.yoctoproject.org/nightly</a>.  
+                These builds include Yocto Project releases, meta-toolchain tarball installation scripts, and 
+                experimental builds.</p></li>
+<li class="listitem"><p><span class="emphasis"><em>Yocto Project Website:</em></span> You can find releases
+                of the Yocto Project and supported BSPs at the
+                <a class="ulink" href="http://www.yoctoproject.org" target="_self">Yocto Project website</a>.
+                Along with these downloads, you can find lots of other information at this site.  
+                </p></li>
+</ul></div>
+<p>
+    </p>
+</div></body>
+</html>

73 lines not on this page · raw message

new file mode 100644
index 0000000..220c2ff
@@ -0,0 +1,21 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.3.�System Requirements</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="intro.html" title="Chapter�1.�Introduction">
+<link rel="prev" href="intro-manualoverview.html" title="1.2.�Documentation Overview">
+<link rel="next" href="intro-getit.html" title="1.4.�Obtaining the Yocto Project">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.3.�System Requirements">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="intro-requirements"></a>1.3.�System Requirements</h2></div></div></div>
+<p>
+        For Yocto Project system requirements, see the
+        <a class="link" href="../yocto-project-qs/yp-resources.html" target="_self">
+        What You Need and How You Get It</a> section in the Yocto Project Quick Start.
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..378b87f
@@ -0,0 +1,30 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.1.�Introduction</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="intro.html" title="Chapter�1.�Introduction">
+<link rel="prev" href="intro.html" title="Chapter�1.�Introduction">
+<link rel="next" href="intro-manualoverview.html" title="1.2.�Documentation Overview">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.1.�Introduction">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="intro-welcome"></a>1.1.�Introduction</h2></div></div></div>
+<p>
+        This manual provides reference information for the current release of the Yocto Project.
+        The Yocto Project is an open-source collaboration project focused on embedded Linux
+        developers.
+        Amongst other things, the Yocto Project uses the OpenEmbedded build system, which 
+        is based on the Poky project, to construct complete Linux images.
+        You can find complete introductory and getting started information on the Yocto Project
+        by reading the 
+        <a class="link" href="../yocto-project-qs/index.html" target="_self">Yocto Project Quick Start</a>.
+        For task-based information using the Yocto Project, see the
+        <a class="link" href="../dev-manual/index.html" target="_self">Yocto Project Development Manual</a>.
+        You can also find lots of information on the Yocto Project on the 
+        <a class="ulink" href="http://www.yoctoproject.org" target="_self">Yocto Project website</a>.
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..219fbc3
@@ -0,0 +1,26 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter�1.�Introduction</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="prev" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="next" href="intro-welcome.html" title="1.1.�Introduction">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter�1.�Introduction">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="intro"></a>Chapter�1.�Introduction</h2></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="intro-welcome.html">1.1. Introduction</a></span></dt>
+<dt><span class="section"><a href="intro-manualoverview.html">1.2. Documentation Overview</a></span></dt>
+<dt><span class="section"><a href="intro-requirements.html">1.3. System Requirements</a></span></dt>
+<dt><span class="section"><a href="intro-getit.html">1.4. Obtaining the Yocto Project</a></span></dt>
+<dt><span class="section"><a href="intro-getit-dev.html">1.5. Development Checkouts</a></span></dt>
+</dl>
+</div>
+</div></body>
+</html>

53 lines not on this page · raw message

91 lines not on this page · raw message

new file mode 100644
index 0000000..e1bcebe
@@ -0,0 +1,22 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.4.�Licenses</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="technical-details.html" title="Chapter�3.�Technical Details">
+<link rel="prev" href="using-x32-right-now.html" title="3.3.3.�Using x32 Right Now">
+<link rel="next" href="usingpoky-configuring-LIC_FILES_CHKSUM.html" title="3.4.1.�Tracking License Changes">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.�Licenses">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="licenses"></a>3.4.�Licenses</h2></div></div></div>
+<p>
+        This section describes the mechanism by which the OpenEmbedded build system 
+        tracks changes to licensing text.
+        The section also describes how to enable commercially licensed recipes, 
+        which by default are disabled.
+    </p>
+</div></body>
+</html>

47 lines not on this page · raw message

45 lines not on this page · raw message

60 lines not on this page · raw message

new file mode 100644
index 0000000..89a6979
@@ -0,0 +1,31 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.2.1.�Overall Architecture</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="shared-state-cache.html" title="3.2.�Shared State Cache">
+<link rel="prev" href="shared-state-cache.html" title="3.2.�Shared State Cache">
+<link rel="next" href="checksums.html" title="3.2.2.�Checksums (Signatures)">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2.1.�Overall Architecture">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="overall-architecture"></a>3.2.1.�Overall Architecture</h3></div></div></div>
+<p>
+            When determining what parts of the system need to be built, BitBake 
+            uses a per-task basis and does not use a per-recipe basis.
+            You might wonder why using a per-task basis is preferred over a per-recipe basis.
+            To help explain, consider having the IPK packaging backend enabled and then switching to DEB. 
+            In this case, <code class="filename">do_install</code> and <code class="filename">do_package</code>
+            output are still valid.
+            However, with a per-recipe approach, the build would not include the 
+            <code class="filename">.deb</code> files.        
+            Consequently, you would have to invalidate the whole build and rerun it. 
+            Rerunning everything is not the best situation.
+            Also in this case, the core must be "taught" much about specific tasks. 
+            This methodology does not scale well and does not allow users to easily add new tasks 
+            in layers or as external recipes without touching the packaged-staging core.
+        </p>
+</div></body>
+</html>

41 lines not on this page · raw message

79 lines not on this page · raw message

new file mode 100644
index 0000000..c3d826f
@@ -0,0 +1,34 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>5.3.�Dependencies</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="ref-bitbake.html" title="Chapter�5.�BitBake">
+<link rel="prev" href="ref-bitbake-providers.html" title="5.2.�Preferences and Providers">
+<link rel="next" href="ref-bitbake-tasklist.html" title="5.4.�The Task List">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.�Dependencies">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="ref-bitbake-dependencies"></a>5.3.�Dependencies</h2></div></div></div>
+<p>
+            Each target BitBake builds consists of multiple tasks such as 
+            <code class="filename">fetch</code>, <code class="filename">unpack</code>, 
+            <code class="filename">patch</code>, <code class="filename">configure</code>, 
+            and <code class="filename">compile</code>. 
+            For best performance on multi-core systems, BitBake considers each task as an independent 
+            entity with its own set of dependencies. 
+        </p>
+<p>
+            Dependencies are defined through several variables.
+            You can find information about variables BitBake uses in the BitBake documentation,
+            which is found in the <code class="filename">bitbake/doc/manual</code> directory within the
+            <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>. 
+            At a basic level, it is sufficient to know that BitBake uses the 
+            <code class="filename"><a class="link" href="ref-variables-glos.html#var-DEPENDS" title="DEPENDS">DEPENDS</a></code> and 
+            <code class="filename"><a class="link" href="ref-variables-glos.html#var-RDEPENDS" title="RDEPENDS">RDEPENDS</a></code> variables when 
+            calculating dependencies. 
+        </p>
+</div></body>
+</html>

43 lines not on this page · raw message

93 lines not on this page · raw message

63 lines not on this page · raw message

86 lines not on this page · raw message

54 lines not on this page · raw message

48 lines not on this page · raw message

52 lines not on this page · raw message

new file mode 100644
index 0000000..f553679
@@ -0,0 +1,28 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>6.1.�The base class - base.bbclass</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="ref-classes.html" title="Chapter�6.�Classes">
+<link rel="prev" href="ref-classes.html" title="Chapter�6.�Classes">
+<link rel="next" href="ref-classes-autotools.html" title="6.2.�Autotooled Packages - autotools.bbclass">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.1.�The base class - base.bbclass">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="ref-classes-base"></a>6.1.�The base class - <code class="filename">base.bbclass</code>
+</h2></div></div></div>
+<p>
+        The base class is special in that every <code class="filename">.bb</code> 
+        file inherits it automatically. 
+        This class contains definitions for standard basic 
+        tasks such as fetching, unpacking, configuring (empty by default), compiling 
+        (runs any <code class="filename">Makefile</code> present), installing (empty by default) and packaging 
+        (empty by default). 
+        These classes are often overridden or extended by other classes 
+        such as <code class="filename">autotools.bbclass</code> or <code class="filename">package.bbclass</code>. 
+        The class also contains some commonly used functions such as <code class="filename">oe_runmake</code>.
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..ffb7ca6
@@ -0,0 +1,30 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>6.5.�Binary config scripts - binconfig.bbclass</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="ref-classes.html" title="Chapter�6.�Classes">
+<link rel="prev" href="ref-classes-update-rc.d.html" title="6.4.�Initscripts - update-rc.d.bbclass">
+<link rel="next" href="ref-classes-debian.html" title="6.6.�Debian renaming - debian.bbclass">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.5.�Binary config scripts - binconfig.bbclass">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="ref-classes-binconfig"></a>6.5.�Binary config scripts - <code class="filename">binconfig.bbclass</code>
+</h2></div></div></div>
+<p>
+        Before <code class="filename">pkg-config</code> had become widespread, libraries shipped shell
+        scripts to give information about the libraries and include paths needed 
+        to build software (usually named <code class="filename">LIBNAME-config</code>).
+        This class assists any recipe using such scripts.
+    </p>
+<p>
+        During staging, BitBake installs such scripts into the
+        <code class="filename">sysroots/</code> directory. 
+        BitBake also changes all paths to point into the <code class="filename">sysroots/</code>
+        directory so all builds that use the script will use the correct 
+        directories for the cross compiling layout.
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..14bbf26
@@ -0,0 +1,22 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>6.6.�Debian renaming - debian.bbclass</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="ref-classes.html" title="Chapter�6.�Classes">
+<link rel="prev" href="ref-classes-binconfig.html" title="6.5.�Binary config scripts - binconfig.bbclass">
+<link rel="next" href="ref-classes-pkgconfig.html" title="6.7.�Pkg-config - pkgconfig.bbclass">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.6.�Debian renaming - debian.bbclass">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="ref-classes-debian"></a>6.6.�Debian renaming - <code class="filename">debian.bbclass</code>
+</h2></div></div></div>
+<p>
+        This class renames packages so that they follow the Debian naming
+        policy (i.e. <code class="filename">eglibc</code> becomes <code class="filename">libc6</code>
+        and <code class="filename">eglibc-devel</code> becomes <code class="filename">libc6-dev</code>.
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..3d27969
@@ -0,0 +1,24 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>6.11.�Developer Shell - devshell.bbclass</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="ref-classes.html" title="Chapter�6.�Classes">
+<link rel="prev" href="ref-classes-distutils.html" title="6.10.�Python extensions - distutils.bbclass">
+<link rel="next" href="ref-classes-packagegroup.html" title="6.12.�Package Groups - packagegroup.bbclass">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.11.�Developer Shell - devshell.bbclass">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="ref-classes-devshell"></a>6.11.�Developer Shell - <code class="filename">devshell.bbclass</code>
+</h2></div></div></div>
+<p>
+        This class adds the <code class="filename">devshell</code> task. 
+        Distribution policy dictates whether to include this class.
+        See the 
+        "<a class="link" href="../dev-manual/platdev-appdev-devshell.html" target="_self">Using a Development Shell</a>" section 
+        in the Yocto Project Development Manual for more information about using <code class="filename">devshell</code>.
+    </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..960da56
@@ -0,0 +1,31 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>6.10.�Python extensions - distutils.bbclass</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="ref-classes.html" title="Chapter�6.�Classes">
+<link rel="prev" href="ref-classes-perl.html" title="6.9.�Perl modules - cpan.bbclass">
+<link rel="next" href="ref-classes-devshell.html" title="6.11.�Developer Shell - devshell.bbclass">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.10.�Python extensions - distutils.bbclass">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="ref-classes-distutils"></a>6.10.�Python extensions - <code class="filename">distutils.bbclass</code>
+</h2></div></div></div>
+<p>
+        Recipes for Python extensions are simple.
+        These recipes usually only need to point to the source's archive and then inherit
+        the proper <code class="filename">.bbclass</code> file.
+        Building is split into two methods dependling on which method the module authors used.
+    </p>
+<p>
+        Extensions that use an Autotools-based build system require Autotools and 
+        <code class="filename">distutils</code>-based <code class="filename">.bbclasse</code> files in their recipes.
+    </p>
+<p>
+        Extensions that use <code class="filename">distutils</code>-based build systems require 
+        <code class="filename">distutils.bbclass</code> in their recipes.
+    </p>
+</div></body>
+</html>

72 lines not on this page · raw message

new file mode 100644
index 0000000..cc86a97
@@ -0,0 +1,31 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>6.15.�Creating images - image.bbclass and rootfs*.bbclass</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
+<link rel="up" href="ref-classes.html" title="Chapter�6.�Classes">
+<link rel="prev" href="ref-classes-kernel.html" title="6.14.�Building kernels - kernel.bbclass">
+<link rel="next" href="ref-classes-sanity.html" title="6.16.�Host System sanity checks - sanity.bbclass">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.15.�Creating images - image.bbclass and rootfs*.bbclass">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="ref-classes-image"></a>6.15.�Creating images - <code class="filename">image.bbclass</code> and <code class="filename">rootfs*.bbclass</code>
+</h2></div></div></div>
+<p>
+        These classes add support for creating images in several formats. 
+        First, the root filesystem is created from packages using
+        one of the <code class="filename">rootfs_*.bbclass</code> 
+        files (depending on the package format used) and then the image is created.
+    </p>
+<p>
+        The <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_FSTYPES" title="IMAGE_FSTYPES">IMAGE_FSTYPES</a></code>
+        variable controls the types of images to generate.
+    </p>
+<p>        
+        The <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_INSTALL" title="IMAGE_INSTALL">IMAGE_INSTALL</a></code>
+        variable controls the list of packages to install into the image.
+    </p>
+</div></body>
+</html>

11 lines not on this page · raw message

new file mode 100644
index 0000000..cefb7ef

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..22dc182

Lines of this file are not shown. View the raw message.

73 lines not on this page · raw message

new file mode 100644
index 0000000..eb57191

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..699595b

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..3c43569

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..8604b0c

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..6c7877f

Lines of this file are not shown. View the raw message.

43 lines not on this page · raw message

48 lines not on this page · raw message

new file mode 100644
index 0000000..a2c03ee

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..391a362

Lines of this file are not shown. View the raw message.

61 lines not on this page · raw message

59 lines not on this page · raw message

70 lines not on this page · raw message

54 lines not on this page · raw message

41 lines not on this page · raw message

137 lines not on this page · raw message

90 lines not on this page · raw message

1,903 lines not on this page · raw message

new file mode 100644
index 0000000..8c27a25

Lines of this file are not shown. View the raw message.

42 lines not on this page · raw message

41 lines not on this page · raw message

new file mode 100644
index 0000000..6ff80f6

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..0463527

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..be1d961

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..fb04117

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..9979745

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..6594707

Lines of this file are not shown. View the raw message.

41 lines not on this page · raw message

new file mode 100644
index 0000000..74175a0

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..eb35ff5

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..0635563

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..ed0afe8

Lines of this file are not shown. View the raw message.

42 lines not on this page · raw message

new file mode 100644
index 0000000..c2eaed3

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..b0db948

Lines of this file are not shown. View the raw message.

60 lines not on this page · raw message

121 lines not on this page · raw message

new file mode 100644
index 0000000..c121353

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..5e9c9fa

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..1190491

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..5fc9be7

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..d48625f

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..342ec64

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..2cd3dcc

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..23cb913

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..22f28e4

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..8ea589d

Lines of this file are not shown. View the raw message.

44 lines not on this page · raw message

new file mode 100644
index 0000000..d9eb66d

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..cadff9a

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..c1d6a8a

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..079d93e

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..000be46

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..9f58c16

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..75e6829

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..bcd8822

Lines of this file are not shown. View the raw message.

52 lines not on this page · raw message

new file mode 100644
index 0000000..5ee04e7

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..12bda0a

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..ab633ab

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..1615f83

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..b50d279

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..db7ade0

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..aa1ac16

Lines of this file are not shown. View the raw message.

41 lines not on this page · raw message

new file mode 100644
index 0000000..3278ff3

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..f0f60db

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..e183751

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..3cef7cb

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..dc8b64f

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..d1755fd

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..e59dc22

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..68a981c

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..54b7b65

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..30e72b8

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..729b77a

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..00327ee

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..1905d40

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..af55c0f

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..a814169

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..eed4f3b

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..b8dce09

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..46b9034

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..0fdc7f7

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..64edcac

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..d9940fc

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..2ae8530

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..65a1e0f

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..4e0a1ef

Lines of this file are not shown. View the raw message.

50 lines not on this page · raw message

new file mode 100644
index 0000000..78773b9

Lines of this file are not shown. View the raw message.

69 lines not on this page · raw message

58 lines not on this page · raw message

new file mode 100644
index 0000000..dc08d17

Lines of this file are not shown. View the raw message.

66 lines not on this page · raw message

new file mode 100644
index 0000000..c1ee3d8

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..ebc6c62

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..4f73445

Lines of this file are not shown. View the raw message.

52 lines not on this page · raw message

new file mode 100644
index 0000000..ffcfd24

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..06a3b7f

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..9450f1a

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..c48b00e

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..d4eb1a8

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..709af32

Lines of this file are not shown. View the raw message.

68 lines not on this page · raw message

new file mode 100644
index 0000000..ae185be

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..9a8b72d

Lines of this file are not shown. View the raw message.

new file mode 100644
index 0000000..07d0c64

Lines of this file are not shown. View the raw message.

57 lines not on this page · raw message

43 lines not on this page · raw message

new file mode 100644
index 0000000..5be3508

Lines of this file are not shown. View the raw message.

index 5d678c1..7ce4771 100644

Lines of this file are not shown. View the raw message.

182 lines not on this page · raw message

index 4e642ec..3d7d0f2 100644

Lines of this file are not shown. View the raw message.

index a41e016..7ce688d 100644
@@ -120,6 +120,28 @@
 			</a>
 		<br />
 			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
+		<br />
+		<br />
+		<strong>
+			The Yocto Project Board Support Package (BSP) Developer's Guide:
+		</strong>
+		<br />
+		<br />
+			This brief document defines a structure for BSP components. 
+			Having a commonly understood layout encourages standardization.
+		<br />
+		<br />
+			<em>License:</em>
+			<a href="http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode">
+				http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode
+			</a>
+		<br />
+			<em>Source Code Repository:</em>
+			<a href="git://git.yoctoproject.org/yocto-docs">
+				git://git.yoctoproject.org/yocto-docs
+			</a>
+		<br />
+			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
 	</p>
 </body>
 </html>

new file mode 100644
index 0000000..36ed786
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="utf-8" standalone="no"?>
+<toc label="The Yocto Project Board Support Package Developer's Guide" topic="html/bsp-guide/index.html">
+  <topic label="Board Support Packages (BSP) - Developer's Guide" href="html/bsp-guide/bsp.html">
+    <topic label="BSP Layers" href="html/bsp-guide/bsp-layers.html"/>
+    <topic label="Example Filesystem Layout" href="html/bsp-guide/bsp-filelayout.html">
+      <topic label="License Files" href="html/bsp-guide/bsp-filelayout-license.html"/>
+      <topic label="README File" href="html/bsp-guide/bsp-filelayout-readme.html"/>
+      <topic label="README.sources File" href="html/bsp-guide/bsp-filelayout-readme-sources.html"/>
+      <topic label="Pre-built User Binaries" href="html/bsp-guide/bsp-filelayout-binary.html"/>
+      <topic label="Layer Configuration File" href="html/bsp-guide/bsp-filelayout-layer.html"/>
+      <topic label="Hardware Configuration Options" href="html/bsp-guide/bsp-filelayout-machine.html"/>
+      <topic label="Miscellaneous Recipe Files" href="html/bsp-guide/bsp-filelayout-misc-recipes.html"/>
+      <topic label="Display Support Files" href="html/bsp-guide/bsp-filelayout-recipes-graphics.html"/>
+      <topic label="Linux Kernel Configuration" href="html/bsp-guide/bsp-filelayout-kernel.html"/>
+    </topic>
+    <topic label="Requirements and Recommendations for Released BSPs" href="html/bsp-guide/requirements-and-recommendations-for-released-bsps.html">
+      <topic label="Released BSP Requirements" href="html/bsp-guide/released-bsp-requirements.html"/>
+      <topic label="Released BSP Recommendations" href="html/bsp-guide/released-bsp-recommendations.html"/>
+    </topic>
+    <topic label="Customizing a Recipe for a BSP" href="html/bsp-guide/customizing-a-recipe-for-a-bsp.html"/>
+    <topic label="BSP Licensing Considerations" href="html/bsp-guide/bsp-licensing-considerations.html"/>
+    <topic label="Using the Yocto Project's BSP Tools" href="html/bsp-guide/using-the-yocto-projects-bsp-tools.html">
+      <topic label="Common Features" href="html/bsp-guide/common-features.html"/>
+      <topic label="Creating a new BSP Layer Using the yocto-bsp Script" href="html/bsp-guide/creating-a-new-bsp-layer-using-the-yocto-bsp-script.html"/>
+      <topic label="Managing Kernel Patches and Config Items with yocto-kernel" href="html/bsp-guide/managing-kernel-patches-and-config-items-with-yocto-kernel.html"/>
+    </topic>
+  </topic>
+</toc>

index 3350a45..833e841 100644
@@ -8,11 +8,13 @@ bin.includes = plugin.xml,\
                adt-manual-toc.xml,\
                OSGI-INF/,\
                dev-manual-toc.xml,\
-               poky-ref-manual-toc.xml
+               poky-ref-manual-toc.xml,\
+               bsp-guide-toc.xml
 src.includes = toc.xml,\
                html/,\
                yocto-project-qs-toc.xml,\
                about.html,\
                adt-manual-toc.xml,\
                dev-manual-toc.xml,\
-               poky-ref-manual-toc.xml
+               poky-ref-manual-toc.xml,\
+               bsp-guide-toc.xml

new file mode 100644
index 0000000..dba9f4a
@@ -0,0 +1,40 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.2.4.�Pre-built User Binaries</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Board Support Package Developer's Guide">
+<link rel="up" href="bsp-filelayout.html" title="1.2.�Example Filesystem Layout">
+<link rel="prev" href="bsp-filelayout-readme-sources.html" title="1.2.3.�README.sources File">
+<link rel="next" href="bsp-filelayout-layer.html" title="1.2.5.�Layer Configuration File">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.2.4.�Pre-built User Binaries">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="bsp-filelayout-binary"></a>1.2.4.�Pre-built User Binaries</h3></div></div></div>
+<p>
+                You can find these files in the BSP Layer at:
+                </p>
+<pre class="literallayout">
+     meta-&lt;bsp_name&gt;/binary/&lt;bootable_images&gt;
+                </pre>
+<p>
+            </p>
+<p>
+                This optional area contains useful pre-built kernels and user-space filesystem 
+                images appropriate to the target system.
+                This directory typically contains graphical (e.g. sato) and minimal live images 
+                when the BSP tarball has been created and made available in the 
+                <a class="ulink" href="http://www.yoctoproject.org" target="_self">Yocto Project</a> website. 
+                You can use these kernels and images to get a system running and quickly get started 
+                on development tasks.
+            </p>
+<p> 
+                The exact types of binaries present are highly hardware-dependent.
+                However, a README file should be present in the BSP Layer that explains how to use 
+                the kernels and images with the target hardware. 
+                If pre-built binaries are present, source code to meet licensing requirements must also 
+                exist in some form.
+            </p>
+</div></body>
+</html>

188 lines not on this page · raw message

65 lines not on this page · raw message

new file mode 100644
index 0000000..79cfa8b
@@ -0,0 +1,34 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.2.1.�License Files</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Board Support Package Developer's Guide">
+<link rel="up" href="bsp-filelayout.html" title="1.2.�Example Filesystem Layout">
+<link rel="prev" href="bsp-filelayout.html" title="1.2.�Example Filesystem Layout">
+<link rel="next" href="bsp-filelayout-readme.html" title="1.2.2.�README File">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.2.1.�License Files">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="bsp-filelayout-license"></a>1.2.1.�License Files</h3></div></div></div>
+<p>
+                You can find these files in the BSP Layer at:
+                </p>
+<pre class="literallayout">
+     meta-&lt;bsp_name&gt;/&lt;bsp_license_file&gt;
+                </pre>
+<p>
+            </p>
+<p>
+                These optional files satisfy licensing requirements for the BSP.
+                The type or types of files here can vary depending on the licensing requirements.
+                For example, in the Crown Bay BSP all licensing requirements are handled with the 
+                <code class="filename">COPYING.MIT</code> file.  
+            </p>
+<p>
+                Licensing files can be MIT, BSD, GPLv*, and so forth.
+                These files are recommended for the BSP but are optional and totally up to the BSP developer.
+            </p>
+</div></body>
+</html>

79 lines not on this page · raw message

56 lines not on this page · raw message

new file mode 100644
index 0000000..64aff0a
@@ -0,0 +1,31 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.2.3.�README.sources File</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Board Support Package Developer's Guide">
+<link rel="up" href="bsp-filelayout.html" title="1.2.�Example Filesystem Layout">
+<link rel="prev" href="bsp-filelayout-readme.html" title="1.2.2.�README File">
+<link rel="next" href="bsp-filelayout-binary.html" title="1.2.4.�Pre-built User Binaries">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.2.3.�README.sources File">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="bsp-filelayout-readme-sources"></a>1.2.3.�README.sources File</h3></div></div></div>
+<p>
+                You can find this file in the BSP Layer at:
+                </p>
+<pre class="literallayout">
+     meta-&lt;bsp_name&gt;/README.sources
+                </pre>
+<p>
+            </p>
+<p>
+                This file provides information on where to locate the BSP source files.
+                For example, information provides where to find the sources that comprise
+                the images shipped with the BSP.
+                Information is also included to help you find the metadata used to generate the images
+                that ship with the BSP.
+            </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..c657a27
@@ -0,0 +1,36 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.2.2.�README File</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Board Support Package Developer's Guide">
+<link rel="up" href="bsp-filelayout.html" title="1.2.�Example Filesystem Layout">
+<link rel="prev" href="bsp-filelayout-license.html" title="1.2.1.�License Files">
+<link rel="next" href="bsp-filelayout-readme-sources.html" title="1.2.3.�README.sources File">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.2.2.�README File">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="bsp-filelayout-readme"></a>1.2.2.�README File</h3></div></div></div>
+<p>
+                You can find this file in the BSP Layer at:
+                </p>
+<pre class="literallayout">
+     meta-&lt;bsp_name&gt;/README
+                </pre>
+<p>
+            </p>
+<p>
+                This file provides information on how to boot the live images that are optionally 
+                included in the <code class="filename">binary/</code> directory.
+                The <code class="filename">README</code> file also provides special information needed for 
+                building the image.
+            </p>
+<p>
+                At a minimum, the <code class="filename">README</code> file must
+                contain a list of dependencies, such as the names of
+                any other layers on which the BSP depends and the name of
+                the BSP maintainer with his or her contact information.
+            </p>
+</div></body>
+</html>

42 lines not on this page · raw message

113 lines not on this page · raw message

71 lines not on this page · raw message

125 lines not on this page · raw message

67 lines not on this page · raw message

138 lines not on this page · raw message

191 lines not on this page · raw message

56 lines not on this page · raw message

new file mode 100644
index 0000000000000000000000000000000000000000..f624dd4f941c62c77070f1fd9fcf0977fbb352a5
GIT binary patch

130 lines not on this page · raw message

153 lines not on this page · raw message

58 lines not on this page · raw message

184 lines not on this page · raw message

new file mode 100644
index 0000000..9cc6ba4
@@ -0,0 +1,23 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.3.�Requirements and Recommendations for Released BSPs</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Board Support Package Developer's Guide">
+<link rel="up" href="bsp.html" title="Chapter�1.�Board Support Packages (BSP) - Developer's Guide">
+<link rel="prev" href="bsp-filelayout-kernel.html" title="1.2.9.�Linux Kernel Configuration">
+<link rel="next" href="released-bsp-requirements.html" title="1.3.1.�Released BSP Requirements">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.3.�Requirements and Recommendations for Released BSPs">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="requirements-and-recommendations-for-released-bsps"></a>1.3.�Requirements and Recommendations for Released BSPs</h2></div></div></div>
+<p>
+                Certain requirements exist for a released BSP to be considered
+                compliant with the Yocto Project.
+                Additionally, a single recommendation also exists. 
+                This section describes the requirements and recommendation for
+                released BSPs.
+            </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..7547f75
@@ -0,0 +1,29 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>1.6.�Using the Yocto Project's BSP Tools</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Board Support Package Developer's Guide">
+<link rel="up" href="bsp.html" title="Chapter�1.�Board Support Packages (BSP) - Developer's Guide">
+<link rel="prev" href="bsp-licensing-considerations.html" title="1.5.�BSP Licensing Considerations">
+<link rel="next" href="common-features.html" title="1.6.1.�Common Features">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.6.�Using the Yocto Project's BSP Tools">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="using-the-yocto-projects-bsp-tools"></a>1.6.�Using the Yocto Project's BSP Tools</h2></div></div></div>
+<p>
+                The Yocto Project includes a couple of tools that enable
+                you to create a <a class="link" href="bsp-layers.html" title="1.1.�BSP Layers">BSP layer</a> 
+                from scratch and do basic configuration and maintenance 
+                of the kernel without ever looking at a metadata file.
+                These tools are <code class="filename">yocto-bsp</code> and <code class="filename">yocto-kernel</code>,
+                respectively. 
+	    </p>
+<p>
+                The following sections describe the common location and help features as well 
+                as details for the <code class="filename">yocto-bsp</code> and <code class="filename">yocto-kernel</code> 
+                tools.
+            </p>
+</div></body>
+</html>

index 7ce4771..da26279 100644
@@ -23,5 +23,9 @@
           file="poky-ref-manual-toc.xml"
           primary="false">
     </toc>
+    <toc
+          file="bsp-guide-toc.xml"
+          primary="false">
+    </toc>
  </extension>
 </plugin>

index 3d7d0f2..af26d88 100644
@@ -12,4 +12,7 @@
    <topic label="The Yocto Project Reference Manual">
       <link toc="poky-ref-manual-toc.xml"/>
    </topic>
+   <topic label="The Yocto Project Board Support Package Developer&apos;s Guide">
+      <link toc="bsp-guide-toc.xml"/>
+   </topic>
 </toc>

index 7ce688d..c6ece55 100644
@@ -142,6 +142,28 @@
 			</a>
 		<br />
 			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
+		<br />
+		<br />
+		<strong>
+			Yocto Project Kernel Architecture and Use Manual:
+		</strong>
+		<br />
+		<br />
+			  This document describes the architecture of the Yocto Project
+			  kernel and provides some work flow examples.
+		<br />
+		<br />
+			<em>License:</em>
+			<a href="http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode">
+				http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode
+			</a>
+		<br />
+			<em>Source Code Repository:</em>
+			<a href="git://git.yoctoproject.org/yocto-docs">
+				git://git.yoctoproject.org/yocto-docs
+			</a>
+		<br />
+			<em>Commit:</em> abc32d85a7f241766d1fcc52a251249f2172ea89
 	</p>
 </body>
 </html>

index 833e841..788e9e9 100644
@@ -9,7 +9,8 @@ bin.includes = plugin.xml,\
                OSGI-INF/,\
                dev-manual-toc.xml,\
                poky-ref-manual-toc.xml,\
-               bsp-guide-toc.xml
+               bsp-guide-toc.xml,\
+               kernel-manual-toc.xml
 src.includes = toc.xml,\
                html/,\
                yocto-project-qs-toc.xml,\

@@ -17,4 +18,5 @@ src.includes = toc.xml,\
                adt-manual-toc.xml,\
                dev-manual-toc.xml,\
                poky-ref-manual-toc.xml,\
-               bsp-guide-toc.xml
+               bsp-guide-toc.xml,\
+               kernel-manual-toc.xml

new file mode 100644
index 0000000..bfc21e5
@@ -0,0 +1,29 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.1.�Introduction</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="kernel-how-to.html" title="Chapter�3.�Working with the Yocto Project Kernel">
+<link rel="prev" href="kernel-how-to.html" title="Chapter�3.�Working with the Yocto Project Kernel">
+<link rel="next" href="tree-construction.html" title="3.2.�Tree Construction">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.1.�Introduction">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="actions-org"></a>3.1.�Introduction</h2></div></div></div>
+<p>
+        This chapter describes how to accomplish tasks involving a kernel's tree structure. 
+        The information is designed to help the developer that wants to modify the Yocto 
+        Project kernel and contribute changes upstream to the Yocto Project.
+        The information covers the following:
+        </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>Tree construction</p></li>
+<li class="listitem"><p>Build strategies</p></li>
+<li class="listitem"><p>Workflow examples</p></li>
+</ul></div>
+<p>
+    </p>
+</div></body>
+</html>

79 lines not on this page · raw message

81 lines not on this page · raw message

71 lines not on this page · raw message

82 lines not on this page · raw message

53 lines not on this page · raw message

new file mode 100644
index 0000000..2611910
@@ -0,0 +1,36 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.4.1.�Change Inspection: Changes/Commits</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="workflow-examples.html" title="3.4.�Workflow Examples">
+<link rel="prev" href="workflow-examples.html" title="3.4.�Workflow Examples">
+<link rel="next" href="what-changed-in-a-kernel.html" title="3.4.1.1.�What Changed in a Kernel?">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.1.�Change Inspection: Changes/Commits">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="change-inspection-kernel-changes-commits"></a>3.4.1.�Change Inspection: Changes/Commits</h3></div></div></div>
+<p>
+                A common question when working with a kernel is: 
+                "What changes have been applied to this tree?"
+            </p>
+<p>
+                In projects that have a collection of directories that
+                contain patches to the kernel, it is possible to inspect or "grep" the contents 
+                of the directories to get a general feel for the changes. 
+                This sort of patch inspection is not an efficient way to determine what has been 
+                done to the kernel.
+                The reason it is inefficient is because there are many optional patches that are 
+                selected based on the kernel type and the feature description.
+                Additionally, patches could exist in directories that are not included in the search.
+            </p>
+<p>
+                A more efficient way to determine what has changed in the branch is to use
+                Git and inspect or search the kernel tree. 
+                This method gives you a full view of not only the source code modifications, 
+                but also provides the reasons for the changes.
+            </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..9375e86
@@ -0,0 +1,27 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.1.�Introduction</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="kernel-concepts.html" title="Chapter�2.�Yocto Project Kernel Concepts">
+<link rel="prev" href="kernel-concepts.html" title="Chapter�2.�Yocto Project Kernel Concepts">
+<link rel="next" href="kernel-goals.html" title="2.2.�Kernel Goals">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.1.�Introduction">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="concepts-org"></a>2.1.�Introduction</h2></div></div></div>
+<p>
+        This chapter provides conceptual information about the kernel:
+        </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>Kernel Goals</p></li>
+<li class="listitem"><p>Kernel Development and Maintenance Overview</p></li>
+<li class="listitem"><p>Kernel Architecture</p></li>
+<li class="listitem"><p>Kernel Tools</p></li>
+</ul></div>
+<p>
+    </p>
+</div></body>
+</html>

68 lines not on this page · raw message

72 lines not on this page · raw message

new file mode 100644
index 0000000..0b4243b
@@ -0,0 +1,30 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.4.2.4.�Exporting Changes for Import into Another SCM</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="development-saving-kernel-modifications.html" title="3.4.2.�Development: Saving Kernel Modifications">
+<link rel="prev" href="export-for-external-upstream-submission.html" title="3.4.2.3.�Exporting Changes for External (Upstream) Submission">
+<link rel="next" href="scm-working-with-the-yocto-project-kernel-in-another-scm.html" title="3.4.3.�Working with the Yocto Project Kernel in Another SCM">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.2.4.�Exporting Changes for Import into Another SCM">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="export-for-import-into-other-scm"></a>3.4.2.4.�Exporting Changes for Import into Another SCM</h4></div></div></div>
+<p>
+                    When you want to export changes for import into another
+                    Source Code Manager (SCM), you can use any of the previously discussed 
+                    techniques.
+                    However, if the patches are manually applied to a secondary tree and then 
+                    that tree is checked into the SCM, you can lose change information such as 
+                    commit logs.
+                    This process is not recommended.
+                </p>
+<p>
+                    Many SCMs can directly import Git commits, or can translate Git patches so that
+                    information is not lost. 
+                    Those facilities are SCM-dependent and you should use them whenever possible.
+                </p>
+</div></body>
+</html>

55 lines not on this page · raw message

64 lines not on this page · raw message

54 lines not on this page · raw message

new file mode 100755
index 0000000000000000000000000000000000000000..2aad172db3b84382f5be412447a005f3846a5c9d
GIT binary patch

new file mode 100644
index 0000000000000000000000000000000000000000..59d86c00dca5e2475f7cdee54f82d6ff8c027a47
GIT binary patch

new file mode 100644
index 0000000..4ce0f79
@@ -0,0 +1,22 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.4.3.2.�Importing Changes for the Build</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="scm-working-with-the-yocto-project-kernel-in-another-scm.html" title="3.4.3.�Working with the Yocto Project Kernel in Another SCM">
+<link rel="prev" href="exporting-delivered-kernel-to-scm.html" title="3.4.3.1.�Exporting the Delivered Kernel to the SCM">
+<link rel="next" href="bsp-creating.html" title="3.4.4.�Creating a BSP Based on an Existing Similar BSP">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.3.2.�Importing Changes for the Build">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="importing-changes-for-build"></a>3.4.3.2.�Importing Changes for the Build</h4></div></div></div>
+<p>
+                    Once development has reached a suitable point in the second development
+                    environment, you need to export the changes as patches.
+                    To export them, place the changes in a recipe and
+                    automatically apply them to the kernel during patching.
+                </p>
+</div></body>
+</html>

111 lines not on this page · raw message

126 lines not on this page · raw message

new file mode 100644
index 0000000..0a50300
@@ -0,0 +1,21 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.4.�Kernel Architecture</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="kernel-concepts.html" title="Chapter�2.�Yocto Project Kernel Concepts">
+<link rel="prev" href="kernel-big-picture.html" title="2.3.�Yocto Project Kernel Development and Maintenance Overview">
+<link rel="next" href="architecture-overview.html" title="2.4.1.�Overview">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4.�Kernel Architecture">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="kernel-architecture"></a>2.4.�Kernel Architecture</h2></div></div></div>
+<p>
+            This section describes the architecture of the kernels available through the 
+            Yocto Project and provides information
+            on the mechanisms used to achieve that architecture.
+        </p>
+</div></body>
+</html>

91 lines not on this page · raw message

new file mode 100644
index 0000000..c042c13
@@ -0,0 +1,32 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter�2.�Yocto Project Kernel Concepts</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="prev" href="kernel-intro-section.html" title="1.1.�Introduction">
+<link rel="next" href="concepts-org.html" title="2.1.�Introduction">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter�2.�Yocto Project Kernel Concepts">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="kernel-concepts"></a>Chapter�2.�Yocto Project Kernel Concepts</h2></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="concepts-org.html">2.1. Introduction</a></span></dt>
+<dt><span class="section"><a href="kernel-goals.html">2.2. Kernel Goals</a></span></dt>
+<dt><span class="section"><a href="kernel-big-picture.html">2.3. Yocto Project Kernel Development and Maintenance Overview</a></span></dt>
+<dt><span class="section"><a href="kernel-architecture.html">2.4. Kernel Architecture</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="architecture-overview.html">2.4.1. Overview</a></span></dt>
+<dt><span class="section"><a href="branching-and-workflow.html">2.4.2. Branching Strategy and Workflow</a></span></dt>
+<dt><span class="section"><a href="source-code-manager-git.html">2.4.3. Source Code Manager - Git</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="kernel-configuration.html">2.5. Kernel Configuration</a></span></dt>
+<dt><span class="section"><a href="kernel-tools.html">2.6. Kernel Tools</a></span></dt>
+</dl>
+</div>
+</div></body>
+</html>

85 lines not on this page · raw message

new file mode 100644
index 0000000..498edc4
@@ -0,0 +1,20 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter�1.�Yocto Project Kernel Architecture and Use Manual</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="prev" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="next" href="kernel-intro-section.html" title="1.1.�Introduction">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter�1.�Yocto Project Kernel Architecture and Use Manual">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="kernel-doc-intro"></a>Chapter�1.�Yocto Project Kernel Architecture and Use Manual</h2></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl><dt><span class="section"><a href="kernel-intro-section.html">1.1. Introduction</a></span></dt></dl>
+</div>
+</div></body>
+</html>

55 lines not on this page · raw message

new file mode 100644
index 0000000..a36c561
@@ -0,0 +1,32 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Chapter�3.�Working with the Yocto Project Kernel</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="prev" href="kernel-tools.html" title="2.6.�Kernel Tools">
+<link rel="next" href="actions-org.html" title="3.1.�Introduction">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter�3.�Working with the Yocto Project Kernel">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="kernel-how-to"></a>Chapter�3.�Working with the Yocto Project Kernel</h2></div></div></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="actions-org.html">3.1. Introduction</a></span></dt>
+<dt><span class="section"><a href="tree-construction.html">3.2. Tree Construction</a></span></dt>
+<dt><span class="section"><a href="build-strategy.html">3.3. Build Strategy</a></span></dt>
+<dt><span class="section"><a href="workflow-examples.html">3.4. Workflow Examples</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="change-inspection-kernel-changes-commits.html">3.4.1. Change Inspection: Changes/Commits</a></span></dt>
+<dt><span class="section"><a href="development-saving-kernel-modifications.html">3.4.2. Development: Saving Kernel Modifications</a></span></dt>
+<dt><span class="section"><a href="scm-working-with-the-yocto-project-kernel-in-another-scm.html">3.4.3. Working with the Yocto Project Kernel in Another SCM</a></span></dt>
+<dt><span class="section"><a href="bsp-creating.html">3.4.4. Creating a BSP Based on an Existing Similar BSP</a></span></dt>
+<dt><span class="section"><a href="tip-dirty-string.html">3.4.5. "-dirty" String</a></span></dt>
+</dl></dd>
+</dl>
+</div>
+</div></body>
+</html>

73 lines not on this page · raw message

new file mode 100644
index 0000000..8a32531
@@ -0,0 +1,35 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.6.�Kernel Tools</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="kernel-concepts.html" title="Chapter�2.�Yocto Project Kernel Concepts">
+<link rel="prev" href="kernel-configuration.html" title="2.5.�Kernel Configuration">
+<link rel="next" href="kernel-how-to.html" title="Chapter�3.�Working with the Yocto Project Kernel">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.6.�Kernel Tools">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="kernel-tools"></a>2.6.�Kernel Tools</h2></div></div></div>
+<p>
+            Since most standard workflows involve moving forward with an existing tree by
+            continuing to add and alter the underlying baseline, the tools that manage
+            the Yocto Project's kernel construction are largely hidden from the developer to
+            present a simplified view of the kernel for ease of use.
+        </p>
+<p>
+            Fundamentally, the kernel tools that manage and construct the
+            Yocto Project kernel accomplish the following:
+            </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>Group patches into named, reusable features.</p></li>
+<li class="listitem"><p>Allow top-down control of included features.</p></li>
+<li class="listitem"><p>Bind kernel configurations to kernel patches and features.</p></li>
+<li class="listitem"><p>Present a seamless Git repository that blends Yocto Project value 
+                    with the <code class="filename">kernel.org</code> history and development.</p></li>
+</ul></div>
+<p>
+        </p>
+</div></body>
+</html>

new file mode 100644
index 0000000..23f7044
@@ -0,0 +1,31 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.4.3.�Working with the Yocto Project Kernel in Another SCM</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="workflow-examples.html" title="3.4.�Workflow Examples">
+<link rel="prev" href="export-for-import-into-other-scm.html" title="3.4.2.4.�Exporting Changes for Import into Another SCM">
+<link rel="next" href="exporting-delivered-kernel-to-scm.html" title="3.4.3.1.�Exporting the Delivered Kernel to the SCM">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.3.�Working with the Yocto Project Kernel in Another SCM">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="scm-working-with-the-yocto-project-kernel-in-another-scm"></a>3.4.3.�Working with the Yocto Project Kernel in Another SCM</h3></div></div></div>
+<p>
+                This section describes kernel development in an SCM other than Git, 
+                which is not the same as exporting changes to another SCM described earlier.
+                For this scenario, you use the OpenEmbedded build system to 
+                develop the kernel in a different SCM.
+                The following must be true for you to accomplish this:
+                </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>The delivered Yocto Project kernel must be exported into the second
+                        SCM.</p></li>
+<li class="listitem"><p>Development must be exported from that secondary SCM into a 
+                        format that can be used by the OpenEmbedded build system.</p></li>
+</ul></div>
+<p>
+            </p>
+</div></body>
+</html>

53 lines not on this page · raw message

new file mode 100644
index 0000000..9c8c016
@@ -0,0 +1,39 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>2.4.3.�Source Code Manager - Git</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="kernel-architecture.html" title="2.4.�Kernel Architecture">
+<link rel="prev" href="branching-and-workflow.html" title="2.4.2.�Branching Strategy and Workflow">
+<link rel="next" href="kernel-configuration.html" title="2.5.�Kernel Configuration">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4.3.�Source Code Manager - Git">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="source-code-manager-git"></a>2.4.3.�Source Code Manager - Git</h3></div></div></div>
+<p>
+                The Source Code Manager (SCM) is Git.
+                This SCM is the obvious mechanism for meeting the previously mentioned goals.  
+                Not only is it the SCM for <code class="filename">kernel.org</code> but,
+                Git continues to grow in popularity and supports many different work flows, 
+                front-ends and management techniques.
+            </p>
+<p>
+                You can find documentation on Git at <a class="ulink" href="http://git-scm.com/documentation" target="_self">http://git-scm.com/documentation</a>.
+                You can also get an introduction to Git as it applies to the Yocto Project in the
+                "<a class="link" href="../dev-manual/git.html" target="_self">Git</a>"
+                section in the Yocto Project Development Manual. 
+                These referenced sections overview Git and describe a minimal set of 
+                commands that allows you to be functional using Git.
+                </p>
+<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
+<h3 class="title">Note</h3>
+                    You can use as much, or as little, of what Git has to offer to accomplish what
+                    you need for your project.
+                    You do not have to be a "Git Master" in order to use it with the Yocto Project.
+                </div>
+<p>
+            </p>
+</div></body>
+</html>

43 lines not on this page · raw message

158 lines not on this page · raw message

98 lines not on this page · raw message

new file mode 100644
index 0000000..677e208
@@ -0,0 +1,34 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>3.4.�Workflow Examples</title>
+<link rel="stylesheet" type="text/css" href="../book.css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<link rel="home" href="index.html" title="The Yocto Project Kernel Architecture and Use Manual">
+<link rel="up" href="kernel-how-to.html" title="Chapter�3.�Working with the Yocto Project Kernel">
+<link rel="prev" href="build-strategy.html" title="3.3.�Build Strategy">
+<link rel="next" href="change-inspection-kernel-changes-commits.html" title="3.4.1.�Change Inspection: Changes/Commits">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.�Workflow Examples">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="workflow-examples"></a>3.4.�Workflow Examples</h2></div></div></div>
+<p>
+            As previously noted, the Yocto Project kernel has built-in Git integration.
+            However, these utilities are not the only way to work with the kernel repository.
+            The Yocto Project has not made changes to Git or to other tools that
+            would invalidate alternate workflows. 
+            Additionally, the way the kernel repository is constructed results in using 
+            only core Git functionality, thus allowing any number of tools or front ends to use the 
+            resulting tree.
+        </p>
+<p>
+            This section contains several workflow examples.
+            Many of the examples use Git commands. 
+            You can find Git documentation at 
+            <a class="ulink" href="http://git-scm.com/documentation" target="_self">http://git-scm.com/documentation</a>.
+            You can find a simple overview of using Git with the Yocto Project in the 
+            "<a class="link" href="../dev-manual/git.html" target="_self">Git</a>"
+            section of the Yocto Project Development Manual.
+        </p>
+</div></body>
+</html>

44 lines not on this page · raw message

index da26279..9730b3e 100644
@@ -27,5 +27,9 @@
           file="bsp-guide-toc.xml"
           primary="false">
     </toc>
+    <toc
+          file="kernel-manual-toc.xml"
+          primary="false">
+    </toc>
  </extension>
 </plugin>

index af26d88..671054c 100644
@@ -15,4 +15,7 @@
    <topic label="The Yocto Project Board Support Package Developer&apos;s Guide">
       <link toc="bsp-guide-toc.xml"/>
    </topic>
+   <topic label="The Yocto Project Kernel Architecture and Use Manual">
+      <link toc="kernel-manual-toc.xml"/>
+   </topic>
 </toc>