[bootlin/training-materials updates] master: labs/buildroot: use correct path to labs directory (d931fe3a)

Thomas Petazzoni thomas.petazzoni at bootlin.com
Fri Apr 3 11:46:37 CEST 2020

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


commit d931fe3aa78108bd4a6d4197716f78feeb0082ee
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Fri Apr 3 11:46:37 2020 +0200

    labs/buildroot: use correct path to labs directory
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


 labs/buildroot-advanced/buildroot-advanced.tex | 8 ++++----
 labs/buildroot-appdev/buildroot-appdev.tex     | 6 +++---
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/labs/buildroot-advanced/buildroot-advanced.tex b/labs/buildroot-advanced/buildroot-advanced.tex
index d2b49e69..4d4a7a1b 100644
--- a/labs/buildroot-advanced/buildroot-advanced.tex
+++ b/labs/buildroot-advanced/buildroot-advanced.tex
@@ -73,8 +73,8 @@ Now, let's draw a graph for a much bigger system. To do this, create a
 completely separate Buildroot output directory:
-mkdir $HOME/felabs/buildroot-output-test-graph/
-cd $HOME/felabs/buildroot-output-test-graph/
+mkdir $HOME/__SESSION_NAME__-labs/buildroot-output-test-graph/
+cd $HOME/__SESSION_NAME__-labs/buildroot-output-test-graph/
 We're going to create a Buildroot configuration, so create a file
@@ -103,7 +103,7 @@ First, let's run \code{make menuconfig} to expand this minimal
 configuration into a full configuration:
-make -C $HOME/felabs/buildroot/ O=$(pwd) menuconfig
+make -C $HOME/__SESSION_NAME__-labs/buildroot/ O=$(pwd) menuconfig
 Feel free to explore the configuration at this stage. Now, let's
@@ -138,7 +138,7 @@ files generated in \code{output/graphs/}.
 \section{Licensing report}
 Go back to our original build directory, in
 As explained during the lectures, Buildroot has a built-in mechanism
 to generate a licensing report, describing all the components part of
diff --git a/labs/buildroot-appdev/buildroot-appdev.tex b/labs/buildroot-appdev/buildroot-appdev.tex
index 360121f5..d9521546 100644
--- a/labs/buildroot-appdev/buildroot-appdev.tex
+++ b/labs/buildroot-appdev/buildroot-appdev.tex
@@ -11,7 +11,7 @@
 \section{Build and run your own application}
 Let's create your own little application that we will use for
-demonstration in this lab. Create a folder \code{$HOME/felabs/myapp},
+demonstration in this lab. Create a folder \code{$HOME/__SESSION_NAME__-labs/myapp},
 and inside this folder a single C file called \code{myapp.c} with the
 following contents:
@@ -29,7 +29,7 @@ Buildroot. To make this easy, let's add the Buildroot host directory
 into our PATH:
-export PATH=$HOME/felabs/buildroot/output/host/bin:$PATH
+export PATH=$HOME/__SESSION_NAME__-labs/buildroot/output/host/bin:$PATH
 Now you can build your application easily:
@@ -202,7 +202,7 @@ code of your application is available locally.
 Create a new package called \code{myapp} in your \code{BR2_EXTERNAL}
 tree, and by using the \code{local} {\em site method}, make it use
 directly the \code{myapp} source code from
-\code{$HOME/felabs/myapp}. Remember that you can use \code{$(TOPDIR)}
+\code{$HOME/__SESSION_NAME__-labs/myapp}. Remember that you can use \code{$(TOPDIR)}
 to reference the top-level directory of the Buildroot sources.
 For now, directly call \code{gcc} in the build commands. Of course, if

More information about the training-materials-updates mailing list