[bootlin/training-materials updates] master: yocto: slides: upgrade to kirkstone (368b824e)

Luca Ceresoli luca.ceresoli at bootlin.com
Thu Jul 14 11:48:28 CEST 2022


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

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

commit 368b824ec162aae437774d42278594b5cbb7301c
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Wed Jul 13 03:03:29 2022 +0200

    yocto: slides: upgrade to kirkstone
    
    Upgrade the slides to focus on the Yocto kirkstone release.
    
    Main changes:
    
     * Document the ':' syntax for overrides, but keep a note of the old syntax
       for reference
     * Use ':' for overrides in variable assignments
     * Use ':' for overrides in 'bitbake -e' output
     * Mention kirkstone in examples
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

368b824ec162aae437774d42278594b5cbb7301c
 slides/yocto-advanced/yocto-advanced.tex           | 27 +++++++++++-----------
 slides/yocto-bsp/yocto-bsp.tex                     |  2 +-
 slides/yocto-image/yocto-image.tex                 |  2 +-
 slides/yocto-layer-distro/yocto-layer-distro.tex   | 10 ++++----
 slides/yocto-overview/yocto-overview.tex           |  4 ++--
 .../yocto-recipe-advanced.tex                      |  6 ++---
 slides/yocto-recipe-basics/yocto-recipe-basics.tex |  8 +++----
 slides/yocto-recipe-extra/yocto-recipe-extra.tex   | 12 +++++-----
 8 files changed, 35 insertions(+), 36 deletions(-)

diff --git a/slides/yocto-advanced/yocto-advanced.tex b/slides/yocto-advanced/yocto-advanced.tex
index 99b5c225..b9d7e7bd 100644
--- a/slides/yocto-advanced/yocto-advanced.tex
+++ b/slides/yocto-advanced/yocto-advanced.tex
@@ -58,26 +58,25 @@
   \item Bitbake supports \textbf{overrides}, to allow appending,
     prepending or modifying a variable at expansion time, when
     the variable's value is read
-  \item Overrides are written as \code{VARIABLE_override = "some_value"}
-  \item A new syntax was introduced in bitbake: \code{VARIABLE:override = "some_value"}
-  \item It will be the new syntax to be used starting with \textbf{Honister}, with no retrocompatibility
+  \item Overrides are written as \code{VARIABLE:override = "some_value"}
+  \item A different syntax was used before \textbf{Honister}, with no retrocompatibility: \code{VARIABLE_override = "some_value"}
   \end{itemize}
 \end{frame}
 
 \begin{frame}
   \frametitle{Methods and conditions 1/4}
   \begin{itemize}
-    \item Append the keyword \code{_append} to a configuration
+    \item Append the keyword \code{:append} to a configuration
       variable to add values {\bf after} the ones previously defined
       (without space).
       \begin{itemize}
-        \item \code{IMAGE_INSTALL_append = " dropbear"} adds
+        \item \code{IMAGE_INSTALL:append = " dropbear"} adds
           \code{dropbear} to the packages installed on the image.
       \end{itemize}
