From ea793b23c98403cefb38670d02a778b843bdf997 Mon Sep 17 00:00:00 2001
From: John Ogness <john.ogness@linutronix.de>
Date: Thu, 19 Apr 2018 11:03:45 +0200
Subject: replace *all* tabs with spaces

There are times when tabs are allowed and times when they are not.
Let's just simply never use tabs for anything. This makes it easy
to find presentations where tabs were accidentally inserted.

Signed-off-by: John Ogness <john.ogness@linutronix.de>
---
 distribution/yocto-intro/yocto-intro.tex | 56 ++++++++++++++++----------------
 1 file changed, 28 insertions(+), 28 deletions(-)

(limited to 'distribution/yocto-intro/yocto-intro.tex')

diff --git a/distribution/yocto-intro/yocto-intro.tex b/distribution/yocto-intro/yocto-intro.tex
index 14cde2d..23cb185 100644
--- a/distribution/yocto-intro/yocto-intro.tex
+++ b/distribution/yocto-intro/yocto-intro.tex
@@ -1,27 +1,27 @@
 \begin{frame}
 \frametitle{Yocto is \dots}
 \begin{itemize}
-	\item an Ecosystem (not a single open-source project)
-	\item a collection of embedded projects and tooling
-	\item a place for Industry to publish BSPs
-	\item NOT an embedded Linux distribution
+\item an Ecosystem (not a single open-source project)
+\item a collection of embedded projects and tooling
+\item a place for Industry to publish BSPs
+\item NOT an embedded Linux distribution
 \end{itemize}
 \dots used to build a Linux system from source in about an hour \footnote{quad i7, 16GB
-	RAM, fast disks, needed}
+        RAM, fast disks, needed}
 \end{frame}
 
 \begin{frame}
 \frametitle{the Yocto project family}
 \begin{description}
-	\item[Poky] reference build system / distribution
-	\begin{description}
-		\item[BitBake] build-engine
-		\item[Toaster] graphical user interface for BitBake
-		\item[meta] shared base layer of recipes and classes
-		\item[Example BSPs] for qemux86, mpc8315e-rdb, beaglebone
-	\end{description}
-	\item[ADT] development environment for user-space applications
-	\item[Eclipse IDE Plugin] integration of ADT into the Eclipse IDE
+\item[Poky] reference build system / distribution
+\begin{description}
+\item[BitBake] build-engine
+\item[Toaster] graphical user interface for BitBake
+\item[meta] shared base layer of recipes and classes
+\item[Example BSPs] for qemux86, mpc8315e-rdb, beaglebone
+\end{description}
+\item[ADT] development environment for user-space applications
+\item[Eclipse IDE Plugin] integration of ADT into the Eclipse IDE
 \end{description}
 \end{frame}
 
@@ -29,12 +29,12 @@
 \frametitle{Poky is \dots}
 the Yocto key project; a reference distribution consisting of
 \begin{itemize}
-	\item a build system for Linux (openembedded + customized busybox,
-		psplash, alsa-state and tiny-init)
-	\item Yocto Linux kernel
-	\item build recipes for common open-source software from openembedded
-	\item able to generate toolchains for several architectures
-	\item documentation
+\item a build system for Linux (openembedded + customized busybox,
+        psplash, alsa-state and tiny-init)
+\item Yocto Linux kernel
+\item build recipes for common open-source software from openembedded
+\item able to generate toolchains for several architectures
+\item documentation
 \end{itemize}
 release cycle: about 6 months
 \end{frame}
@@ -93,19 +93,19 @@ freescale.com        &   159       &         187 &  0,52\% &  0,43\%  \\
 \begin{frame}
 \frametitle{Yocto principles}
 \begin{itemize}
-	\item poky provides a collection of software build recipes
-	\item customize build recipe blueprints for your own needs
-	\item distinguishing between app and system developers
-	\item layer model for modular development, reuse, and customizations
+\item poky provides a collection of software build recipes
+\item customize build recipe blueprints for your own needs
+\item distinguishing between app and system developers
+\item layer model for modular development, reuse, and customizations
 \end{itemize}
 \end{frame}
 
 \begin{frame}
 \frametitle{cross-build vs. binary distribution}
 \begin{itemize}
-	\item men-power needed for building an own distribution?
-	\item security tracking?
-	\item optimizations needed on all binaries?
-	\item cross-compile wanted?
+\item men-power needed for building an own distribution?
+\item security tracking?
+\item optimizations needed on all binaries?
+\item cross-compile wanted?
 \end{itemize}
 \end{frame}
-- 
cgit v1.2.3

