[FE training-materials-updates] labs/sysdev-application-debugging: don't copy the entire Buildroot

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Thu Apr 6 17:08:31 CEST 2017

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=5b7b995b62ffbfbe7f3ea18729c38428afd9e7b8


commit 5b7b995b62ffbfbe7f3ea18729c38428afd9e7b8
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Thu Apr 6 17:08:31 2017 +0200

    labs/sysdev-application-debugging: don't copy the entire Buildroot
    Copying the entire Buildroot folder with all the build output and then
    cleaning it up is really silly. Ideally, we should have people use out
    of tree build, but that's probably a bit too confusing for a sysdev
    toolchain aimed at beginners.
    So instead, ask participants to re-extract the Buildroot source code,
    and copy the Buildroot configuration from the previous build.
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


 .../sysdev-application-debugging.tex               | 27 ++++++++++------------
 1 file changed, 12 insertions(+), 15 deletions(-)

diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index 92d1dd2..9229798 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -9,21 +9,18 @@ Create an \code{nfsroot} directory.
 \section{Debugging setup}
-Reuse the Buildroot 2016.02 sources:
-cp -a $HOME/embedded-linux-labs/buildroot/buildroot-2016.02 .
-Instead of using the toolchain we compiled, we are going to use an
-external toolchain from Linaro. Indeed gdb is buggy when built with
-the toolchain we created: it uses a too old version of uClibc.
-From the directory
-cleanup the binaries:
-make clean
-then configure buildroot with the following modification:
+For this lab, we will create a separate Buildroot build, with a
+slightly different configuration. Indeed, we want to use a different
+toolchain as the toolchain produced by Crosstool-NG currently has a
+non-functional {\em gdb}. And also because experimenting with multiple
+toolchains is good!
+Extract the Buildroot source code again from its tarball into
+\code{$HOME/embedded-linux-labs/debugging}. Then, copy the
+configuration of the previous Buildroot build (\code{.config} file)
+into the new Buildroot source directory.
+Then, in \code{menuconfig}, adjust the configuration as follows:
 \item In \code{Toolchain}:

More information about the training-materials-updates mailing list