\input{configpres}

\title{YOCTO - Advanced}
\date{}
\maketitle

\begin{frame}
\frametitle{Agenda}
\begin{itemize}
\item Using BSP layers
\item Create layers \& recipes for own applications
\item Define a distribution
\item Integrate own Kernel
\end{itemize}
\end{frame}

\input{yocto-local-conf}
\input{yocto-layers}
%\input{yocto-wega-layer}
\input{yocto-create-own-layer}
\input{yocto-add-simple-application}
\input{yocto-add-autotools-based-src}
\input{yocto-layer-imx6}
\input{yocto-add-own-kernel}
%\input{yocto-flash-official-bb-img}
%\input{yocto-bbb-machine-conf}
%\input{yocto-u-boot-integration}
%\input{yocto-sdcard-generation}
\input{yocto-distro-definitions}
\input{yocto-extend-image}
%\input{yocto-add-qt-cmake-projects}
\input{yocto-img-customization}
\begin{frame}[fragile]
\frametitle{override default config files}
default templates can be overridden by setting TEMPLATECONF
to e.g. meta-foo/conf during ./oe-init-buildenv.

Then meta-foo/conf bblayers.conf.sample and local.conf.sample will
be used.

The default location is specified in

\begin{verbatim}
% cat .templateconf
# Template settings
TEMPLATECONF=${TEMPLATECONF:-meta-yocto/conf}
\end{verbatim}
\end{frame}
\input{yocto-scripts}
\input{yocto-resume}

\begin{frame}
\frametitle{Application Development Excercise}
\begin{itemize}
\item generate a standalone or integrated SDK
\item configure the SDK in eclipse
\item build and remote debug yesterdays application on the beaglebone-black
\item integrate the application into the image
\item build the image including your application
\end{itemize}
\end{frame}

\input{tailpres}
