[bootlin/training-materials updates] master: yocto: slides: move varflags slide before varflags are used (almost) (7d987399)

[Luca Ceresoli]

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

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

commit 7d987399ef7e2a637c7f5b27dde78b0ecde57a3e
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Wed Aug 17 12:23:58 2022 +0200

    yocto: slides: move varflags slide before varflags are used (almost)
    
    Explaining PACKAGECONFIG is quite hard, not only because it is an advanced
    topic, but also because it is heavily based on varflags, which are
    introduced later on.
    
    Move the "Variable flags" subsection before PACKAGECONFIG (still within the
    "Writing recipes - going further" section).
    
    Also move yocto-licensing after yocto-recipe-extra as it uses varflags too,
    and there is no cross-dependency between those two sections.
    
    According to my search, there is no other use of varflags in the slides
    except for SRC_URI[*sum], but let's keep it as is: SRC_URI is such a basic
    variable that it's not possible to move it late in the slides, and moving
    varflags earlier than that would anticipate a slightly complex topic for no
    reason.
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

7d987399ef7e2a637c7f5b27dde78b0ecde57a3e
 mk/yocto-stm32.mk                                |  2 +-
 mk/yocto.mk                                      |  2 +-
 slides/yocto-recipe-extra/yocto-recipe-extra.tex | 54 ++++++++++++------------
 3 files changed, 29 insertions(+), 29 deletions(-)

diff --git a/mk/yocto-stm32.mk b/mk/yocto-stm32.mk
index 8ac937d6..92b05fa3 100644
--- a/mk/yocto-stm32.mk
+++ b/mk/yocto-stm32.mk
@@ -23,8 +23,8 @@ YOCTO_STM32_SLIDES    = \
 		yocto-layer-distro \
 		yocto-image \
 		yocto-image-lab \
-		yocto-licensing \
 		yocto-recipe-extra \
+		yocto-licensing \
 		yocto-sdk \
 		yocto-sdk-lab \
 		yocto-runtime-package-management \
diff --git a/mk/yocto.mk b/mk/yocto.mk
index dd0da9f1..fe10a8e9 100644
--- a/mk/yocto.mk
+++ b/mk/yocto.mk
@@ -23,8 +23,8 @@ YOCTO_SLIDES    = \
 		yocto-layer-distro \
 		yocto-image \
 		yocto-image-lab \
-		yocto-licensing \
 		yocto-recipe-extra \
+		yocto-licensing \
 		yocto-sdk \
 		yocto-sdk-lab \
 		yocto-runtime-package-management \
diff --git a/slides/yocto-recipe-extra/yocto-recipe-extra.tex b/slides/yocto-recipe-extra/yocto-recipe-extra.tex
index c4cec89e..d95a47e4 100644
--- a/slides/yocto-recipe-extra/yocto-recipe-extra.tex
+++ b/slides/yocto-recipe-extra/yocto-recipe-extra.tex
@@ -1,5 +1,32 @@
 \section{Writing recipes - going further}
 
+\subsection{Variable flags}
+
+\begin{frame}[fragile]
+  \frametitle{Variable flags}
+  \begin{itemize}
+    \item {\em Variable flags} are used to store extra information on
+      tasks and variables.
+    \item They are used to control task functionalities.
+    \item A number of these flags are already used by BitBake:
+      \begin{itemize}
+        \item \code{dirs}: directories that should be created before the
+          task runs. The last one becomes the work directory for the
+          task.
+        \item \code{noexec}: disable the execution of the task.
+        \item \code{nostamp}: do not create a {\em stamp} file when
+          running the task. The task will always be executed.
+        \item \code{doc}: task documentation displayed by {\em
+          listtasks}.
+      \end{itemize}
+  \end{itemize}
+  \begin{minted}{sh}
+do_settime[noexec] = "1"
+do_compile[nostamp] = "1"
+do_settime[doc] = "Set the current time in ${TIME}"
+  \end{minted}
+\end{frame}
+
 \subsection{Packages features}
 
 \begin{frame}
@@ -140,33 +167,6 @@ python do_settime() {
   \end{minted}
 \end{frame}
 
-\subsection{Variable flags}
-
-\begin{frame}[fragile]
-  \frametitle{Variable flags}
-  \begin{itemize}
-    \item {\em Variable flags} are used to store extra information on
-      tasks and variables.
-    \item They are used to control task functionalities.
-    \item A number of these flags are already used by BitBake:
-      \begin{itemize}
-        \item \code{dirs}: directories that should be created before the
-          task runs. The last one becomes the work directory for the
-          task.
-        \item \code{noexec}: disable the execution of the task.
-        \item \code{nostamp}: do not create a {\em stamp} file when
-          running the task. The task will always be executed.
-        \item \code{doc}: task documentation displayed by {\em
-          listtasks}.
-      \end{itemize}
-  \end{itemize}
-  \begin{minted}{sh}
-do_settime[noexec] = "1"
-do_compile[nostamp] = "1"
-do_settime[doc] = "Set the current time in ${TIME}"
-  \end{minted}
-\end{frame}
-
 \subsection{Root filesystem creation}
 
 \begin{frame}[fragile]