[FE training-materials-updates] slides/buildroot: minor typo fixes
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Tue May 26 11:32:47 CEST 2015
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=2e63e7da46649a1f2a45a0ac9140d51ae58642b3
>---------------------------------------------------------------
commit 2e63e7da46649a1f2a45a0ac9140d51ae58642b3
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date: Tue May 26 11:31:13 2015 +0200
slides/buildroot: minor typo fixes
All typos reported by Thomas De Schampheleire, round 2.
Reported-by: Thomas De Schampheleire <patrickdepinguin at gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
>---------------------------------------------------------------
2e63e7da46649a1f2a45a0ac9140d51ae58642b3
slides/autotools-advanced/autotools-advanced.tex | 4 ++--
slides/autotools-basics/autotools-basics.tex | 6 +++---
slides/autotools-references/autotools-references.tex | 2 +-
slides/autotools-usage/autotools-usage.tex | 12 ++++++------
.../buildroot-advanced-packages.tex | 6 +++---
slides/buildroot-appdev/buildroot-appdev.tex | 2 +-
slides/buildroot-build/buildroot-build.tex | 2 +-
slides/buildroot-download/buildroot-download.tex | 7 +++----
slides/buildroot-internals/buildroot-internals.tex | 2 +-
slides/buildroot-introduction/buildroot-introduction.tex | 2 +-
slides/buildroot-kernel/buildroot-kernel.tex | 4 ++--
slides/buildroot-make/buildroot-make.tex | 2 +-
slides/buildroot-new-packages/buildroot-new-packages.tex | 10 +++++-----
slides/buildroot-rootfs/buildroot-rootfs.tex | 10 +++++-----
slides/buildroot-tree/buildroot-tree.tex | 2 +-
15 files changed, 36 insertions(+), 37 deletions(-)
diff --git a/slides/autotools-advanced/autotools-advanced.tex b/slides/autotools-advanced/autotools-advanced.tex
index d84292e..8af968c 100644
--- a/slides/autotools-advanced/autotools-advanced.tex
+++ b/slides/autotools-advanced/autotools-advanced.tex
@@ -489,7 +489,7 @@ PKG_CHECK_MODULES(prefix, list-of-modules,
\item Can contain version specifiers, such as \code{foo >= 3 bar
baz <= 4}
\end{itemize}
-\item Will exit with a failure if one of the dependency is missing.
+\item Will exit with a failure if one of the dependencies is missing.
\end{itemize}
\end{frame}
@@ -579,7 +579,7 @@ gdbus_serialization_LDADD = $(LDADD) $(DBUS1_LIBS)
\begin{frame}[fragile]{Recursive make}
\begin{itemize}
- \item The \code{SUBDIRS} variable in a \code{Makefile.am} indicate
+ \item The \code{SUBDIRS} variable in a \code{Makefile.am} indicates
the sub-directories that contain other \code{Makefile.am}
\end{itemize}
diff --git a/slides/autotools-basics/autotools-basics.tex b/slides/autotools-basics/autotools-basics.tex
index e4e2d44..557d66e 100644
--- a/slides/autotools-basics/autotools-basics.tex
+++ b/slides/autotools-basics/autotools-basics.tex
@@ -410,12 +410,12 @@ hello_SOURCES = main.c
\begin{itemize}
-\item \code{prefix} is the installation prefix, i.e where it should be
+\item \code{prefix} is the installation prefix, i.e. where it should be
installed
\begin{itemize}
\item All \code{*dir} variables from {\em autoconf} can be used,
without their \code{dir} suffix: use \code{bin} for \code{bindir}
- \item E.g: \code{bindir}, \code{libdir}, \code{includedir},
+ \item E.g.: \code{bindir}, \code{libdir}, \code{includedir},
\code{datadir}, etc.
\end{itemize}
@@ -465,7 +465,7 @@ hello_SOURCES = main.c
\end{frame}
-\begin{frame}[fragile]{Example: building multiples programs}
+\begin{frame}[fragile]{Example: building multiple programs}
\begin{block}{Makefile.am}
{\small
\begin{verbatim}
diff --git a/slides/autotools-references/autotools-references.tex b/slides/autotools-references/autotools-references.tex
index 13652a6..e42f898 100644
--- a/slides/autotools-references/autotools-references.tex
+++ b/slides/autotools-references/autotools-references.tex
@@ -17,7 +17,7 @@
\end{itemize}
\end{frame}
-\begin{frame}{Book: {\em Autotools, a practitionner guide}}
+\begin{frame}{Book: {\em Autotools, a practitioner's guide}}
\begin{columns}
\column{0.6\textwidth}
\begin{itemize}
diff --git a/slides/autotools-usage/autotools-usage.tex b/slides/autotools-usage/autotools-usage.tex
index ff1fed7..a150e4c 100644
--- a/slides/autotools-usage/autotools-usage.tex
+++ b/slides/autotools-usage/autotools-usage.tex
@@ -25,7 +25,7 @@
\begin{itemize}
\item Not very portable
\item No configuration tests, or options
- \item Hard to take into account all dependencies (e.g dependencies
+ \item Hard to take into account all dependencies (e.g. dependencies
on header files)
\item No standardized behavior
\end{itemize}
@@ -139,8 +139,8 @@
\item They are all automatically {\em guessed} to the current
machine by default
\item \code{--build}, generally does not need to be changed
- \item \code{--host}, must be overriden to do cross-compilation
- \item \code{--target}, needs to be overriden if needed (to
+ \item \code{--host}, must be overridden to do cross-compilation
+ \item \code{--target}, needs to be overridden if needed (to
generate a cross-compiler, for example)
\end{itemize}
\item Arguments to these options are {\em configuration names}, also
@@ -154,13 +154,13 @@
system, ABI and C library
\item General format: \code{<arch>-<vendor>-<kernel>-<operating_system>}
\begin{itemize}
- \item \code{<arch>} is the type of processor, i.e \code{arm},
+ \item \code{<arch>} is the type of processor, i.e. \code{arm},
\code{i686}, etc.
\item \code{<vendor>} is a free form string, which can be omitted
\item \code{<kernel>} is always \code{linux} when working with
Linux systems, or \code{none} for bare metal systems
\item \code{<operating_system>} generally identifies the C library
- and ABI, i.e \code{gnu}, \code{gnueabi}, \code{eabi},
+ and ABI, i.e. \code{gnu}, \code{gnueabi}, \code{eabi},
\code{gnueabihf}, \code{uclibcgnueabihf}
\end{itemize}
\item Also often used as the {\em prefix} for cross-compilation
@@ -197,7 +197,7 @@ checking how to run the C preprocessor... gcc -E
\begin{itemize}
\item By default, {\em autotools} will guess the {\bf host} machine
as being the current machine
- \item To cross-compile, it must be overriden by passing the
+ \item To cross-compile, it must be overridden by passing the
\code{--host} option with the appropriate {\em configuration name}
\item By default, {\em autotools} will try to use the
cross-compilation tools that use the {\em configuration name} as
diff --git a/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex b/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
index 3a3656a..20db8ca 100644
--- a/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
+++ b/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
@@ -68,7 +68,7 @@ $ make legal-info
\begin{itemize}
\item Boolean indicating whether the package source code can be
redistributed or not (part of the \code{legal-info} output)
- \item Defaults to \code{YES}, can be overriden to \code{NO}
+ \item Defaults to \code{YES}, can be overridden to \code{NO}
\item If \code{NO}, source code is not copied when generating the
licensing report
\end{itemize}
@@ -114,7 +114,7 @@ OWL_LINUX_REDISTRIBUTE = NO
that are too specific to the product being made
\end{itemize}
\item Patches are automatically applied by Buildroot, during the
- {\em patch} step, i.e after extracting the package, but before
+ {\em patch} step, i.e. after extracting the package, but before
configuring it.
\item Buildroot already comes with a number of patches for various
packages, but you may need to add more for your own packages, or
@@ -347,7 +347,7 @@ endef
\begin{itemize}
\item By default, before creating the root filesystem images,
- Buildroot changes the ownership of all files to \code{0:0}, i.e
+ Buildroot changes the ownership of all files to \code{0:0}, i.e.
\code{root:root}
\item Permissions are preserved as is, but since the build is executed
as non-root, it is not possible to install setuid applications.
diff --git a/slides/buildroot-appdev/buildroot-appdev.tex b/slides/buildroot-appdev/buildroot-appdev.tex
index 807610f..2d99b39 100644
--- a/slides/buildroot-appdev/buildroot-appdev.tex
+++ b/slides/buildroot-appdev/buildroot-appdev.tex
@@ -188,7 +188,7 @@ LINUX_OVERRIDE_SRCDIR = $(HOME)/projects/linux
\begin{itemize}
\item Disabled by default.
\item Sub-options allow to control the amount of debugging symbols
- (i.e gcc options \code{-g1}, \code{-g2} and \code{-g3}).
+ (i.e. gcc options \code{-g1}, \code{-g2} and \code{-g3}).
\end{itemize}
\item The \code{BR2_STRIP_none} and \code{BR2_STRIP_strip} options
allow to disable or enable stripping of binaries on the target.
diff --git a/slides/buildroot-build/buildroot-build.tex b/slides/buildroot-build/buildroot-build.tex
index ec80730..dd27ca5 100644
--- a/slides/buildroot-build/buildroot-build.tex
+++ b/slides/buildroot-build/buildroot-build.tex
@@ -225,7 +225,7 @@ $ make
\end{block}
\item Additional instructions often available in
- \code{board/<boardname>}, e.g: \code{board/qemu/arm-vexpess/readme.txt}.
+ \code{board/<boardname>}, e.g.: \code{board/qemu/arm-vexpess/readme.txt}.
\end{itemize}
\end{frame}
diff --git a/slides/buildroot-download/buildroot-download.tex b/slides/buildroot-download/buildroot-download.tex
index 08ace7e..158b770 100644
--- a/slides/buildroot-download/buildroot-download.tex
+++ b/slides/buildroot-download/buildroot-download.tex
@@ -52,9 +52,8 @@
\begin{frame}{Backup Buildroot mirror}
\begin{itemize}
- \item Since sometimes the upstream location disappear or are
- temporarily unavailable, having a backup server is sometimes
- useful
+ \item Since sometimes the upstream locations disappear or are
+ temporarily unavailable, having a backup server is useful
\item Address configured through \code{BR2_BACKUP_SITE}
\item Defaults to \code{http://sources.buildroot.net}
\begin{itemize}
@@ -150,7 +149,7 @@ strace-4.10.tar.xz: OK (sha1: 5c3ec4c5a9eeb440d7ec70514923c2e7e7f9ab6c)
\end{itemize}
\item \code{make source-check}
\begin{itemize}
- \item Checks where the upstream site of all downloads needed for
+ \item Checks whether the upstream site of all downloads needed for
the current configuration are still available.
\end{itemize}
\end{itemize}
diff --git a/slides/buildroot-internals/buildroot-internals.tex b/slides/buildroot-internals/buildroot-internals.tex
index 9396acf..3e1a266 100644
--- a/slides/buildroot-internals/buildroot-internals.tex
+++ b/slides/buildroot-internals/buildroot-internals.tex
@@ -493,7 +493,7 @@ $$($(2)_TARGET_SOURCE): | dependencies
\item \code{prepare}: generates a kconfig-related \code{auto.conf}
file
\item \code{dependencies}: triggers the check of Buildroot system
- dependencies, i.e things that must be installed on the machine
+ dependencies, i.e. things that must be installed on the machine
to use Buildroot
\end{itemize}
\end{itemize}
diff --git a/slides/buildroot-introduction/buildroot-introduction.tex b/slides/buildroot-introduction/buildroot-introduction.tex
index ce2edf9..c13ac72 100644
--- a/slides/buildroot-introduction/buildroot-introduction.tex
+++ b/slides/buildroot-introduction/buildroot-introduction.tex
@@ -255,7 +255,7 @@ $ make 2>&1 | tee build.log
device
\begin{itemize}
\item Those steps are very device specific
- \item Buildroot provides some tools for specific platforms (e.g:
+ \item Buildroot provides some tools for specific platforms (e.g.:
SAM-BA for Atmel, imx-usb-loader for i.MX6, etc.)
\end{itemize}
\end{itemize}
diff --git a/slides/buildroot-kernel/buildroot-kernel.tex b/slides/buildroot-kernel/buildroot-kernel.tex
index c79f18a..4605c7d 100644
--- a/slides/buildroot-kernel/buildroot-kernel.tex
+++ b/slides/buildroot-kernel/buildroot-kernel.tex
@@ -54,8 +54,8 @@
configuration file, and start the corresponding Linux kernel
configuration interface.
\item Changes made are only made in
- \code{$(O)/build/linux-<version>/}, i.e they are not preserved
- accross a clean rebuild.
+ \code{$(O)/build/linux-<version>/}, i.e. they are not preserved
+ across a clean rebuild.
\item To save them:
\begin{itemize}
\item \code{make linux-update-config}, to save a full config file
diff --git a/slides/buildroot-make/buildroot-make.tex b/slides/buildroot-make/buildroot-make.tex
index 7822046..3c96ac3 100644
--- a/slides/buildroot-make/buildroot-make.tex
+++ b/slides/buildroot-make/buildroot-make.tex
@@ -11,7 +11,7 @@
\item Defining and using functions
\item Useful {\em make} functions
\end{itemize}
- \item This does not aim at replacing a full course o {\em GNU Make}
+ \item This does not aim at replacing a full course on {\em GNU Make}
\item \url{http://www.gnu.org/software/make/manual/make.html}
\item \url{http://www.nostarch.com/gnumake}
\end{itemize}
diff --git a/slides/buildroot-new-packages/buildroot-new-packages.tex b/slides/buildroot-new-packages/buildroot-new-packages.tex
index d85026f..8295747 100644
--- a/slides/buildroot-new-packages/buildroot-new-packages.tex
+++ b/slides/buildroot-new-packages/buildroot-new-packages.tex
@@ -215,7 +215,7 @@ config BR2_PACKAGE_NEARD
\begin{frame}{\code{Config.in.host} for host packages?}
\begin{itemize}
\item Most of the packages in Buildroot are {\em target} packages,
- i.e they are cross-compiled for the target architecture, and meant
+ i.e. they are cross-compiled for the target architecture, and meant
to be run on the target platform.
\item Some packages have a {\em host} variant, built to be executed
on the build machine. Such packages are needed for the build
@@ -346,7 +346,7 @@ endif
\end{center}
\end{frame}
-\begin{frame}{Other packages infrastructures}
+\begin{frame}{Other package infrastructures}
\begin{itemize}
\item The other package infrastructures are meant to be used when
the software component uses a well-known build system.
@@ -528,7 +528,7 @@ NODEJS_MODULES_LIST = $(call qstrip,$(BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL))
\item Exceptions:
\begin{itemize}
\item Git, Subversion or Mercurial repositories accessed over
- HTTP.
+ HTTP or SSH.
\item \code{file} and \code{local} methods
\end{itemize}
\item In such cases, use \code{<pkg>_SITE_METHOD} explicitly.
@@ -1035,7 +1035,7 @@ $(eval $(autotools-package))
be set to either \code{distutils} or \code{setuptools}
\item And several optional variables to further adjust the build:
\code{<pkg>_ENV}, \code{<pkg>_BUILD_OPTS},
- \code{<pkg>_INSTALL_TARGETS_OPTS},
+ \code{<pkg>_INSTALL_TARGET_OPTS},
\code{<pkg>_INSTALL_STAGING_OPTS}, \code{<pkg>_INSTALL_OPTS},
\code{<pkg>_NEEDS_HOST_PYTHON}.
\end{itemize}
@@ -1137,7 +1137,7 @@ $(eval $(python-package))
prepending \code{host-} to all dependencies.
\item \code{FOO_DEPENDENCIES = bar host-baz} $\rightarrow$
\code{HOST_FOO_DEPENDENCIES = host-bar host-baz}.
- \item Can be overriden if the dependencies of the host variant are
+ \item Can be overridden if the dependencies of the host variant are
different than the ones of the target variant.
\end{itemize}
\end{itemize}
diff --git a/slides/buildroot-rootfs/buildroot-rootfs.tex b/slides/buildroot-rootfs/buildroot-rootfs.tex
index 242cc8c..5b6b5a8 100644
--- a/slides/buildroot-rootfs/buildroot-rootfs.tex
+++ b/slides/buildroot-rootfs/buildroot-rootfs.tex
@@ -36,8 +36,8 @@
Busybox, Qt, OpenSSH, lighttpd, and many more)
\item Most of them will install files in \code{$(TARGET_DIR)}:
programs, libraries, fonts, data files, configuration files, etc.
- \item This is really the step that will bring in the root filesystem
- the vast majority of the files.
+ \item This is really the step that will bring the vast majority of
+ the files in the root filesystem.
\item Covered in more details in the section about creating your own
Buildroot packages.
\end{itemize}
@@ -49,7 +49,7 @@
executed to reduce the size of the root filesystem.
\item It mainly involves:
\begin{itemize}
- \item Remove header files, pkg-config files, CMake files, static
+ \item Removing header files, pkg-config files, CMake files, static
libraries, man pages, documentation.
\item Stripping all the programs and libraries using \code{strip},
to remove unneeded information. Depends on
@@ -230,7 +230,7 @@ BR2_ROOTFS_POST_BUILD_SCRIPT="board/myproject/post-build.sh"
\begin{frame}[fragile]{Users table}
\begin{itemize}
\item One may need to add specific Unix users and groups in addition
- to the one available in the default skeleton.
+ to the ones available in the default skeleton.
\item \code{BR2_ROOTFS_USERS_TABLES} is a space-separated list of
user tables.
\item Packages can also specify their own users. See the {\em
@@ -375,7 +375,7 @@ test 8000 wheel -1 = - /bin/sh - Test u
\begin{frame}{Deploying the image: initramfs}
\begin{itemize}
- \item Another common use case is to use an {\em initramfs}, i.e a
+ \item Another common use case is to use an {\em initramfs}, i.e. a
root filesystem fully in RAM.
\begin{itemize}
\item Convenient for small filesystems, fast booting or kernel
diff --git a/slides/buildroot-tree/buildroot-tree.tex b/slides/buildroot-tree/buildroot-tree.tex
index 28c67e3..a123215 100644
--- a/slides/buildroot-tree/buildroot-tree.tex
+++ b/slides/buildroot-tree/buildroot-tree.tex
@@ -181,7 +181,7 @@
\item \code{output/}
\begin{itemize}
\item \code{staging/}
- \item Just a symbolic link to the {\em sysroot}, i.e to
+ \item Just a symbolic link to the {\em sysroot}, i.e. to
\code{host/<tuple>/sysroot/}.
\item Available for convenience
\end{itemize}
More information about the training-materials-updates
mailing list