[FE training-materials-updates] Replace /home/<user>/ by $HOME whenever possible
Michael Opdenacker
michael.opdenacker at free-electrons.com
Mon Dec 17 09:55:26 CET 2012
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=b61ba46cb62e6ce266252fdbfc8405a0ff8873ce
>---------------------------------------------------------------
commit b61ba46cb62e6ce266252fdbfc8405a0ff8873ce
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Mon Dec 17 09:53:44 2012 +0100
Replace /home/<user>/ by $HOME whenever possible
That's shorter and cleaner, and allows for copying and pasting
commands without having to modify them.
>---------------------------------------------------------------
b61ba46cb62e6ce266252fdbfc8405a0ff8873ce
labs/android-adb/android-adb.tex | 2 +-
labs/android-application/android-application.tex | 2 +-
labs/android-boot/android-boot.tex | 2 +-
.../android-first-compilation.tex | 2 +-
labs/android-jni-library/android-jni-library.tex | 2 +-
labs/android-native-app/android-native-app.tex | 2 +-
labs/android-new-board/android-new-board.tex | 2 +-
labs/android-source-code/android-source-code.tex | 2 +-
labs/kernel-debugging/kernel-debugging.tex | 2 +-
labs/kernel-git/kernel-git.tex | 2 +-
labs/kernel-locking/kernel-locking.tex | 2 +-
.../kernel-module-environment.tex | 2 +-
labs/kernel-module-simple/kernel-module-simple.tex | 2 +-
.../kernel-power-management.tex | 2 +-
labs/kernel-serial-driver/kernel-serial-driver.tex | 2 +-
.../kernel-serial-interrupt.tex | 2 +-
labs/kernel-serial-iomem/kernel-serial-iomem.tex | 2 +-
labs/kernel-serial-output/kernel-serial-output.tex | 2 +-
labs/kernel-sources/kernel-sources.tex | 4 +-
.../sysdev-application-debugging.tex | 2 +-
.../sysdev-application-development.tex | 4 +-
.../sysdev-block-filesystems.tex | 4 +-
labs/sysdev-buildroot/sysdev-buildroot.tex | 2 +-
.../sysdev-flash-filesystems.tex | 2 +-
.../sysdev-kernel-cross-compiling.tex | 2 +-
.../sysdev-kernel-fetch-and-patch.tex | 2 +-
labs/sysdev-real-time/sysdev-real-time.tex | 2 +-
labs/sysdev-thirdparty/sysdev-thirdparty.tex | 50 ++++++++++----------
labs/sysdev-tinysystem/sysdev-tinysystem.tex | 2 +-
labs/sysdev-toolchain/sysdev-toolchain.tex | 2 +-
labs/sysdev-u-boot/sysdev-u-boot.tex | 2 +-
.../sysdev-embedded-linux.tex | 2 +-
32 files changed, 59 insertions(+), 59 deletions(-)
diff --git a/labs/android-adb/android-adb.tex b/labs/android-adb/android-adb.tex
index 330940c..31a1e43 100644
--- a/labs/android-adb/android-adb.tex
+++ b/labs/android-adb/android-adb.tex
@@ -10,7 +10,7 @@ After this lab, you will be able to use ADB to:
\section{Setup}
-Stay in the the \code{/home/<user>/felabs/android/linaro} directory.
+Stay in the the \code{$HOME/felabs/android/linaro} directory.
\section{Get ADB}
diff --git a/labs/android-application/android-application.tex b/labs/android-application/android-application.tex
index ea8016f..f0e0c7c 100644
--- a/labs/android-application/android-application.tex
+++ b/labs/android-application/android-application.tex
@@ -9,7 +9,7 @@ After this lab, you will be able to:
\section{Write the application}
-Go to the \code{/home/<user/felabs/android/app} directory.
+Go to the \code{$HOME/felabs/android/app} directory.
You will find the basics for the \code{MissileControl} app. This app is incomplete,
parts of some activities are missing. However the UI part is
diff --git a/labs/android-boot/android-boot.tex b/labs/android-boot/android-boot.tex
index 324d52d..c9ff9ae 100644
--- a/labs/android-boot/android-boot.tex
+++ b/labs/android-boot/android-boot.tex
@@ -10,7 +10,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{/home/<user>/felabs/android/kernel} directory.
+Go to the \code{$HOME/felabs/android/kernel} directory.
\section{Compile a kernel for the Android emulator}
diff --git a/labs/android-first-compilation/android-first-compilation.tex b/labs/android-first-compilation/android-first-compilation.tex
index 4c35273..5894a7c 100644
--- a/labs/android-first-compilation/android-first-compilation.tex
+++ b/labs/android-first-compilation/android-first-compilation.tex
@@ -8,7 +8,7 @@ During this lab, you will:
\section{Setup}
-Stay in the \code{/home/<user>/felabs/android/aosp/android} directory.
+Stay in the \code{$HOME/felabs/android/aosp/android} directory.
\section{Build environment}
diff --git a/labs/android-jni-library/android-jni-library.tex b/labs/android-jni-library/android-jni-library.tex
index ec24e8b..8f3f2f6 100644
--- a/labs/android-jni-library/android-jni-library.tex
+++ b/labs/android-jni-library/android-jni-library.tex
@@ -14,7 +14,7 @@ After this lab, you will be able to
The code should be pretty close to the one you wrote in the native
application lab, so you will find a skeleton of the folder to
integrate into your product definition in the
-\code{/home/<user>/felabs/android/jni} directory. You will
+\code{$HOME/felabs/android/jni} directory. You will
mostly have to modify function prototypes from your previous
application to make it work with JNI.
diff --git a/labs/android-native-app/android-native-app.tex b/labs/android-native-app/android-native-app.tex
index 07ada57..0c98128 100644
--- a/labs/android-native-app/android-native-app.tex
+++ b/labs/android-native-app/android-native-app.tex
@@ -9,7 +9,7 @@ After this lab, you will be able to:
\section{Add the binary to the compiled image}
Copy the \code{mlbin.c} file from the
-\code{/home/<user>/felabs/android/native-app} directory and put it
+\code{$HOME/felabs/android/native-app} directory and put it
into the \code{external/ml} folder.
Just as for \code{libusb}, you now need to make an \code{Android.mk} file
diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index 9a7cf8a..54e9887 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -10,7 +10,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{/home/<user>/felabs/android/linaro} directory.
+Go to the \code{$HOME/felabs/android/linaro} directory.
Install the \code{bzr}, \code{python-argparse}, \code{python-parted}
and \code{python-yaml} packages.
diff --git a/labs/android-source-code/android-source-code.tex b/labs/android-source-code/android-source-code.tex
index c64f1a0..3c23ea8 100644
--- a/labs/android-source-code/android-source-code.tex
+++ b/labs/android-source-code/android-source-code.tex
@@ -10,7 +10,7 @@ During this labs, you will:
\section{Setup}
-Go to the \code{/home/<user>/felabs/android/aosp} directory.
+Go to the \code{$HOME/felabs/android/aosp} directory.
\section{Install needed packages}
diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index 2a5dc38..24127e9 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -59,7 +59,7 @@ that have been transmitted by your driver.
\subsection{Setup}
-Go to the \code{/home/<user>/felabs/linux/debugging} directory.
+Go to the \code{$HOME/felabs/linux/debugging} directory.
Make sure that your kernel has the following options enabled:
diff --git a/labs/kernel-git/kernel-git.tex b/labs/kernel-git/kernel-git.tex
index 6cab386..dd9f71a 100644
--- a/labs/kernel-git/kernel-git.tex
+++ b/labs/kernel-git/kernel-git.tex
@@ -13,7 +13,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to \code{/home/<user>/felabs/linux/git/}
+Go to \code{$USER/felabs/linux/git/}
This lab assumes that you already installed git software and cloned
the Linus Torvalds' git tree. See our {\em Kernel source code} lab for
diff --git a/labs/kernel-locking/kernel-locking.tex b/labs/kernel-locking/kernel-locking.tex
index 29c7b42..76c9011 100644
--- a/labs/kernel-locking/kernel-locking.tex
+++ b/labs/kernel-locking/kernel-locking.tex
@@ -9,7 +9,7 @@ During this lab, you will:
\section{Setup}
-Stay in the \code{/home/<user>/felabs/linux/character} directory.
+Stay in the \code{$HOME/felabs/linux/character} directory.
You need to have completed the previous two labs to perform this one.
diff --git a/labs/kernel-module-environment/kernel-module-environment.tex b/labs/kernel-module-environment/kernel-module-environment.tex
index 37f1990..ec68ef3 100644
--- a/labs/kernel-module-environment/kernel-module-environment.tex
+++ b/labs/kernel-module-environment/kernel-module-environment.tex
@@ -37,7 +37,7 @@ accessed through the network by the target, using NFS.
\section{Setup}
-Stay in the \code{/home/<user>/felabs/linux/modules} directory.
+Stay in the \code{$HOME/felabs/linux/modules} directory.
Install packages needed for this lab:
diff --git a/labs/kernel-module-simple/kernel-module-simple.tex b/labs/kernel-module-simple/kernel-module-simple.tex
index 1e88346..e0ea694 100644
--- a/labs/kernel-module-simple/kernel-module-simple.tex
+++ b/labs/kernel-module-simple/kernel-module-simple.tex
@@ -12,7 +12,7 @@ After this lab, you will be able to:
\section{Setup}
-Stay inside the \code{/home/<user>/felabs/linux/modules} directory.
+Stay inside the \code{$HOME/felabs/linux/modules} directory.
Boot your board again, as you did in the previous lab.
\section{Writing a module}
diff --git a/labs/kernel-power-management/kernel-power-management.tex b/labs/kernel-power-management/kernel-power-management.tex
index e0a9527..99580f3 100644
--- a/labs/kernel-power-management/kernel-power-management.tex
+++ b/labs/kernel-power-management/kernel-power-management.tex
@@ -10,7 +10,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{/home/<user>/felabs/powermgt/usage/} directory.
+Go to the \code{$HOME/felabs/powermgt/usage/} directory.
Download and extract the latest update to the Linux 3.0 kernel.
diff --git a/labs/kernel-serial-driver/kernel-serial-driver.tex b/labs/kernel-serial-driver/kernel-serial-driver.tex
index 4a2c400..934c3df 100644
--- a/labs/kernel-serial-driver/kernel-serial-driver.tex
+++ b/labs/kernel-serial-driver/kernel-serial-driver.tex
@@ -14,7 +14,7 @@ serial driver from scratch!
\section{Setup}
-Go to the \code{/home/<user>/felabs/linux/character} directory. It
+Go to the \code{$HOME/felabs/linux/character} directory. It
contains the root filesystem that you will mount over NFS to work on
this lab. Re-use the setup instructions of the lab on {\em Character
Device Drivers} to get a kernel without the serial port driver and
diff --git a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
index 3bfb925..d17f0af 100644
--- a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
+++ b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
@@ -18,7 +18,7 @@ During this lab, you will:
This lab is a continuation of the {\em Output-only character driver
lab}, so we'll re-use the code in
-\code{/home/<user>/felabs/linux/character}. Your Calao board should boot over
+\code{$HOME/felabs/linux/character}. Your Calao board should boot over
NFS and mount \code{/home/<user>/felabs/linux/character/nfsroot/} as the root
filesystem.
diff --git a/labs/kernel-serial-iomem/kernel-serial-iomem.tex b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
index 3aace47..bfe14b6 100644
--- a/labs/kernel-serial-iomem/kernel-serial-iomem.tex
+++ b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
@@ -22,7 +22,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{/home/<user>/felabs/linux/character} directory.
+Go to the \code{$HOME/felabs/linux/character} directory.
As in the {\em Module development environment} lab, we will use a the
CALAO board booted from NFS.
diff --git a/labs/kernel-serial-output/kernel-serial-output.tex b/labs/kernel-serial-output/kernel-serial-output.tex
index 78aa8f1..631e136 100644
--- a/labs/kernel-serial-output/kernel-serial-output.tex
+++ b/labs/kernel-serial-output/kernel-serial-output.tex
@@ -17,7 +17,7 @@ After this lab, you will be able to:
You must have completed the previous lab before.
-Stay in the \code{/home/<user>/felabs/linux/character} directory.
+Stay in the \code{$HOME/felabs/linux/character} directory.
\section{Major number registration}
diff --git a/labs/kernel-sources/kernel-sources.tex b/labs/kernel-sources/kernel-sources.tex
index afe861e..d4df67f 100644
--- a/labs/kernel-sources/kernel-sources.tex
+++ b/labs/kernel-sources/kernel-sources.tex
@@ -14,7 +14,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{/home/<user>/felabs/linux/modules} directory.
+Go to the \code{$HOME/felabs/linux/modules} directory.
Download and extract the Linux 3.5 kernel sources
from \url{http://kernel.org}.
@@ -76,7 +76,7 @@ First, install required software packages:
sudo apt-get install git gitk git-email
\end{verbatim}
-Then, go to the \code{/home/<user>/felabs/linux/git directory}, and run
+Then, go to the \code{$HOME/felabs/linux/git directory}, and run
the below command:
\small
diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index a2c16c0..67b7ed2 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -6,7 +6,7 @@
\section{Setup}
-Go to the \code{/home/<user>/felabs/sysdev/debugging} directory.
+Go to the \code{$HOME/felabs/sysdev/debugging} directory.
\section{Debugging setup}
diff --git a/labs/sysdev-application-development/sysdev-application-development.tex b/labs/sysdev-application-development/sysdev-application-development.tex
index e56638d..e2f7f74 100644
--- a/labs/sysdev-application-development/sysdev-application-development.tex
+++ b/labs/sysdev-application-development/sysdev-application-development.tex
@@ -3,7 +3,7 @@
\section{Setup}
-Go to the \code{/home/<user>/felabs/sysdev/appdev} directory.
+Go to the \code{$HOME/felabs/sysdev/appdev} directory.
\section{Compile your own application}
@@ -35,7 +35,7 @@ Let's add this directory to our PATH:
\footnotesize
\begin{verbatim}
-export PATH=/home/<user>/felabs/sysdev/buildroot/buildroot-XXXX.YY/output/host/usr/bin:$PATH
+export PATH=$HOME/felabs/sysdev/buildroot/buildroot-XXXX.YY/output/host/usr/bin:$PATH
\end{verbatim}
\normalsize
diff --git a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
index 5105053..6982ff1 100644
--- a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
+++ b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
@@ -18,8 +18,8 @@ this MMC card, without using NFS anymore.
\section{Setup}
-Go to \code{/home/<user>/felabs/sysdev/fs}. Reuse the kernel that you
-used in \code{/home/<user>/felabs/sysdev/tinysystem}.
+Go to \code{$HOME/felabs/sysdev/fs}. Reuse the kernel that you
+used in \code{$HOME/felabs/sysdev/tinysystem}.
Recompile it with support for SquashFS and ext3.
diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index 4b4582e..f98e278 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -5,7 +5,7 @@
\section{Setup}
-Go into the \code{/home/<user>/felabs/sysdev/buildroot/} directory,
+Go to the \code{$HOME/felabs/sysdev/buildroot/} directory,
which already contains some data needed for this lab, including a
kernel image.
diff --git a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index ee9db99..a87d611 100644
--- a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -8,7 +8,7 @@ After this lab, you will be able to:
\section{Setup}
-Stay in \code{/home/<user>/felabs/sysdev/fs}. Install the
+Stay in \code{$HOME/felabs/sysdev/fs}. Install the
\code{mtd-utils} package, which will be useful to create JFFS2
filesystem images.
diff --git a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
index 218296e..70bff99 100644
--- a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
+++ b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
@@ -11,7 +11,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{/home/<user>/felabs/sysdev/kernel} directory.
+Go to the \code{$HOME/felabs/sysdev/kernel} directory.
Install the following packages: \code{libqt4-dev} and
\code{u-boot-tools}. \code{libqt4-dev} is needed for the
diff --git a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
index c55c9e0..e47d022 100644
--- a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
+++ b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
@@ -9,7 +9,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{/home/<user>/felabs/sysdev/kernel} directory.
+Go to the \code{$HOME/felabs/sysdev/kernel} directory.
\section{Get the sources}
diff --git a/labs/sysdev-real-time/sysdev-real-time.tex b/labs/sysdev-real-time/sysdev-real-time.tex
index 5566750..91c106e 100644
--- a/labs/sysdev-real-time/sysdev-real-time.tex
+++ b/labs/sysdev-real-time/sysdev-real-time.tex
@@ -13,7 +13,7 @@ POSIX real-time API, and against Xenomai's POSIX skin.
\section{Setup}
-Go to the \code{/home/<user>/felabs/realtime/rttest} directory.
+Go to the \code{$HOME/felabs/realtime/rttest} directory.
Install the \code{netcat} package.
diff --git a/labs/sysdev-thirdparty/sysdev-thirdparty.tex b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
index 989df19..1c3b1da 100644
--- a/labs/sysdev-thirdparty/sysdev-thirdparty.tex
+++ b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
@@ -79,7 +79,7 @@ To sum up, the {\em staging} space will contain everything that's
needed for compilation, while the {\em target} space will contain only
what's needed for execution.
-So, in \code{/home/<user>/felabs/sysdev/thirdparty}, create two
+So, in \code{$HOME/felabs/sysdev/thirdparty}, create two
directories: \code{staging} and \code{target}.
For the target, we need a basic system with BusyBox, device nodes and
@@ -88,7 +88,7 @@ initialization scripts. We will re-use the system built in the {\em A
directory:
\begin{verbatim}
-sudo cp -a /home/<user>/felabs/sysdev/tinysystem/nfsroot/* target/
+sudo cp -a $HOME/felabs/sysdev/tinysystem/nfsroot/* target/
\end{verbatim}
The copy must be done as \code{root}, because the root filesystem of
@@ -122,7 +122,7 @@ The system should boot and give you a prompt.
\code{Zlib} is a compression/decompression library available at
\url{http://www.zlib.net/}. Download version 1.2.5, and extract it in
-\code{/home/<user>/felabs/sysdev/thirdparty/}.
+\code{$HOME/felabs/sysdev/thirdparty/}.
By looking at the \code{configure} script, we see that this configure
script has not been generated by \code{autoconf} (otherwise it would
@@ -258,12 +258,12 @@ Do not confuse the {\em prefix} (where the application or library will
be running on the target system) from the location where the
application or library will be installed on your host while building
the root filesystem. For example, zlib will be installed in
-\code{/home/<user>/felabs/sysdev/thirdparty/target/usr/lib/} because
+\code{$HOME/felabs/sysdev/thirdparty/target/usr/lib/} because
this is the directory where we are building the root filesystem, but
once our target system will be running, it will see zlib in
\code{/usr/lib}. The prefix corresponds to the path in the target
system and {\bf never} on the host. So, one should {\bf never} pass a
-prefix like \code{/home/<user>/felabs/sysdev/thirdparty/target/usr},
+prefix like \code{$HOME/felabs/sysdev/thirdparty/target/usr},
otherwise at runtime, the application or library may look for files
inside this directory on the target system, which obviously doesn't
exist! By default, most build systems will install the application or
@@ -408,7 +408,7 @@ configure script:
Let's use this \code{LDFLAGS} variable:
\begin{verbatim}
-LDFLAGS=-L/home/<user>/felabs/sysdev/thirdparty/staging/usr/lib \
+LDFLAGS=-L$HOME/felabs/sysdev/thirdparty/staging/usr/lib \
CC=arm-linux-gcc \
./configure --host=arm-linux
\end{verbatim}
@@ -417,7 +417,7 @@ Let's also specify the prefix, so that the library is compiled to be
installed in \code{/usr} and not \code{/usr/local}:
\begin{verbatim}
- LDFLAGS=-L/home/<user>/felabs/sysdev/thirdparty/staging/usr/lib \
+ LDFLAGS=-L$HOME/felabs/sysdev/thirdparty/staging/usr/lib \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -445,8 +445,8 @@ can be found: there are not in the default directory
Let's use it:
\begin{verbatim}
-LDFLAGS=-L/home/<user>/felabs/sysdev/thirdparty/staging/usr/lib \
-CPPFLAGS=-I/home/<user>/felabs/sysdev/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/felabs/sysdev/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/felabs/sysdev/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -564,7 +564,7 @@ So, we have:
Now, let's make the installation in the {\em staging} space:
\begin{verbatim}
-make DESTDIR=/home/<user>/felabs/sysdev/thirdparty/staging/ install
+make DESTDIR=$HOME/felabs/sysdev/thirdparty/staging/ install
\end{verbatim}
Then, let's install only the necessary files in the {\em target}
@@ -601,7 +601,7 @@ Installation to the {\em staging} space can be done using the
classical \code{DESTDIR} mechanism:
\begin{verbatim}
-make DESTDIR=/home/<user>/felabs/sysdev/thirdparty/staging/ install
+make DESTDIR=$HOME/felabs/sysdev/thirdparty/staging/ install
\end{verbatim}
And finally, install manually the only needed files at runtime in the
@@ -639,7 +639,7 @@ make
Install it in the {\em staging} space:
\begin{verbatim}
-make DESTDIR=/home/<user>/felabs/sysdev/thirdparty/staging/ install
+make DESTDIR=$HOME/felabs/sysdev/thirdparty/staging/ install
\end{verbatim}
And install only the required files in the {\em target} space:
@@ -708,8 +708,8 @@ are. So let's configure again with:
\small
\begin{verbatim}
-LDFLAGS=-L/home/<user>/felabs/sysdev/thirdparty/staging/usr/lib \
-CPPFLAGS=-I/home/<user>/felabs/sysdev/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/felabs/sysdev/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/felabs/sysdev/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr \
--with-gfxdrivers=none --with-inputdrivers=keyboard,linuxinput
@@ -754,7 +754,7 @@ explained in the manual page of \code{pkg-config}.
Moreover, the \code{.pc} files contain references to paths. For
example, in
-\code{/home/<user>/felabs/sysdev/thirdparty/staging/usr/lib/pkgconfig/freetype2.pc},
+\code{$HOME/felabs/sysdev/thirdparty/staging/usr/lib/pkgconfig/freetype2.pc},
we can see:
\begin{verbatim}
@@ -777,10 +777,10 @@ variables:
\small
\begin{verbatim}
-LDFLAGS=-L/home/<user>/felabs/sysdev/thirdparty/staging/usr/lib \
-CPPFLAGS=-I/home/<user>/felabs/sysdev/thirdparty/staging/usr/include \
-PKG_CONFIG_PATH=/home/<user>/felabs/sysdev/thirdparty/staging/usr/lib/pkgconfig \
-PKG_CONFIG_SYSROOT_DIR=/home/<user>/felabs/sysdev/thirdparty/staging \
+LDFLAGS=-L$HOME/felabs/sysdev/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/felabs/sysdev/thirdparty/staging/usr/include \
+PKG_CONFIG_PATH=$HOME/felabs/sysdev/thirdparty/staging/usr/lib/pkgconfig \
+PKG_CONFIG_SYSROOT_DIR=$HOME/felabs/sysdev/thirdparty/staging \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr \
--with-gfxdrivers=none --with-inputdrivers=keyboard,linuxinput
@@ -841,7 +841,7 @@ Finally, it builds!
Now, install DirectFB to the {\em staging} space using:
\begin{verbatim}
-make DESTDIR=/home/<user>/felabs/sysdev/thirdparty/staging/ install
+make DESTDIR=$HOME/felabs/sysdev/thirdparty/staging/ install
\end{verbatim}
And so the installation in the {\em target} space:
@@ -888,10 +888,10 @@ Then, we configure it just as we configured DirectFB:
\small
\begin{verbatim}
-LDFLAGS=-L/home/<user>/felabs/sysdev/thirdparty/staging/usr/lib \
-CPPFLAGS=-I/home/<user>/felabs/sysdev/thirdparty/staging/usr/include \
-PKG_CONFIG_PATH=/home/<user>/felabs/sysdev/thirdparty/staging/usr/lib/pkgconfig \
-PKG_CONFIG_SYSROOT_DIR=/home/<user>/felabs/sysdev/thirdparty/staging \
+LDFLAGS=-L$HOME/felabs/sysdev/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/felabs/sysdev/thirdparty/staging/usr/include \
+PKG_CONFIG_PATH=$HOME/felabs/sysdev/thirdparty/staging/usr/lib/pkgconfig \
+PKG_CONFIG_SYSROOT_DIR=$HOME/felabs/sysdev/thirdparty/staging \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -928,7 +928,7 @@ variable):
\begin{verbatim}
make STRIP=arm-linux-strip \
- DESTDIR=/home/<user>/felabs/sysdev/thirdparty/target/ install-strip
+ DESTDIR=$HOME/felabs/sysdev/thirdparty/target/ install-strip
\end{verbatim}
\section{Final setup}
diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index 99f043d..a4856b9 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -35,7 +35,7 @@ target to test the impact of script or application updates.
\section{Setup}
-Go to the \code{/home/<user>/felabs/sysdev/tinysystem/} directory.
+Go to the \code{$HOME/felabs/sysdev/tinysystem/} directory.
\section{Kernel configuration}
diff --git a/labs/sysdev-toolchain/sysdev-toolchain.tex b/labs/sysdev-toolchain/sysdev-toolchain.tex
index 1f7e715..21caf17 100644
--- a/labs/sysdev-toolchain/sysdev-toolchain.tex
+++ b/labs/sysdev-toolchain/sysdev-toolchain.tex
@@ -11,7 +11,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{/home/<user>/felabs/sysdev/toolchain} directory.
+Go to the \code{$HOME/felabs/sysdev/toolchain} directory.
Make sure you have at least 2 GB of free disk space.
diff --git a/labs/sysdev-u-boot/sysdev-u-boot.tex b/labs/sysdev-u-boot/sysdev-u-boot.tex
index 00de3b2..acc1951 100644
--- a/labs/sysdev-u-boot/sysdev-u-boot.tex
+++ b/labs/sysdev-u-boot/sysdev-u-boot.tex
@@ -28,7 +28,7 @@ start up a OMAP3-based board without having anything installed on it.
\section{Setup}
-Go to the \code{/home/<user>/felabs/sysdev/u-boot/} directory.
+Go to the \code{$HOME/felabs/sysdev/u-boot/} directory.
\section{MMC/SD card setup}
diff --git a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
index 8ffd204..4fdf09e 100644
--- a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
+++ b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
@@ -1272,7 +1272,7 @@ export CC=arm-linux-gcc
export STRIP=arm-linux-strip
./configure --host=arm-linux --prefix=/usr
make
-make DESTDIR=/home/<user>/work/rootfs install
+make DESTDIR=$HOME/work/rootfs install
\end{verbatim}
\end{block}
\end{itemize}
More information about the training-materials-updates
mailing list