[FE training-materials-updates] labs/autotools: don't use a $HOME/autotools-labs directory

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Fri May 22 16:47:04 CEST 2015

Repository : git://git.free-electrons.com/training-materials.git

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


commit f529e272d77a10ba9242ad6707eb888ba7b005b8
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Fri May 22 16:46:23 2015 +0200

    labs/autotools: don't use a $HOME/autotools-labs directory
    We won't provide a tarball with data for this training.
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


 labs/autotools-basics/autotools-basics.tex |  5 +++--
 labs/autotools-usage/autotools-usage.tex   | 17 +++++++++--------
 2 files changed, 12 insertions(+), 10 deletions(-)

diff --git a/labs/autotools-basics/autotools-basics.tex b/labs/autotools-basics/autotools-basics.tex
index 98494dd..3a704ed 100644
--- a/labs/autotools-basics/autotools-basics.tex
+++ b/labs/autotools-basics/autotools-basics.tex
@@ -10,8 +10,9 @@
 \section{Create your first {\tt configure.ac}}
-In \code{$HOME/autotools-labs/basics/}, create a new folder
-\code{project} for your first {\em autotools} project.
+In \code{$HOME} (or the directory you created for this training),
+create a new folder \code{project} for your first {\em autotools}
 In order to keep a good understanding of real source files as opposed
 to generated files, we'll put our project under version control, using
diff --git a/labs/autotools-usage/autotools-usage.tex b/labs/autotools-usage/autotools-usage.tex
index 705aa9d..eb2f8a9 100644
--- a/labs/autotools-usage/autotools-usage.tex
+++ b/labs/autotools-usage/autotools-usage.tex
@@ -10,13 +10,13 @@
 \section{Download ethtool}
-Go to the \code{$HOME/autotools-labs/usage/} directory.
 To start our exploration of {\em autotools}, we'll use the {\bf
   ethtool} set of programs. Download the 3.18 version from the project
 home page at
 \url{https://www.kernel.org/pub/software/network/ethtool/} and extract
+it. The location doesn't really matter, you can extract it directly in
+\code{$HOME}, or create a \code{$HOME/autotools-labs} for all your
+autotools labs.
 \section{Exploration of the sources}
@@ -59,9 +59,9 @@ program an man pages installed.
 \section{Out of tree build and cross-compiling}
-Now, create a separate build directory, say
-\code{$HOME/autotools-labs/usage/ethtool-arm/}, and move to this
-directory. Then, call the \code{configure} script of {\em ethtool}:
+Now, create a separate build directory, say \code{$HOME/ethtool-arm/},
+and move to this directory. Then, call the \code{configure} script of
+{\em ethtool}:
@@ -132,8 +132,9 @@ really absent, there would be a build failure.
 Now, let's look at another piece of software, which isn't distributed
 with pre-generated \code{configure} and \code{Makefile.in} files.
-Move back to \code{$HOME/autotools-labs/usage/}, and use {\em Git} to
-fetch the source code of a library called {\em libconfuse}:
+Go back to your \code{$HOME} directory (or another directory you
+created for this training session), and use {\em Git} to fetch the
+source code of a library called {\em libconfuse}:
 git clone https://github.com/martinh/libconfuse

More information about the training-materials-updates mailing list