[bootlin/training-materials updates] master: slides/buildroot-appdev: re-order one slide (2bdb4e84)

[Thomas Petazzoni]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/2bdb4e84325c2ec11719ec7e8ef7fbe0fc808759

>---------------------------------------------------------------

commit 2bdb4e84325c2ec11719ec7e8ef7fbe0fc808759
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Fri Dec 10 16:56:29 2021 +0100

    slides/buildroot-appdev: re-order one slide
    
    Will be more logical to have it earlier.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


>---------------------------------------------------------------

2bdb4e84325c2ec11719ec7e8ef7fbe0fc808759
 slides/buildroot-appdev/buildroot-appdev.tex | 46 ++++++++++++++--------------
 1 file changed, 23 insertions(+), 23 deletions(-)

diff --git a/slides/buildroot-appdev/buildroot-appdev.tex b/slides/buildroot-appdev/buildroot-appdev.tex
index 3373eb25..6d3d38be 100644
--- a/slides/buildroot-appdev/buildroot-appdev.tex
+++ b/slides/buildroot-appdev/buildroot-appdev.tex
@@ -2,6 +2,29 @@
 
 \section{Application development}
 
+\begin{frame}{Building during development}
+  \begin{itemize}
+  \item Buildroot is mainly a {\em final integration} tool: it is
+    aimed at downloading and building {\bf fixed} versions of software
+    components, in a reproducible way.
+  \item When doing active development of a software component, you
+    need to be able to quickly change the code, build it, and deploy
+    it on the target.
+  \item The package build directory is temporary, and removed on
+    \code{make clean}, so making changes here is not practical
+  \item Buildroot does not automatically ``update'' your source code
+    when the package is fetched from a version control system.
+  \item Three solutions:
+    \begin{itemize}
+    \item Build your software component outside of Buildroot during
+      development. Doable for software components that are easy to
+      build.
+    \item Use the \code{local} \code{SITE_METHOD} for your package
+    \item Use the \code{<pkg>_OVERRIDE_SRCDIR} mechanism
+    \end{itemize}
+  \end{itemize}
+\end{frame}
+
 \begin{frame}{Building code for Buildroot}
   \begin{itemize}
   \item The Buildroot cross-compiler is installed in
@@ -199,29 +222,6 @@ alias configure='./configure --target=arm-buildroot-linux-gnueabihf --host=arm-b
 
 \end{frame}
 
-\begin{frame}{Building during development}
-  \begin{itemize}
-  \item Buildroot is mainly a {\em final integration} tool: it is
-    aimed at downloading and building {\bf fixed} versions of software
-    components, in a reproducible way.
-  \item When doing active development of a software component, you
-    need to be able to quickly change the code, build it, and deploy
-    it on the target.
-  \item The package build directory is temporary, and removed on
-    \code{make clean}, so making changes here is not practical
-  \item Buildroot does not automatically ``update'' your source code
-    when the package is fetched from a version control system.
-  \item Three solutions:
-    \begin{itemize}
-    \item Build your software component outside of Buildroot during
-      development. Doable for software components that are easy to
-      build.
-    \item Use the \code{local} \code{SITE_METHOD} for your package
-    \item Use the \code{<pkg>_OVERRIDE_SRCDIR} mechanism
-    \end{itemize}
-  \end{itemize}
-\end{frame}
-
 \begin{frame}[fragile]{{\tt local} site method}
   \begin{itemize}
   \item Allows to tell Buildroot that the source code for a package is