-    \item Append the keyword \code{_prepend} to add values {\bf
+    \item Append the keyword \code{:prepend} to add values {\bf
       before} the ones previously defined (without space).
       \begin{itemize}
-        \item \code{FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"}
+        \item \code{FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"}
           %stopzone
           adds the folder to the set of paths where files are located
           (in a recipe).
@@ -88,18 +87,18 @@
 \begin{frame}
   \frametitle{Methods and conditions 2/4}
   \begin{itemize}
-    \item Append the keyword \code{_remove} to a configuration
+    \item Append the keyword \code{:remove} to a configuration
       variable to remove all occurrences of a value within a
       configuration variable.
       \begin{itemize}
-        \item \code{IMAGE_INSTALL_remove = "i2c-tools"}
+        \item \code{IMAGE_INSTALL:remove = "i2c-tools"}
       \end{itemize}
     \item Append the machine name to only define a configuration
       variable for a given machine. It tries to match with values from
       \code{MACHINEOVERRIDES} which include \code{MACHINE} and
       \code{SOC_FAMILY}.
       \begin{itemize}
-        \item \code{KERNEL_DEVICETREE_beaglebone = "am335x-bone.dtb"}
+        \item \code{KERNEL_DEVICETREE:beaglebone = "am335x-bone.dtb"}
           tells to use the kernel device tree \code{am335x-bone.dtb}
           only when the machine is \code{beaglebone}.
       \end{itemize}
@@ -113,8 +112,8 @@
     \item If we define:
       \begin{itemize}
         \item \code{IMAGE_INSTALL = "busybox mtd-utils"}
-        \item \code{IMAGE_INSTALL_append = " dropbear"}
-        \item \code{IMAGE_INSTALL_append_beaglebone = " i2c-tools"}
+        \item \code{IMAGE_INSTALL:append = " dropbear"}
+        \item \code{IMAGE_INSTALL:append:beaglebone = " i2c-tools"}
       \end{itemize}
     \item The resulting configuration variable will be:
       \begin{itemize}
@@ -133,7 +132,7 @@
     \item The most specific variable takes precedence.
     \item Example:
       \begin{minted}[fontsize=\footnotesize]{console}
-IMAGE_INSTALL_beaglebone = "busybox mtd-utils i2c-tools"
+IMAGE_INSTALL:beaglebone = "busybox mtd-utils i2c-tools"
 IMAGE_INSTALL = "busybox mtd-utils"
       \end{minted}
     \item If the machine is \code{beaglebone}:
@@ -173,7 +172,7 @@ IMAGE_INSTALL = "busybox mtd-utils"
       \begin{itemize}
         \item If \code{+=} is parsed before \code{?=}, the latter will
           be discarded.
-        \item Using \code{_append} unconditionally appends the value.
+        \item Using \code{:append} unconditionally appends the value.
       \end{itemize}
   \end{itemize}
 \end{frame}
diff --git a/slides/yocto-bsp/yocto-bsp.tex b/slides/yocto-bsp/yocto-bsp.tex
index fa3b87dd..e8ee986e 100644
--- a/slides/yocto-bsp/yocto-bsp.tex
+++ b/slides/yocto-bsp/yocto-bsp.tex
@@ -122,7 +122,7 @@ IMXBOOTLETS_MACHINE = "cfa10036"
 KERNEL_IMAGETYPE = "zImage"
 KERNEL_DEVICETREE = "imx28-cfa10036.dtb"
 # we need the kernel to be installed in the final image
-IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
+IMAGE_INSTALL:append = " kernel-image kernel-devicetree"
 SDCARD_ROOTFS ?= "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.ext3"
 SERIAL_CONSOLE = "115200 ttyAMA0"
 MACHINE_FEATURES = "usbgadget usbhost vfat"
diff --git a/slides/yocto-image/yocto-image.tex b/slides/yocto-image/yocto-image.tex
index 56872e3b..245a2f60 100644
--- a/slides/yocto-image/yocto-image.tex
+++ b/slides/yocto-image/yocto-image.tex
@@ -215,7 +215,7 @@ LICENSE = "MIT"
 
 inherit packagegroup
 
-RDEPENDS_${PN} = "\
+RDEPENDS:${PN} = "\
     gdb \
     gdbserver \
     strace"
diff --git a/slides/yocto-layer-distro/yocto-layer-distro.tex b/slides/yocto-layer-distro/yocto-layer-distro.tex
index e5186558..f5f14784 100644
--- a/slides/yocto-layer-distro/yocto-layer-distro.tex
+++ b/slides/yocto-layer-distro/yocto-layer-distro.tex
@@ -157,7 +157,7 @@ MAINTAINER = "..."
   <remote name="yocto-project" fetch="git.yoctoproject.org" />
   <remote name="private" fetch="git.example.net" />
 
-  <default revision="dunfell" remote="private" />
+  <default revision="kirkstone" remote="private" />
 
   <project name="poky" remote="yocto-project" />
   <project name="meta-ti" remote="yocto-project" />
@@ -226,13 +226,13 @@ repos:
 
   bitbake:
     url: "https://git.openembedded.org/bitbake"
-    refspec: "1.46"
+    refspec: "2.0"
     layers:
       .: excluded
 
   openembedded-core:
     url: "https://git.openembedded.org/openembedded-core"
-    refspec: dunfell
+    refspec: kirkstone
     layers:
       meta:
   \end{minted}
@@ -246,11 +246,11 @@ repos:
   \begin{minted}{yaml}
   meta-freescale:
     url: "https://github.com/Freescale/meta-freescale"
-    refspec: dunfell
+    refspec: kirkstone
 
   meta-openembedded:
    url: https://git.openembedded.org/meta-openembedded
-   refspec: dunfell
+   refspec: kirkstone
    layers:
      meta-oe:
      meta-python:
diff --git a/slides/yocto-overview/yocto-overview.tex b/slides/yocto-overview/yocto-overview.tex
index 6ee54b15..3922869e 100644
--- a/slides/yocto-overview/yocto-overview.tex
+++ b/slides/yocto-overview/yocto-overview.tex
@@ -98,9 +98,9 @@
           available at \url{https://git.yoctoproject.org/cgit/}
     \item To download the Poky reference system: \\
           {\small
-          \code{git clone -b dunfell https://git.yoctoproject.org/git/poky}
+          \code{git clone -b kirkstone https://git.yoctoproject.org/git/poky}
           }
-    \item Each release has a codename such as \code{dunfell} or \code{hardknott},
+    \item Each release has a codename such as \code{kirkstone} or \code{honister},
 	  corresponding to a release number.
 		  \begin{itemize}
 			  \item A summary can be found at \url{https://wiki.yoctoproject.org/wiki/Releases}
diff --git a/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex b/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex
index df9ffb5b..c49f5d6d 100644
--- a/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex
+++ b/slides/yocto-recipe-advanced/yocto-recipe-advanced.tex
@@ -61,7 +61,7 @@
   \frametitle{Hello world append file}
   \begin{block}{}
     \begin{minted}{sh}
-FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
+FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
 
 SRC_URI += "file://custom-modification-0.patch \
             file://custom-modification-1.patch \
@@ -339,7 +339,7 @@ $ bitbake -e ninvaders
 #     ""
 #   set /yocto-labs/poky/meta/conf/documentation.conf:130
 #     [doc] "Lists a recipe's build-time dependencies (i.e. other recipe files)."
-#   _prepend /yocto-training/yocto-labs/poky/meta/classes/base.bbclass:74
+#   :prepend /yocto-training/yocto-labs/poky/meta/classes/base.bbclass:74
 #     "${BASEDEPENDS} "
 #   set /yocto-labs/meta-bootlinlabs/recipes-games/ninvaders/ninvaders.inc:11
 #     "ncurses"
@@ -425,7 +425,7 @@ https://.*/.* http://downloads.yoctoproject.org/mirror/sources/ \n"
   \end{itemize}
   \begin{block}{}
     \begin{minted}{sh}
-PREMIRRORS_prepend = "\
+PREMIRRORS:prepend = "\
  git://.*/.* http://www.yoctoproject.org/sources/   \n \
  ftp://.*/.* http://www.yoctoproject.org/sources/   \n \
  http://.*/.* http://www.yoctoproject.org/sources/  \n \
diff --git a/slides/yocto-recipe-basics/yocto-recipe-basics.tex b/slides/yocto-recipe-basics/yocto-recipe-basics.tex
index 521aeae8..116cc3d7 100644
--- a/slides/yocto-recipe-basics/yocto-recipe-basics.tex
+++ b/slides/yocto-recipe-basics/yocto-recipe-basics.tex
@@ -250,7 +250,7 @@ LIC_FILES_CHKSUM =  \
     \end{description}
     \item \code{DEPENDS = "recipe-b"}: the local \code{do_configure}
       task depends on the \code{do_populate_sysroot} task of recipe-b.
-    \item \code{RDEPENDS_${PN} = "recipe-b"}: the local
+    \item \code{RDEPENDS:${PN} = "recipe-b"}: the local
       \code{do_build} task depends on the
       \code{do_package_write_<archive-format>} task of recipe b.
   \end{itemize}
@@ -264,7 +264,7 @@ LIC_FILES_CHKSUM =  \
     \item BitBake allows to reflect this by using:
     \begin{itemize}
       \item \code{DEPENDS = "recipe-b (>= 1.2)"}
-      \item \code{RDEPENDS_${PN} = "recipe-b (>= 1.2)"}
+      \item \code{RDEPENDS:${PN} = "recipe-b (>= 1.2)"}
     \end{itemize}
     \item The following operators are supported: \code{=}, \code{>},
       \code{<}, \code{>=} and \code{<=}.
@@ -340,10 +340,10 @@ do_install() {
 
 \begin{frame}[fragile]
   \frametitle{Modifying existing tasks}
-  Tasks can be extended with \code{_prepend} or \code{_append}
+  Tasks can be extended with \code{:prepend} or \code{:append}
   \begin{block}{}
     \begin{minted}{sh}
-do_install_append() {
+do_install:append() {
     install -d ${D}${sysconfdir}
     install -m 0644 hello.conf ${D}${sysconfdir}
 }
diff --git a/slides/yocto-recipe-extra/yocto-recipe-extra.tex b/slides/yocto-recipe-extra/yocto-recipe-extra.tex
index d042362c..c4cec89e 100644
--- a/slides/yocto-recipe-extra/yocto-recipe-extra.tex
+++ b/slides/yocto-recipe-extra/yocto-recipe-extra.tex
@@ -174,12 +174,12 @@ do_settime[doc] = "Set the current time in ${TIME}"
   \begin{itemize}
     \item The \code{FILES} variable controls the list of files and
       directories to be placed into packages.
-    \item It must be package specific (e.g. with \code{_${PN}}).
+    \item It must be package specific (e.g. with \code{:${PN}}).
     \item In Poky, defaults to:
   \end{itemize}
   \begin{block}{}
     \begin{minted}[fontsize=\scriptsize]{sh}
-FILES_${PN} = \
+FILES:${PN} = \
     "${bindir}/* ${sbindir}/* ${libexecdir}/* ${libdir}/lib*${SOLIBS} \
      ${sysconfdir} ${sharedstatedir} ${localstatedir} \
      ${base_bindir}/* ${base_sbindir}/* \
@@ -272,8 +272,8 @@ SRC_URI[sha256sum] = "..."
 
 PACKAGES =+ "kexec kdump"
 
-FILES_kexec = "${sbindir}/kexec"
-FILES_kdump = "${sbindir}/kdump"
+FILES:kexec = "${sbindir}/kexec"
+FILES:kdump = "${sbindir}/kdump"
     \end{minted}
     \end{block}
   \end{itemize}
@@ -293,13 +293,13 @@ PACKAGES = "${PN}-src ${PN}-dbg ${PN}-staticdev ${PN}-dev \
       defined in \code{meta/conf/bitbake.conf}:
     \begin{block}{}
     \begin{minted}[fontsize=\small]{sh}
-FILES_${PN}-dev = \
+FILES:${PN}-dev = \
     "${includedir} ${FILES_SOLIBSDEV} ${libdir}/*.la \
      ${libdir}/*.o ${libdir}/pkgconfig ${datadir}/pkgconfig \
      ${datadir}/aclocal ${base_libdir}/*.o \
      ${libdir}/${BPN}/*.la ${base_libdir}/*.la \
      ${libdir}/cmake ${datadir}/cmake"
-FILES_${PN}-dbg = \
+FILES:${PN}-dbg = \
     "/usr/lib/debug /usr/lib/debug-static \
      /usr/src/debug"
     \end{minted}




More information about the training-materials-updates mailing list