lfs/glfs
1
0
Fork 0
mirror of https://github.com/glfs-book/glfs.git synced 2025-07-22 01:12:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

*: Remove <application> tags.

Browse Source 
The application tag seemed to just put an extra space on either side of
the word(s) the tags surrounded and seemed to serve no purpose beyond
that. If it served the purpose of jhalfs, well this book is not
supported by jhalfs. The result of the tags just added space in both the
rendered output and in the XML files.

Now, when referring to a package name, we just say the name and don't
surround it via a tag. The only exception is using <command>,
<filename>, <xref>, or <ulink>.
This commit is contained in:
Zeckmathederg
2025-07-17 13:32:36 -06:00
parent 4ec763de39
commit b6e0053e6a
162 changed files with 936 additions and 938 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
archive/git.xml
View File

@ -23,18 +23,18 @@
<title>Introduction to Git</title>
<para>
<application>Git</application> is a free and open source, distributed
Git is a free and open source, distributed
version control system designed to handle everything from small to very
large projects with speed and efficiency. Every
<application>Git</application> clone is a full-fledged repository with
Git clone is a full-fledged repository with
complete history and full revision tracking capabilities, not dependent
on network access or a central server. Branching and merging are fast and
easy to do. <application>Git</application> is used for version control of
files, much like tools such as <application>Mercurial</application>,
<application>Bazaar</application>, <application>Subversion</application>,
easy to do. Git is used for version control of
files, much like tools such as Mercurial,
Bazaar, Subversion,
<ulink url="https://www.nongnu.org/cvs/">CVS</ulink>,
<application>Perforce</application>, and
<application>Team Foundation Server</application>.
Perforce, and
Team Foundation Server.
</para>
<itemizedlist spacing="compact">
@ -71,7 +71,7 @@
<bridgehead renderas="sect4">Recommended</bridgehead>
<para role="recommended">
<xref linkend="curl"/> (needed to use <application>Git</application> over
<xref linkend="curl"/> (needed to use Git over
http, https, ftp or ftps)
</para>
@ -81,7 +81,7 @@
<title>Installation of Git</title>
<para>
Install <application>Git</application> by running the following
Install Git by running the following
commands:
</para>
@ -242,14 +242,14 @@ sed -i '/^\* link:/s|howto/|&amp;html/|' /usr/share/doc/git-&git-version;/howto-
<para>
<parameter>--with-gitconfig=/etc/gitconfig</parameter>: This sets
<filename>/etc/gitconfig</filename> as the file that stores
the default, system wide, <application>Git</application>
the default, system wide, Git
settings.
</para>
<para>
<parameter>--with-python=python3</parameter>: Use this switch to use
<application>Python 3</application>, instead of the EOL'ed
<application>Python 2</application>. Python is used for the
Python 3, instead of the EOL'ed
Python 2. Python is used for the
<command>git p4</command> interface to Perforce repositories,
and also used in some tests.
</para>
@ -257,7 +257,7 @@ sed -i '/^\* link:/s|howto/|&amp;html/|' /usr/share/doc/git-&git-version;/howto-
<!--
<para>
<option>- -with-libpcre2</option>: Use this switch if
<application>PCRE2</application> is installed.
PCRE2 is installed.
</para>
-->
@ -354,7 +354,7 @@ sed -i '/^\* link:/s|howto/|&amp;html/|' /usr/share/doc/git-&git-version;/howto-
<term><command>git-cvsserver</command></term>
<listitem>
<para>
is a CVS server emulator for <application>Git</application>
is a CVS server emulator for Git
</para>
<indexterm zone="git git-cvsserver">
<primary sortas="b-git-cvsserver">git-cvsserver</primary>
@ -366,7 +366,7 @@ sed -i '/^\* link:/s|howto/|&amp;html/|' /usr/share/doc/git-&git-version;/howto-
<term><command>gitk</command></term>
<listitem>
<para>
is a graphical <application>Git</application> repository browser
is a graphical Git repository browser
(needs <ulink url="&blfs-svn;/general/tk.html">Tk</ulink>)
</para>
<indexterm zone="git gitk">

2
archive/glibc.xml
View File

@ -71,7 +71,7 @@
<title>lib32 Installation of glibc</title>
<para>
Install lib32-<application>glibc</application> by running the following commands:
Install lib32-glibc by running the following commands:
</para>
<screen><userinput>patch -Np1 -i ../glibc-&glibc-version;-fhs-1.patch &amp;&amp;

6
archive/glslang.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Glslang</title>
<para>
The <application>Glslang</application> package contains an frontend and
The Glslang package contains an frontend and
validator for OpenGL, OpenGL ES, and Vulkan shaders.
</para>
@ -75,7 +75,7 @@
-->
<para>
Install <application>Glslang</application> by running the following
Install Glslang by running the following
commands:
</para>
@ -107,7 +107,7 @@ ninja</userinput></screen>
<title>lib32 Installation of Glslang</title>
<para>
Install lib32-<application>Glslang</application> by running the following
Install lib32-Glslang by running the following
commands:
</para>

20
archive/gnat-binary.xml
View File

@ -33,12 +33,12 @@
<para>
The compiler and associated tools on this page are known as the
<application>GNAT</application> technology, developed by the Adacore
company, using the <application>GCC</application> backend. Since
GNAT technology, developed by the Adacore
company, using the GCC backend. Since
parts of the Ada compiler are written in Ada, there is a circular
dependency on an Ada compiler. The instructions below install a
binary compiler. You do not need to do that if you already have built
<application>GNAT</application> tools. The next section covers how to
GNAT tools. The next section covers how to
build GNAT once the circular dependency is satisfied.
</para>
@ -68,7 +68,7 @@
<ulink url="https://www.linuxfromscratch.org/blfs/view/svn/basicnet/links.html">
links</ulink>. You can use
<xref linkend="wget"/> but not <xref linkend="curl"/>.
If you do end up using <application>wget</application>
If you do end up using wget
regardless of the recommendation against it, please run
the following the command before unpacking:
</para>
@ -81,9 +81,9 @@
<important>
<para>
If you are doing multilib, just download the x86_64
<application>GNAT</application> binary tarball.
GNAT binary tarball.
The instructions in the next section for multilib will
work as expected and <application>GCC</application>
work as expected and GCC
will continue to have multilib support.
</para>
</important>
@ -94,7 +94,7 @@
<title>Installation of GNAT Binaries</title>
<para>
Install the x86_64 <application>GNAT</application>
Install the x86_64 GNAT
binaries by running the following commands as the
<systemitem class="username">root</systemitem> user
while still in the directory the tarball is in:
@ -111,7 +111,7 @@ cd $GNATTBPATH &amp;&amp;
unset GNATTBPATH</userinput></screen>
<para>
Or install the x86 <application>GNAT</application>
Or install the x86 GNAT
binaries by running the following commands as the
<systemitem class="username">root</systemitem> user
while still in the directory the tarball is in:
@ -129,7 +129,7 @@ unset GNATTBPATH</userinput></screen>
<para>
Now adjust the <filename>PATH</filename> variable so
the <application>GNAT</application> software can be found
the GNAT software can be found
and used:
</para>
@ -138,7 +138,7 @@ export PATH=/opt/gnat/bin:$PATH_HOLD</userinput></screen>
<para>
Ensure <command>ld</command> and <command>as</command>
from the <application>GNAT</application> package aren't
from the GNAT package aren't
used as to prevent issues with aging by issuing the
following as the <systemitem class="username">root
</systemitem> user:

40
archive/gnat.xml
View File

@ -21,10 +21,10 @@
<title>Introduction to GNAT</title>
<para>
<application>GNAT</application> is a part of
<application>GCC</application>. It is often called
GNAT is a part of
GCC. It is often called
GCC-Ada because of this. Not many packages depend
on <application>GNAT</application> besides
on GNAT besides
<xref linkend="wine"/>, although some packages
optionally depend on it.
</para>
@ -137,7 +137,7 @@ else
fi</userinput></screen>
<para>
Now install <application>GNAT</application> by running the following
Now install GNAT by running the following
commands:
</para>
@ -166,8 +166,8 @@ sed -e 's/{ target nonpic } //' \
<para>
If you have installed additional packages such as
<application>valgrind</application> and <application>gdb
</application>, the <application>gcc</application> part of the
valgrind and gdb
, the gcc part of the
test suite will run more tests than in LFS. Some of those will
report FAIL and others XPASS (pass when expected to FAIL).
As of gcc-&gcc-version;, about 74 FAIL occur in the “guality”
@ -209,7 +209,7 @@ ln -sfv ../../libexec/gcc/$(gcc -dumpmachine)/&gcc-version;/liblto_plugin.so \
<title>Cleaning Up and Testing</title>
<para>
Now that <application>GNAT</application> has been installed,
Now that GNAT has been installed,
it is time to clean up and test your installation to make sure
everything is working as expected.
</para>
@ -289,7 +289,7 @@ rm -v testgnat*</userinput></screen>
<para>
<command>mkdir build; cd build</command>: The
<application>GCC</application> documentation recommends
GCC documentation recommends
building the package in a dedicated build directory.
</para>
@ -307,9 +307,9 @@ rm -v testgnat*</userinput></screen>
<para>
<parameter>--with-system-zlib</parameter>: Uses the system
<application>zlib</application> instead of the bundled one.
<application>zlib</application> is used for compressing
and decompressing <application>GCC</application>'s intermediate
zlib instead of the bundled one.
zlib is used for compressing
and decompressing GCC's intermediate
language in LTO (Link Time Optimization) object files.
</para>
@ -332,8 +332,8 @@ rm -v testgnat*</userinput></screen>
This command builds support for ADA, C, and C++. Refer to <ulink
url="https://www.linuxfromscratch.org/blfs/view/svn/general/gcc.html"/>
to find what other languages are supported. Make sure to add
<parameter>ada</parameter> to the option if you recompile <application>
GCC</application>.
<parameter>ada</parameter> to the option if you recompile
GCC.
</para>
<para>
@ -356,7 +356,7 @@ rm -v testgnat*</userinput></screen>
<para>
<command>mv -v /usr/lib/*gdb.py ...</command>: The installation
stage puts some files used by <application>gdb</application> under the
stage puts some files used by gdb under the
<filename class="directory">/usr/lib</filename> directory. This generates
spurious error messages when performing <command>ldconfig</command>. This
command moves the files to another location.
@ -456,7 +456,7 @@ rm -v testgnat*</userinput></screen>
<listitem>
<para>
is useful for renaming files to meet the standard
<application>Ada</application> default file naming conventions.
Ada default file naming conventions.
</para>
<indexterm zone="gnat gnatchop">
<primary sortas="b-gnatchop">gnatchop</primary>
@ -469,7 +469,7 @@ rm -v testgnat*</userinput></screen>
<listitem>
<para>
is used to remove files associated with a
<application>GNAT</application> project.
GNAT project.
</para>
<indexterm zone="gnat gnatclean">
<primary sortas="b-gnatclean">gnatclean</primary>
@ -482,7 +482,7 @@ rm -v testgnat*</userinput></screen>
<listitem>
<para>
is intended for locating definition and/or references to
specified entities in a <application>GNAT</application> project.
specified entities in a GNAT project.
</para>
<indexterm zone="gnat gnatfind">
<primary sortas="b-gnatfind">gnatfind</primary>
@ -531,7 +531,7 @@ rm -v testgnat*</userinput></screen>
<term><command>gnatmake</command></term>
<listitem>
<para>
is the <application>Ada</application> compiler, which performs
is the Ada compiler, which performs
compilation, binding and linking.
</para>
<indexterm zone="gnat gnatmake">
@ -545,7 +545,7 @@ rm -v testgnat*</userinput></screen>
<listitem>
<para>
will list the files associated with a
<application>GNAT</application> project.
GNAT project.
</para>
<indexterm zone="gnat gnatname">
<primary sortas="b-gnatname">gnatname</primary>
@ -557,7 +557,7 @@ rm -v testgnat*</userinput></screen>
<term><command>gnatprep</command></term>
<listitem>
<para>
is the <application>GNAT</application> external preprocessor.
is the GNAT external preprocessor.
</para>
<indexterm zone="gnat gnatprep">
<primary sortas="b-gnatprep">gnatprep</primary>

6
archive/lib32-check.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to lib32-Check</title>
<para>
The <application>Check</application> package was already installed in
The Check package was already installed in
LFS, but the lib32 instructions are missing from MLFS which is needed for
lib32-<xref linkend="pulseaudio"/>. If you are doing multilib, install
this.
@ -47,7 +47,7 @@
<title>lib32 Installation of Check</title>
<para>
Install lib32-<application>Check</application> by running the following
Install lib32-Check by running the following
commands:
</para>
@ -107,7 +107,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libcheck.so</filename></term>
<listitem>
<para>
contains functions that allow <application>Check</application> to
contains functions that allow Check to
be called from a test program
</para>
<indexterm zone="lib32-check libcheck">

6
archive/libvk.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Vulkan-Loader</title>
<para>
The <application>Vulkan-Loader</application> package contains a library
The Vulkan-Loader package contains a library
which provides the Vulkan API and provides core support for graphics
drivers for Vulkan.
</para>
@ -68,7 +68,7 @@
</note>
<para>
Install <application>Vulkan-Loader</application> by running the following
Install Vulkan-Loader by running the following
commands:
</para>
@ -98,7 +98,7 @@ ninja</userinput></screen>
<title>lib32 Installation of Vulkan-Loader</title>
<para>
Install lib32-<application>Vulkan-Loader</application> by running
Install lib32-Vulkan-Loader by running
the following commands:
</para>

4
archive/luit.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to luit</title>
<para>
The <application>luit</application> package is a filter
The luit package is a filter
that can be run between an arbitrary application and a UTF-8
terminal emulator. It will convert application output from the
locale’s encoding into UTF‐8, and convert terminal input from
@ -54,7 +54,7 @@
<title>Installation of luit</title>
<para>
Install <application>luit</application> by running the
Install luit by running the
following commands:
</para>

64
archive/nvidia.xml
View File

@ -24,7 +24,7 @@
<title>Introduction to NVIDIA</title>
<para>
The <application>NVIDIA</application> proprietary driver contains
The NVIDIA proprietary driver contains
firmware, kernel drivers, userland drivers pertaining to OpenGL,
Vulkan, and hardware acceleration, and provides useful utilites.
</para>
@ -96,8 +96,8 @@
<note>
<para>
Make sure to execute the following command when an <application>Xorg
</application> instance isn't running, or else the driver will
Make sure to execute the following command when an Xorg
instance isn't running, or else the driver will
complain and quit. Alternatively, you can pass <parameter>
--allow-installation-with-running-driver --no-x-check</parameter> to
override NVIDIA's warnings. This is not recommended as it skips
@ -126,7 +126,7 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="nvidia-kernel.xml"/>
<para>
Install x86_64 <application>NVIDIA</application> by running the following
Install x86_64 NVIDIA by running the following
commands as the <systemitem class="username">root</systemitem> user:
</para>
@ -137,7 +137,7 @@
<para>
If you are only interested in the 32-bit driver, install x86
<application>NVIDIA</application> by running the following
NVIDIA by running the following
commands as the <systemitem class="username">root</systemitem> user:
</para>
@ -183,7 +183,7 @@
<important>
<para>
When you update the kernel, you will also need to reinstall the
<application>NVIDIA</application> driver.
NVIDIA driver.
</para>
<para>
@ -344,7 +344,7 @@
<term><command>nvidia-bug-report.sh</command></term>
<listitem>
<para>
is the <application>NVIDIA</application> bug reporting shell script.
is the NVIDIA bug reporting shell script.
</para>
<indexterm zone="nvidia nvidia-bug-report.sh">
<primary sortas="b-nvidia-bug-report.sh">nvidia-bug-report.sh</primary>
@ -393,8 +393,8 @@
<term><command>nvidia-installer</command></term>
<listitem>
<para>
installs, upgrades, and uninstalls the <application>NVIDIA
</application> driver (running the runfile directly is
installs, upgrades, and uninstalls the NVIDIA
driver (running the runfile directly is
recommended)
</para>
<indexterm zone="nvidia nvidia-installer">
@ -407,8 +407,8 @@
<term><command>nvidia-modprobe</command></term>
<listitem>
<para>
creates Linux device files and loads the <application>NVIDIA
</application> kernel module
creates Linux device files and loads the NVIDIA
kernel module
</para>
<indexterm zone="nvidia nvidia-modprobe">
<primary sortas="b-nvidia-modprobe">nvidia-modprobe</primary>
@ -444,7 +444,7 @@
<term><command>nvidia-powerd</command></term>
<listitem>
<para>
provides support for the <application>NVIDIA</application>
provides support for the NVIDIA
Dynamic Boost feature
</para>
<indexterm zone="nvidia nvidia-powerd">
@ -495,8 +495,8 @@
<term><command>nvidia-uninstall</command></term>
<listitem>
<para>
installs, upgrades, and uninstalls the <application>NVIDIA
</application> driver (running the runfile directly is
installs, upgrades, and uninstalls the NVIDIA
driver (running the runfile directly is
recommended)
</para>
<indexterm zone="nvidia nvidia-uninstall">
@ -509,9 +509,9 @@
<term><command>nvidia-xconfig</command></term>
<listitem>
<para>
manipulates <application>X11</application> configuration files
to allow the <application>NVIDIA</application> driver to be used
when starting <application>X11</application>
manipulates X11 configuration files
to allow the NVIDIA driver to be used
when starting X11
</para>
<indexterm zone="nvidia nvidia-xconfig">
<primary sortas="b-nvidia-xconfig">nvidia-xconfig</primary>
@ -523,7 +523,7 @@
<term><filename class="libraryfile">libEGL_nvidia.so</filename></term>
<listitem>
<para>
provides <application>NVIDIA</application> implementations
provides NVIDIA implementations
of OpenGL functionality
</para>
<indexterm zone="nvidia libEGL_nvidia">
@ -560,7 +560,7 @@
<term><filename class="libraryfile">libGLX_nvidia.so</filename></term>
<listitem>
<para>
provides <application>NVIDIA</application> implementations
provides NVIDIA implementations
of OpenGL functionality
</para>
<indexterm zone="nvidia libGLX_nvidia">
@ -597,8 +597,8 @@
<term><filename class="libraryfile">libglxserver_nvidia.so</filename></term>
<listitem>
<para>
is the <application>NVIDIA</application> GLX extension module for
<application>X11</application>
is the NVIDIA GLX extension module for
X11
</para>
<indexterm zone="nvidia libglxserver_nvidia">
<primary sortas="c-libglxserver_nvidia">libglxserver_nvidia.so</primary>
@ -670,7 +670,7 @@
<term><filename class="libraryfile">libnvidia-egl-wayland.so</filename></term>
<listitem>
<para>
provides client-side <application>Wayland</application> EGL
provides client-side Wayland EGL
application support
</para>
<indexterm zone="nvidia libnvidia-egl-wayland">
@ -708,7 +708,7 @@
<listitem>
<para>
provides an interface to capture and optionally encode the
framebuffer of an <application>X11</application> server screen
framebuffer of an X11 server screen
</para>
<indexterm zone="nvidia libnvidia-fbc">
<primary sortas="c-libnvidia-fbc">libnvidia-fbc.so</primary>
@ -828,7 +828,7 @@
<term><filename class="libraryfile">libnvidia-opencl.so</filename></term>
<listitem>
<para>
provides <application>NVIDIA</application>'s implementation of
provides NVIDIA's implementation of
the OpenCL API standard
</para>
<indexterm zone="nvidia libnvidia-opencl">
@ -907,8 +907,8 @@
<term><filename class="libraryfile">libnvidia-tls.so</filename></term>
<listitem>
<para>
provides thread local storage support for the <application>NVIDIA
</application> OpenGL libraries
provides thread local storage support for the NVIDIA
OpenGL libraries
</para>
<indexterm zone="nvidia libnvidia-tls">
<primary sortas="c-libnvidia-tls">libnvidia-tls.so</primary>
@ -921,7 +921,7 @@
<listitem>
<para>
is required for <command>nvidia-settings</command> on
<application>Wayland</application>
Wayland
</para>
<indexterm zone="nvidia libnvidia-wayland-client">
<primary sortas="c-libnvidia-wayland-client">libnvidia-wayland-client.so</primary>
@ -945,7 +945,7 @@
<term><filename class="libraryfile">libvdpau_nvidia.so</filename></term>
<listitem>
<para>
provides the <application>NVIDIA</application> implementation for
provides the NVIDIA implementation for
the VDPAU library
</para>
<indexterm zone="nvidia libvdpau_nvidia">
@ -958,7 +958,7 @@
<term><filename class="libraryfile">_nvngx.dll</filename></term>
<listitem>
<para>
provides DLSS support for use with <application>Wine</application>
provides DLSS support for use with Wine
</para>
<indexterm zone="nvidia _nvngx">
<primary sortas="c-_nvngx">_nvngx.dll</primary>
@ -982,7 +982,7 @@
<term><filename class="libraryfile">nvidia-drm_gbm.so</filename></term>
<listitem>
<para>
is the <application>NVIDIA</application> implementation of GBM
is the NVIDIA implementation of GBM
</para>
<indexterm zone="nvidia nvidia-drm_gbm">
<primary sortas="c-nvidia-drm_gbm">nvidia-drm_gbm.so</primary>
@ -994,8 +994,8 @@
<term><filename class="libraryfile">nvidia_drv.so</filename></term>
<listitem>
<para>
is the <application>NVIDIA</application> <application>X11
</application> driver
is the NVIDIA X11
driver
</para>
<indexterm zone="nvidia nvidia_drv">
<primary sortas="c-nvidia_drv">nvidia_drv.so</primary>

4
archive/pipewire.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Pipewire</title>
<para>
The <application>pipewire</application> package contains a server and
The pipewire package contains a server and
userspace API to handle multimedia pipelines. This includes a universal
API to connect to multimedia devices, as well as sharing multimedia
files between applications.
@ -103,7 +103,7 @@
-->
<para>
Install <application>pipewire</application> by running the following
Install pipewire by running the following
commands:
</para>

4
archive/spirv-headers.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to SPIRV-Headers</title>
<para>
The <application>SPIRV-Headers</application> package contains headers
The SPIRV-Headers package contains headers
that allow for applications to the SPIR-V language and instruction set
with Vulkan. SPIR-V is a binary intermediate language for representing
graphical shader stages and compute kernels for multiple Khronos APIs,
@ -63,7 +63,7 @@
</note>
<para>
Install <application>SPIRV-Headers</application> by running the following
Install SPIRV-Headers by running the following
commands:
</para>

6
archive/spirv-tools.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to SPIRV-Tools</title>
<para>
The <application>SPIRV-Tools</application> package contains libraries
The SPIRV-Tools package contains libraries
and utilities for processing SPIR-V modules.
</para>
@ -63,7 +63,7 @@
</note>
<para>
Install <application>SPIRV-Tools</application> by running the following
Install SPIRV-Tools by running the following
commands:
</para>
@ -96,7 +96,7 @@ ninja</userinput></screen>
<title>lib32 Installation of SPIRV-Tools</title>
<para>
Install lib32-<application>SPIRV-Tools</application> by running the following
Install lib32-SPIRV-Tools by running the following
commands:
</para>

6
archive/twm.xml
View File

@ -26,7 +26,7 @@
<title>Introduction to twm</title>
<para>
The <application>twm</application> package contains a very minimal
The twm package contains a very minimal
window manager.
</para>
@ -87,7 +87,7 @@
<title>Installation of twm</title>
<para>
Install <application>twm</application> by running the
Install twm by running the
following commands:
</para>
@ -111,7 +111,7 @@ make</userinput></screen>
<title>Command Explanations</title>
<para>
<command>sed -i -e '/^rcdir =/s...</command>: This command ensures
the <application>twm</application> configuration file gets installed in
the twm configuration file gets installed in
the proper location.
</para>
</sect2>

4
archive/vkheaders.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Vulkan-headers</title>
<para>
The <application>Vulkan-Headers</application> package contains a set of
The Vulkan-Headers package contains a set of
header files necessary to build and link applications against the Vulkan
API.
</para>
@ -52,7 +52,7 @@
<title>Installation of Vulkan-Headers</title>
<para>
Install <application>Vulkan-Headers</application> by running the following
Install Vulkan-Headers by running the following
commands:
</para>

6
archive/wireplumber.xml
View File

@ -21,8 +21,8 @@
<title>Introduction to Wireplumber</title>
<para>
The <application>Wireplumber</application> package contains a session and
policy manager for <application>Pipewire</application>.
The Wireplumber package contains a session and
policy manager for Pipewire.
</para>
<itemizedlist spacing="compact">
@ -58,7 +58,7 @@
<title>Installation of Wireplumber</title>
<para>
Install <application>Wireplumber</application> by running the following
Install Wireplumber by running the following
commands:
</para>

6
archive/x7legacy.xml
View File

@ -46,11 +46,11 @@
<title>Introduction to Xorg Legacy</title>
<para>
<application>Xorg</application>&apos;s ancestor (X11R1, in 1987) at
Xorg&apos;s ancestor (X11R1, in 1987) at
first only provided bitmap fonts, with a tool
(<command>bdftopcf</command>) to assist in their installation. With the
introduction of <application>xorg-server-1.19.0</application> and
<application>libXfont2</application> many people will not need them.
introduction of xorg-server-1.19.0 and
libXfont2 many people will not need them.
There are still a few old packages which might require, or benefit from,
these deprecated fonts and so the following packages are shown here.
</para>

4
archive/xclock.xml
View File

@ -26,7 +26,7 @@
<title>Introduction to xclock</title>
<para>
The <application>xclock</application> package contains a simple
The xclock package contains a simple
clock application which is used in the default xinit configuration.
</para>
@ -82,7 +82,7 @@
<title>Installation of xclock</title>
<para>
Install <application>xclock</application> by running the
Install xclock by running the
following commands:
</para>

6
archive/xterm.xml
View File

@ -26,7 +26,7 @@
<title>Introduction to xterm</title>
<para>
<application>xterm</application> is a terminal emulator for
xterm is a terminal emulator for
the X Window System.
</para>
@ -97,7 +97,7 @@
<title>Installation of xterm</title>
<para>
Install <application>xterm</application> by running the
Install xterm by running the
following commands:
</para>
@ -155,7 +155,7 @@ cp -v *.desktop /usr/share/applications/</userinput></screen>
<para>
<command>make install-ti</command>: This command installs corrected
terminfo description files for use with
<application>xterm</application>.
xterm.
</para>
-->
</sect2>

4
book/bookinfo.xml
View File

@ -49,8 +49,8 @@
<abstract>
<para>
This book introduces and guides the reader through additions to the
system like <application>Steam</application>,
<application>Wine</application>, and their dependencies after the
system like Steam,
Wine, and their dependencies after the
LFS or Multilib-LFS book on x86_64 systems.
</para>
</abstract>

22
book/organization.xml
View File

@ -26,28 +26,26 @@
<para>
This section is dedicated to covering dependencies that are shared
between <application>Steam</application> and <application>Wine.
</application> As it turns out, there are quite a lot of
dependencies they both depend on. Anything specific to <application>
Steam</application> and <application>Wine</application> are covered
in their respective chapters.
between Steam and Wine. As it turns out, there are quite a lot of
dependencies they both depend on. Anything specific to Steam and
Wine are covered in their respective chapters.
</para>
<bridgehead renderas="sect2">Part III - Steam</bridgehead>
<para>
This part details how to install <application>Steam</application>
and the linear line of dependencies required, as well as some
configuration for certain packages.
This part details how to install Steam and the linear line of
dependencies required, as well as some configuration for certain
packages.
</para>
<bridgehead renderas="sect2">Part IV - Wine</bridgehead>
<para>
This section goes over installing a toolchain called <application>
MinGW-w64</application>, some of the packages necessary to both compile
<application>Wine</application> and use it, and lastly how to compile
<application>Wine</application> and configure it.
This section goes over installing a toolchain called
MinGW-w64, some of the packages necessary to both compile
Wine and use it, and lastly how to compile
Wine and configure it.
</para>
<bridgehead renderas="sect2">Part V - Quality of Life</bridgehead>

12
book/preface.xml
View File

@ -12,11 +12,11 @@
<para>
Sometime after my first install of LFS, I had a question that others had:
how do I install <application>Steam</application> on this system? I kept
how do I install Steam on this system? I kept
that thought in the back of my head as I went for Beyond LFS, a book that
covered a good number of packages I needed. However, the issue of
<application>Steam</application> was not cleared up yet. So I just tried to
install the <application>Steam</application> tarball. Because I did not
Steam was not cleared up yet. So I just tried to
install the Steam tarball. Because I did not
have 32-bit libraries, this ended in failure.
</para>
@ -34,12 +34,12 @@
Rahul Chandra in the same thread mentioned his scripts for his distro,
Tucana. These scripts gave me a basic idea of how to do lib32 installations
for BLFS packages which were necessary for
<application>Steam.</application>. While this wasn't exactly difficult,
Steam.. While this wasn't exactly difficult,
it was a big timesink as I had to manually type in all the lib32
compilation options to successfully build 32-bit libraries. Even after
having built all the 32-bit libraries required, a few more fixes and files
were necessary. After about a week, I managed to get
<application>Steam</application> working. I realized that this was a lot of
Steam working. I realized that this was a lot of
work, and many users who'd want to do the same thing would get stuck and
not know what to do. In the worst case, they'd give up before even reaching
their goal. I had made a pretty lackluster <ulink
@ -54,7 +54,7 @@
Sometime afterwards, I decided to do a <ulink
url="https://www.youtube.com/playlist?list=PL_vcsK5qbWSv-70zpfFcol_D9yovtf6N6">stream
series</ulink> that included that installation of
<application>Wine</application>, not just <application>Steam</application>.
Wine, not just Steam.
My general idea was to compile all the stream footage (roughly 40 GB worth)
into a single video master guide. When some time passed, I came to the
conclusion that for a installation guide for two complex packages on an LFS

4
book/whoread.xml
View File

@ -13,8 +13,8 @@
<para>
This book is aimed towards users who want to use a system following
the Linux From Scratch book but also want to use <application>Steam
</application> and/or <application>Wine</application>.
the Linux From Scratch book but also want to use Steam
and/or Wine.
The official Linux From Scratch and Beyond Linux From Scratch books
do not support these two packages. However, users should still have
both the choice and an easy to follow guide to get these packages

10
introduction/multilib/mesonfiles.xml
View File

@ -15,16 +15,16 @@
<title>Introduction to Meson Toolchain Files</title>
<para>
Most applications that rely on the <application>Meson</application>
Most applications that rely on the Meson
build system have decent support for cross compilation, ie. compiling
32-bit binaries on a 64-bit system. It can be as easy as setting the
<envar>CC</envar>, <envar>CXX</envar>, and <envar>PKG_CONFIG_PATH
</envar> variables before using the <userinput>meson setup ..
</userinput> command to compile 32-bit binaries on a 64-bit system.
However, some projects are more complicated for many different
reasons, leading to the necessity of <application>Meson
</application> toolchain files. They specify compilers,
options that should be invoked, the <application>pkg-conf</application>
reasons, leading to the necessity of Meson
toolchain files. They specify compilers,
options that should be invoked, the pkg-conf
binary (or rather symlink that uses a certain personality file) to use,
<command>llvm-config</command> to use, etc. This is required for many
Meson projects, especially if you have followed BLFS before this book.
@ -32,7 +32,7 @@
</para>
<para>
There are two <application>Meson</application> files: the cross
There are two Meson files: the cross
toolchain file and the native toolchain file. There are different situations
for using either.
</para>

14
introduction/welcome/rationale.xml
View File

@ -27,8 +27,8 @@
the book but rather in the BLFS book. There are multiple reasons
for this, but the most notable one is the packages that aren't in
the book aren't important for the main packages in the book, those
being <application>Steam</application> and
<application>Wine</application>. They are still listed anyway if users
being Steam and
Wine. They are still listed anyway if users
want more support out of the specific packages not specific to the main
packages, like media playback for example. Another reason for
packages not being in the book is that the packages take a lot
@ -64,10 +64,10 @@
<!--
<para>
<xref linkend="mingw-w64-binutils"/>: While
<application>Binutils</application>-2.44 exists and can be installed
Binutils-2.44 exists and can be installed
without issue, on the MinGW-w64 side of things, <xref linkend="wine"/>
is incompatible with <application>MinGW-w64-Binutils</application>-2.44.
Mismatched <application>Binutils</application> versions are fine granted
is incompatible with MinGW-w64-Binutils-2.44.
Mismatched Binutils versions are fine granted
that one toolchain's version does not match with another but separate
toolchain's.
</para>
@ -75,8 +75,8 @@
<!--
<para>
<xref linkend="nvidia"/>: Newer versions of <application>NVIDIA
</application> have many issues. For example, the newest version demands
<xref linkend="nvidia"/>: Newer versions of NVIDIA
have many issues. For example, the newest version demands
that users disable framebuffer emulation support in the kernel in order
to install and use the driver. The one before that requires a
<command>sed</command> command after extraction of the runfile.

2
introduction/welcome/welcome.xml
View File

@ -17,7 +17,7 @@
almost command by command unless otherwise told so, and BLFS
has packages scattered throughout in chapters, only certain
ones meant to be followed through, such as
<application>Xorg</application>.
Xorg.
</para>
<para>

10
introduction/welcome/which.xml
View File

@ -34,8 +34,8 @@
<para>
The following section is Shared Dependencies. Every user
who wants <application>Steam</application> and/or
<application>Wine</application> will want to read this chapter
who wants Steam and/or
Wine will want to read this chapter
as both projects use the packages. Most of this chapter is
necessary. However, it is recommended to check the dependency
lists of Steam and Wine to see what exactly you need from a
@ -47,7 +47,7 @@
<para>
The next section is Steam, which covers all the packages,
patches, configuration, and setup necessary to get
<application>Steam</application> working and capable of the
Steam working and capable of the
playing the following: Linux games, Windows games via Proton,
and games using OpenGL, Vulkan, and Direct3D.
</para>
@ -55,11 +55,11 @@
<para>
The following section that most users will need is Wine. Users
should follow every step in this chapter if they want to install
WoW64 <application>Wine</application>, but more information is covered
WoW64 Wine, but more information is covered
in that chapter. The Wine chapter at the moment does not consider
retrofitting and will handle it in a similar manner to Arch: build the
MinGW-w64 toolchain, install the audio and video components, then finally
<application>Wine</application> itself.
Wine itself.
</para>
<para>

6
qol/binary.xml
View File

@ -12,8 +12,8 @@
<title>Binary Support</title>
<para>
Now that have <application>Steam</application> and/or
<application>Wine</application>, you now have decent support for running
Now that have Steam and/or
Wine, you now have decent support for running
binary only applications. However, there are AppImages and Flatpaks. This
book does not and will not go over how to get that support. However, you
can figure out how to get that support by looking at another project the
@ -27,7 +27,7 @@
<para>
After following the instructions, you should be able to run AppImages and
use Flatpak. You can even use Flatpak to install
<application>Steam</application> if you wish. That method is not covered in
Steam if you wish. That method is not covered in
this book.
</para>

4
qol/qolintro.xml
View File

@ -12,8 +12,8 @@
<title>Quality of Life</title>
<para>
Now that you have installed <application>Steam</application>, <application>
Wine</application>, or both, you may be satisfied with your current setup.
Now that you have installed Steam,
Wine, or both, you may be satisfied with your current setup.
However, there are some quality of life improvements that may be of use to
you. This chapter goes through a handful of those improvements.
</para>

10
shareddeps/audio/alsa-lib.xml
View File

@ -22,9 +22,9 @@
<title>Introduction to ALSA Library</title>
<para>
The <application>ALSA Library</application> package contains
the ALSA library used by programs (including <application>ALSA
Utilities</application>) requiring access to the ALSA sound
The ALSA Library package contains
the ALSA library used by programs (including ALSA
Utilities) requiring access to the ALSA sound
interface.
</para>
@ -115,7 +115,7 @@ esac</userinput></screen>
-->
<para>
Install <application>ALSA Library</application> by
Install ALSA Library by
running the following commands:
</para>
@ -123,7 +123,7 @@ esac</userinput></screen>
make</userinput></screen>
<para>
If you have <application>Doxygen</application> installed and you wish to
If you have Doxygen installed and you wish to
build the library API documentation, run the following
commands from the top-level directory of the source tree:
</para>

16
shareddeps/audio/alsa-plugins.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to ALSA Plugins</title>
<para>
The <application>ALSA Plugins</application> package contains
The ALSA Plugins package contains
plugins for various audio libraries and sound servers.
</para>
@ -65,7 +65,7 @@
<title>Installation of ALSA Plugins</title>
<para>
Install <application>ALSA Plugins</application> by
Install ALSA Plugins by
running the following commands:
</para>
@ -88,7 +88,7 @@ make</userinput></screen>
<title>lib32 Installation of ALSA Plugins</title>
<para>
Install 32-bit <application>ALSA Plugins</application> by
Install 32-bit ALSA Plugins by
running the following commands:
</para>
@ -170,8 +170,8 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libasound_module_pcm_oss</filename></term>
<listitem>
<para>
Allows native <application>ALSA</application> applications to
run on <application>OSS</application>
Allows native ALSA applications to
run on OSS
</para>
<indexterm zone="alsa-plugins libasound_module_pcm_oss">
<primary sortas="c-libasound_module_pcm_oss">libasound_module_pcm_oss</primary>
@ -208,7 +208,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libasound_module_pcm_jack</filename></term>
<listitem>
<para>
Allows native <application>ALSA</application> applications to
Allows native ALSA applications to
work with <command>jackd</command>
</para>
<indexterm zone="alsa-plugins libasound_module_pcm_jack">
@ -221,8 +221,8 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libasound_module_pcm_pulse</filename></term>
<listitem>
<para>
Allows native <application>ALSA</application> applications
to access a <application>PulseAudio</application> sound
Allows native ALSA applications
to access a PulseAudio sound
daemon
</para>
<indexterm zone="alsa-plugins libasound_module_pcm_pulse">

10
shareddeps/audio/alsa-utils.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to ALSA Utilities</title>
<para>
The <application>ALSA Utilities</application> package contains
The ALSA Utilities package contains
various utilities which are useful for controlling your sound
card.
</para>
@ -78,7 +78,7 @@
-->
<para>
Install <application>ALSA Utilities</application> by
Install ALSA Utilities by
running the following commands:
</para>
@ -109,7 +109,7 @@ make</userinput></screen>
<para>
<parameter>--disable-alsaconf</parameter>: This switch disables building
the <command>alsaconf</command> configuration tool which is incompatible
with <application>Udev</application>.
with Udev.
</para>
<para>
@ -166,7 +166,7 @@ make</userinput></screen>
<para>
The <filename>alsactl</filename> program is normally run from a
standard <application>udev</application> rule. The first time it
standard udev rule. The first time it
is run, it will complain that there is no state in
<filename>/var/lib/alsa/asound.state</filename>. You can prevent
this by running the following command as the
@ -177,7 +177,7 @@ make</userinput></screen>
<para>
The volume settings should be restored from the saved state by
<application>Udev</application> when the device is detected
Udev when the device is detected
(during boot or when plugged in for USB devices).
</para>
<!-- not needed with elogind or systemd-logind

8
shareddeps/audio/flac.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to FLAC</title>
<para>
<application>FLAC</application> is an audio CODEC similar to
FLAC is an audio CODEC similar to
MP3, but lossless, meaning that audio is compressed without losing any
information.
</para>
@ -69,7 +69,7 @@
<title>Installation of FLAC</title>
<para>
Install <application>FLAC</application> by running the
Install FLAC by running the
following commands:
</para>
@ -100,7 +100,7 @@ make</userinput></screen>
<title>lib32 Installation of FLAC</title>
<para>
Install lib32-<application>FLAC</application> by running the
Install lib32-FLAC by running the
following commands:
</para>
@ -204,7 +204,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libxmms-flac.{so,a}</filename></term>
<listitem>
<para>
is a plugin for <application>XMMS</application>.
is a plugin for XMMS.
</para>
<indexterm zone="flac libxmms-flac">
<primary sortas="c-libxmms-flac">libxmms-flac.{so,a}</primary>

6
shareddeps/audio/libogg.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to libogg</title>
<para>
The <application>libogg</application> package contains the Ogg file
The libogg package contains the Ogg file
structure. This is useful for creating (encoding) or playing (decoding) a
single physical bit stream.
</para>
@ -46,7 +46,7 @@
<title>Installation of libogg</title>
<para>
Install <application>libogg</application> by running the following
Install libogg by running the following
commands:
</para>
@ -72,7 +72,7 @@ make</userinput></screen>
<title>lib32 Installation of libogg</title>
<para>
Install lib32-<application>libogg</application> by running the following
Install lib32-libogg by running the following
commands:
</para>

8
shareddeps/audio/libsndfile.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to libsndfile</title>
<para>
<application>Libsndfile</application> is a library of C routines for
Libsndfile is a library of C routines for
reading and writing files containing sampled audio data.
</para>
@ -69,7 +69,7 @@
<screen><userinput>sed '/typedef enum/,/bool ;/d' -i src/ALAC/alac_{en,de}coder.c</userinput></screen>
<para>
Install <application>libsndfile</application> by running the following
Install libsndfile by running the following
commands:
</para>
@ -93,7 +93,7 @@ make</userinput></screen>
<title>lib32 Installation of libsndfile</title>
<para>
Install lib32-<application>libsndfile</application> by running the following
Install lib32-libsndfile by running the following
commands:
</para>
@ -280,7 +280,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libsndfile</filename></term>
<listitem>
<para>
contains the <application>libsndfile</application> API functions
contains the libsndfile API functions
</para>
<indexterm zone="libsndfile libsndfile-lib">
<primary sortas="c-libsndfile">libsndfile</primary>

6
shareddeps/audio/libvorbis.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to libvorbis</title>
<para>
The <application>libvorbis</application> package contains a general
The libvorbis package contains a general
purpose audio and music encoding format. This is useful for creating
(encoding) and playing (decoding) sound in an open (patent free)
format.
@ -70,7 +70,7 @@
<screen><userinput>sed -i '/components.png \\/{n;d}' doc/Makefile.in</userinput></screen>
-->
<para>
Install <application>libvorbis</application> by running the following
Install libvorbis by running the following
commands:
</para>
@ -94,7 +94,7 @@ install -v -m644 doc/Vorbis* /usr/share/doc/libvorbis-&libvorbis-version;</useri
<title>lib32 Installation of libvorbis</title>
<para>
Install lib32-<application>libvorbis</application> by running the following
Install lib32-libvorbis by running the following
commands:
</para>

6
shareddeps/audio/opus.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Opus</title>
<para>
<application>Opus</application> is a lossy audio compression format
Opus is a lossy audio compression format
developed by the Internet Engineering Task Force (IETF) that is
particularly suitable for interactive speech and audio transmission over
the Internet. This package provides the Opus development library and
@ -55,7 +55,7 @@
<title>Installation of Opus</title>
<para>
Install <application>Opus</application> by running the following
Install Opus by running the following
commands:
</para>
@ -84,7 +84,7 @@ ninja</userinput></screen>
<title>lib32 Installation of Opus</title>
<para>
Install lib32-<application>Opus</application> by running the following
Install lib32-Opus by running the following
commands:
</para>

40
shareddeps/audio/pulseaudio.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to PulseAudio</title>
<para>
<application>PulseAudio</application> is a sound system for POSIX OSes,
PulseAudio is a sound system for POSIX OSes,
meaning that it is a proxy for sound applications. It allows you to do
advanced operations on your sound data as it passes between your
application and your hardware. Things like transferring the audio to a
@ -100,7 +100,7 @@
<screen><userinput>sed '/doxygen/d' -i meson.build</userinput></screen>
-->
<para>
Install <application>PulseAudio</application> by running the following
Install PulseAudio by running the following
commands:
</para>
@ -129,7 +129,7 @@ ninja</userinput></screen>
url="https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/"/>
for more information.
While still as the <systemitem class="username">root</systemitem>
user, remove the <application>D-Bus</application> configuration file
user, remove the D-Bus configuration file
for the system wide daemon to avoid creating unnecessary system
users and groups:
</para>
@ -142,7 +142,7 @@ ninja</userinput></screen>
<title>lib32 Installation of PulseAudio</title>
<para>
Install lib32-<application>PulseAudio</application> by running the following
Install lib32-PulseAudio by running the following
commands:
</para>
@ -191,7 +191,7 @@ ldconfig</userinput></screen>
<para>
<parameter>-D tests=false</parameter>: This switch disables building
tests as they require <application>Check</application>.
tests as they require Check.
</para>
<!--
@ -252,7 +252,7 @@ ldconfig</userinput></screen>
-->
<para>
You may have to configure the audio system. You can start
<application>pulseaudio</application> in command line mode using
pulseaudio in command line mode using
<command>pulseaudio -C</command> and then list various
information and change settings. See
<command>man pulse-cli-syntax</command>.
@ -270,14 +270,14 @@ ldconfig</userinput></screen>
<screen role="root"><userinput>usermod -a -G audio <replaceable>&lt;username&gt;</replaceable></userinput></screen>
<para>
If <application>pulseaudio</application> was working but you no-longer
If pulseaudio was working but you no-longer
have sound, after checking for hardware issues (speakers or headphones
not connected, external amplifier not connected) you may need to fix it.
</para>
<para>
One suggestion is to close the application, such as
<application>firefox</application> where sound has stopped working, then
firefox where sound has stopped working, then
run: <command>pactl list short sinks</command> followed by:
<command>pacmd set-default-sink &lt;sink #&gt;</command> and then
restart the application.
@ -344,7 +344,7 @@ ldconfig</userinput></screen>
<term><command>esdcompat</command></term>
<listitem>
<para>
is the <application>PulseAudio</application> ESD wrapper script.
is the PulseAudio ESD wrapper script.
</para>
<indexterm zone="pulseaudio esdcompat">
<primary sortas="b-esdcompat">esdcompat</primary>
@ -358,7 +358,7 @@ ldconfig</userinput></screen>
<listitem>
<para>
plays back or records raw or encoded audio streams on a
<application>PulseAudio</application> sound server
PulseAudio sound server
</para>
<indexterm zone="pulseaudio pacat">
<primary sortas="b-pacat">pacat</primary>
@ -370,7 +370,7 @@ ldconfig</userinput></screen>
<term><command>pacmd</command></term>
<listitem>
<para>
is a tool used to reconfigure a <application>PulseAudio</application>
is a tool used to reconfigure a PulseAudio
sound server during runtime
</para>
<indexterm zone="pulseaudio pacmd">
@ -383,7 +383,7 @@ ldconfig</userinput></screen>
<term><command>pactl</command></term>
<listitem>
<para>
is used to control a running <application>PulseAudio</application>
is used to control a running PulseAudio
sound server
</para>
<indexterm zone="pulseaudio pactl">
@ -396,7 +396,7 @@ ldconfig</userinput></screen>
<term><command>padsp</command></term>
<listitem>
<para>
is the <application>PulseAudio</application> OSS Wrapper
is the PulseAudio OSS Wrapper
</para>
<indexterm zone="pulseaudio padsp">
<primary sortas="b-padsp">padsp</primary>
@ -421,7 +421,7 @@ ldconfig</userinput></screen>
<listitem>
<para>
is used to play audio files on a
<application>PulseAudio</application> sound server
PulseAudio sound server
</para>
<indexterm zone="pulseaudio paplay">
<primary sortas="b-paplay">paplay</primary>
@ -458,7 +458,7 @@ ldconfig</userinput></screen>
<listitem>
<para>
is a tool that can be used to tell a local
<application>PulseAudio</application> sound server to temporarily
PulseAudio sound server to temporarily
suspend access to the audio devices, to allow other applications
to access them directly
</para>
@ -472,7 +472,7 @@ ldconfig</userinput></screen>
<term><command>pax11publish</command></term>
<listitem>
<para>
is the <application>PulseAudio</application>
is the PulseAudio
X11 Credential Utility
</para>
<indexterm zone="pulseaudio pax11publish">
@ -486,7 +486,7 @@ ldconfig</userinput></screen>
<listitem>
<para>
is a shell script that prints various information relating to the
<application>Pulseaudio</application> server currently in use
Pulseaudio server currently in use
</para>
<indexterm zone="pulseaudio pa-info">
<primary sortas="b-pa-info">pa-info</primary>
@ -512,7 +512,7 @@ ldconfig</userinput></screen>
<listitem>
<para>
is an equalizer interface for
<application>PulseAudio</application> equalizer sinks
PulseAudio equalizer sinks
(Requires fftw at build time)
</para>
<indexterm zone="pulseaudio qpaeq">
@ -526,7 +526,7 @@ ldconfig</userinput></screen>
<term><command>start-pulseaudio-kde</command></term>
<listitem>
<para>
Starts <application>PulseAudio</application> and loads
Starts PulseAudio and loads
module-device-manager to use KDE routing policies.
</para>
<indexterm zone="pulseaudio start-pulseaudio-kde">
@ -539,7 +539,7 @@ ldconfig</userinput></screen>
<term><command>start-pulseaudio-x11</command></term>
<listitem>
<para>
starts <application>PulseAudio</application> and registers it to
starts PulseAudio and registers it to
the X11 session manager
</para>
<indexterm zone="pulseaudio start-pulseaudio-x11">

12
shareddeps/audio/speex.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Speex</title>
<para>
<application>Speex</application> is an audio compression format
Speex is an audio compression format
designed specifically for speech. It is well-adapted to internet
applications and provides useful features that are not present in most
other CODECs.
@ -76,7 +76,7 @@
</para>
<para>
Install <application>Speex</application> by running the
Install Speex by running the
following commands:
</para>
@ -121,7 +121,7 @@ popd</userinput></screen>
<title>lib32 Installation of Speex</title>
<para>
Install lib32-<application>Speex</application> by running the
Install lib32-Speex by running the
following commands:
</para>
@ -216,7 +216,7 @@ popd</userinput></screen>
<term><command>speexdec</command></term>
<listitem>
<para>
decodes a <application>Speex</application> file and
decodes a Speex file and
produces a WAV or raw file
</para>
<indexterm zone="speex speexdec">
@ -229,7 +229,7 @@ popd</userinput></screen>
<term><command>speexenc</command></term>
<listitem>
<para>
encodes a WAV or raw file using <application>Speex</application>
encodes a WAV or raw file using Speex
</para>
<indexterm zone="speex speexenc">
<primary sortas="b-speexenc">speexenc</primary>
@ -254,7 +254,7 @@ popd</userinput></screen>
<listitem>
<para>
is a speech processing library that goes along with the
<application>Speex</application> codec
Speex codec
</para>
<indexterm zone="speex libspeexdsp">
<primary sortas="c-libspeexdsp">libspeexdsp.so</primary>

42
shareddeps/checkpoint/whatnow.xml
View File

@ -27,7 +27,7 @@
and not accidentally lock yourself inside of it without a hard reboot. The
installation of those components is not covered in this book, as the
specific components will depend on if you plan to use
<application>X11</application>, <application>Wayland</application>, or
X11, Wayland, or
both. This page acts as a simple nudge to help point you in the right
direction. When you are done setting up your graphical environment, you can
come back and continue with the next chapters.
@ -53,7 +53,7 @@
It is recommended to read up on the BLFS page <ulink
url="&blfs-svn;/x/xorg-config.html">Xorg-7 Testing and
Configuration</ulink>. It is pretty comprehensive. However, using <xref
linkend="nvidia"/> with <application>X11</application> requires a
linkend="nvidia"/> with X11 requires a
slightly different setup, and there may be extra information you wish to
know.
</para>
@ -63,9 +63,9 @@
<para>
Using a conventional <filename>/etc/X11/xorg.conf</filename>
can lead to issues, if <application>X11</application> manages to
even start. In order to use the <application>NVIDIA</application>
driver when starting <application>X11</application>, run the following
can lead to issues, if X11 manages to
even start. In order to use the NVIDIA
driver when starting X11, run the following
command as the &root; user:
</para>
@ -118,8 +118,8 @@
<para>
If you compiled Zink in <xref linkend="mesa"/>, chances are
<application>X11</application> or any
<application>Wayland</application> compositors will use the Gallium3D
X11 or any
Wayland compositors will use the Gallium3D
driver meant for your GPU specifically. You can override this by
setting the following variable:
</para>
@ -242,7 +242,7 @@
A compositor talks with <xref linkend="xorg-server"/> and can change
what is seen on screen. Compositors can add animations, borders,
shadows, opacity, etc. to windows. They can also enable vsync.
Though compositors aren't needed on <application>X11</application>,
Though compositors aren't needed on X11,
they make the graphical environment look nicer. These visual
enhancements can be GPU-intensive if the GPU is weak or the graphics
driver isn't that performant<footnote><para>If you decide to use a
@ -276,9 +276,9 @@
<title>Wayland</title>
<para>
Wayland is much simpler to set up than <application>X11</application>.
Wayland is much simpler to set up than X11.
You should still read the X11 section above, as much of the information
is also relevant to <application>Wayland</application>. There are a few
is also relevant to Wayland. There are a few
changes, however.
</para>
@ -288,10 +288,10 @@
<para>
You will only need to worry about the refresh rate if it's
applicable to you. You won't need to worry about making sure the
<application>NVIDIA</application> driver is used when starting
<application>Wayland</application>. However, read through the
NVIDIA driver is used when starting
Wayland. However, read through the
installation instructions for your chosen graphical environment, as
they may have information regarding <application>NVIDIA</application>.
they may have information regarding NVIDIA.
Results can be shotty, and sometimes the environment won't be able to
start. Do your research first.
</para>
@ -302,9 +302,9 @@
<title>Window Managers, Desktop Environments, and Compositors</title>
<para>
Unlike on <application>X11</application>, the window manager and
Unlike on X11, the window manager and
compositor will always be combined on
<application>Wayland</application>. Minimal graphical environments are
Wayland. Minimal graphical environments are
called compositors instead of window managers, but desktop environments
are still called desktop environments. For compositors, the only
additional components that need to be installed are a terminal and
@ -315,10 +315,10 @@
<title>Compositors</title>
<para>
Many <application>X11</application> window managers do not support
<application>Wayland</application>. There are some unofficial
Many X11 window managers do not support
Wayland. There are some unofficial
ports that use certain reusable frameworks which would
be called an <application>X11</application> compositor, like
be called an X11 compositor, like
<ulink url="https://gitlab.freedesktop.org/wlroots/wlroots/">
wlroots</ulink> (these are called compositor libraries). You can
try some ports if you wish but some of them do their own thing
@ -326,7 +326,7 @@
</para>
<para>
Native <application>Wayland</application> compositors include
Native Wayland compositors include
<ulink url="&slfs-website;/wm/hypr.html">Hyprland</ulink>,
<ulink url="https://github.com/swaywm/sway">Sway</ulink>, and
<ulink url="&slfs-website;/wm/wf.html">Wayfire</ulink>.
@ -342,8 +342,8 @@
<para>
Go with <ulink url="&blfs-svn;/gnome/gnome.html">GNOME</ulink> or
<ulink url="&blfs-svn;/kde/kde.html">KDE Plasma</ulink>. They have
good <application>Wayland</application> support. Like with
<application>X11</application>, you can launch these using a display
good Wayland support. Like with
X11, you can launch these using a display
manager.
</para>

14
shareddeps/dps/basicx/other/cmake.xml
View File

@ -21,11 +21,11 @@
<title>Introduction to CMake</title>
<para>
The <application>CMake</application> package contains a modern
The CMake package contains a modern
toolset used for generating Makefiles. It is a successor of the
auto-generated <command>configure</command> script and aims to
be platform- and compiler-independent. A significant user of
<application>CMake</application> is <application>KDE</application>
CMake is KDE
since version 4.
</para>
@ -87,7 +87,7 @@
-->
<para>
Install <application>CMake</application> by running the following
Install CMake by running the following
commands:
</para>
@ -156,13 +156,13 @@ make</userinput></screen>
<para>
<parameter>--no-system-jsoncpp</parameter> and
<parameter>--no-system-cppdap</parameter>: These switches remove the
<application>JSON-C++</application> library from the list of system
JSON-C++ library from the list of system
libraries. A bundled version of that library is used instead.
</para>
<para>
<parameter>--no-system-librhash</parameter>: This switch removes the
<application>librhash</application> library from the list of system
librhash library from the list of system
libraries used. A bundled version of that library is used instead.
</para>
@ -174,7 +174,7 @@ make</userinput></screen>
<para>
<option>--parallel=</option>: This switch enables performing the
<application>CMake</application> bootstrap with multiple jobs
CMake bootstrap with multiple jobs
at one time.
</para>
@ -237,7 +237,7 @@ make</userinput></screen>
<term><command>cpack</command></term>
<listitem>
<para>
is the <application>CMake</application> packaging program
is the CMake packaging program
</para>
<indexterm zone="cmake cpack">
<primary sortas="b-cpack">cpack</primary>

26
shareddeps/dps/basicx/other/dbus.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to D-Bus</title>
<para revision="systemd">
Even though <application>D-Bus</application> was built in LFS, there are
Even though D-Bus was built in LFS, there are
some features provided by the package that other GLFS packages need, but
their dependencies didn't fit into LFS.
</para>
@ -128,7 +128,7 @@
<para>
If any packages install a
<application>D-Bus</application> <filename>.service</filename>
D-Bus <filename>.service</filename>
file outside of the standard <filename
class="directory">/usr/share/dbus-1/services</filename> directory,
that directory should be added to the local session configuration.
@ -171,8 +171,8 @@ EOF</userinput></screen>
<para revision="sysv">
Note that this boot script only starts the system-wide
<application>D-Bus</application> daemon. Each user requiring access to
<application>D-Bus</application> services will also need to run a
D-Bus daemon. Each user requiring access to
D-Bus services will also need to run a
session daemon as well. There are many methods you can use to start a
session daemon using the <command>dbus-launch</command> command. Review
the <command>dbus-launch</command> man page for details about the
@ -295,7 +295,7 @@ kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
<term><command>dbus-daemon</command></term>
<listitem>
<para>
is the <application>D-Bus</application> message bus daemon
is the D-Bus message bus daemon
</para>
<indexterm zone="dbus dbus-daemon">
<primary sortas="b-dbus-daemon">dbus-daemon</primary>
@ -322,7 +322,7 @@ kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
<listitem>
<para>
is used to monitor messages going through a
<application>D-Bus</application> message bus
D-Bus message bus
</para>
<indexterm zone="dbus dbus-monitor">
<primary sortas="b-dbus-monitor">dbus-monitor</primary>
@ -334,7 +334,7 @@ kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
<term><command>dbus-run-session</command></term>
<listitem>
<para>
starts a process as a new <application>D-Bus</application> session
starts a process as a new D-Bus session
</para>
<indexterm zone="dbus dbus-run-session">
<primary sortas="b-dbus-run-session">dbus-run-session</primary>
@ -346,7 +346,7 @@ kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
<term><command>dbus-send</command></term>
<listitem>
<para>
is used to send a message to a <application>D-Bus</application>
is used to send a message to a D-Bus
message bus
</para>
<indexterm zone="dbus dbus-send">
@ -359,9 +359,9 @@ kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
<term><command>dbus-test-tool</command></term>
<listitem>
<para>
is a <application>D-Bus</application> traffic generator and test
is a D-Bus traffic generator and test
tool; it is a multi-purpose tool for debugging and profiling
<application>D-Bus</application>
D-Bus
</para>
<indexterm zone="dbus dbus-test-tool">
<primary sortas="b-dbus-test-tool">dbus-test-tool</primary>
@ -374,7 +374,7 @@ kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
<listitem>
<para>
is used to update the environment used for
<application>D-Bus</application> session services;
D-Bus session services;
it updates the list of environment variables used by
<command>dbus-daemon --session</command> when it activates session
services without using systemd
@ -403,8 +403,8 @@ kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
<listitem>
<para>
contains the API functions used by the
<application>D-Bus</application> message daemon.
<application>D-Bus</application> is first a library that provides
D-Bus message daemon.
D-Bus is first a library that provides
one-to-one communication between any two applications;
<command>dbus-daemon</command> is an application that uses this
library to implement a message bus daemon

16
shareddeps/dps/basicx/other/fontconfig.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to Fontconfig</title>
<para>
The <application>Fontconfig</application> package contains
The Fontconfig package contains
a library and support programs used for configuring and
customizing font access.
</para>
@ -70,7 +70,7 @@
<title>Installation of Fontconfig</title>
<para>
Install <application>Fontconfig</application> by running the following
Install Fontconfig by running the following
commands:
</para>
@ -98,7 +98,7 @@ ninja</userinput></screen>
<title>lib32 Installation of Fontconfig</title>
<para>
Install lib32-<application>Fontconfig</application> by running the
Install lib32-Fontconfig by running the
following commands:
</para>
@ -161,7 +161,7 @@ ldconfig</userinput></screen>
<title>Configuration Information</title>
<para>
The main configuration file for <application>Fontconfig</application> is
The main configuration file for Fontconfig is
<filename>/etc/fonts/fonts.conf</filename>. Generally you do not want
to edit this file. It will also read <filename>/etc/fonts/local.conf</filename>
and any files in <filename class="directory">/etc/fonts/conf.d</filename>.
@ -169,7 +169,7 @@ ldconfig</userinput></screen>
(or update) the <filename>/etc/fonts/local.conf</filename> file with your
local information or add a new file in
<filename class="directory">/etc/fonts/conf.d</filename>. The default
location of fonts in <application>Fontconfig</application> is:
location of fonts in Fontconfig is:
</para>
<itemizedlist spacing="compact">
@ -192,7 +192,7 @@ ldconfig</userinput></screen>
</itemizedlist>
<para>
<application>Fontconfig</application> also ships many example
Fontconfig also ships many example
configuration files in the
<filename class="directory">/usr/share/fontconfig/conf.avail</filename>
directory. Symlinking specific files to
@ -211,7 +211,7 @@ ldconfig</userinput></screen>
</indexterm>
<para>
More information about configuring <application>Fontconfig</application>
More information about configuring Fontconfig
can be found in the user's manual in <ulink
url="file:///usr/share/doc/fontconfig-&fontconfig-version;/fontconfig-user.html"/>.
</para>
@ -366,7 +366,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libfontconfig</filename></term>
<listitem>
<para>
contains functions used by the <application>Fontconfig</application>
contains functions used by the Fontconfig
programs and also by other programs to configure or customize font
access
</para>

14
shareddeps/dps/basicx/other/freetype2-pass1.xml
View File

@ -25,15 +25,15 @@
<title>Introduction to FreeType2 - Pass 1</title>
<para>
The <application>FreeType2</application> package contains
The FreeType2 package contains
a library which allows applications to properly render
<application>TrueType</application> fonts.
TrueType fonts.
</para>
<para>
This package has a circular dependency on <xref
linkend="harfbuzz"/>, so this package must be installed first,
<application>harfBuzz</application> second, then lastly this
harfBuzz second, then lastly this
package again. This is the first pass.
</para>
@ -132,9 +132,9 @@ rm -v /usr/share/doc/freetype-&freetype2-version;/freetype-config.1</userinput><
<para>
<option>--without-harfbuzz</option>: If
<application>harfbuzz</application> is installed prior to
<application>freetype</application> without
<application>freetype</application> support, use this switch to avoid a
harfbuzz is installed prior to
freetype without
freetype support, use this switch to avoid a
build failure.
</para>
@ -182,7 +182,7 @@ rm -v /usr/share/doc/freetype-&freetype2-version;/freetype-config.1</userinput><
<term><command>freetype-config</command></term>
<listitem>
<para>
is used to get <application>FreeType</application> compilation
is used to get FreeType compilation
and linking information
</para>
<indexterm zone="freetype2-pass1 freetype-config-pass1">

8
shareddeps/dps/basicx/other/freetype2-pass2.xml
View File

@ -95,9 +95,9 @@
<para>
<option>--without-harfbuzz</option>: If
<application>harfbuzz</application> is installed prior to
<application>freetype</application> without
<application>freetype</application> support, use this switch to avoid a
harfbuzz is installed prior to
freetype without
freetype support, use this switch to avoid a
build failure.
</para>
@ -145,7 +145,7 @@
<term><command>freetype-config</command></term>
<listitem>
<para>
is used to get <application>FreeType</application> compilation
is used to get FreeType compilation
and linking information
</para>
<indexterm zone="freetype2-pass2 freetype-config-pass2">

10
shareddeps/dps/basicx/other/gnutls.xml
View File

@ -21,9 +21,9 @@
<title>Introduction to GnuTLS</title>
<para>
The <application>GnuTLS</application> package contains libraries and
The GnuTLS package contains libraries and
userspace tools which provide a secure layer over a reliable transport
layer. Currently the <application>GnuTLS</application> library implements
layer. Currently the GnuTLS library implements
the proposed standards by the IETF's TLS working group. Quoting from the
<ulink url="https://datatracker.ietf.org/doc/rfc8446/">
TLS 1.3 protocol specification
@ -39,7 +39,7 @@
</para>
<para>
<application>GnuTLS</application> provides support for TLS 1.3, TLS 1.2,
GnuTLS provides support for TLS 1.3, TLS 1.2,
TLS 1.1, TLS 1.0, and (optionally) SSL 3.0 protocols. It also supports
TLS extensions, including server name and max record size. Additionally,
the library supports authentication using the SRP protocol, X.509
@ -95,7 +95,7 @@
<!-- Note that if you do not install <xref linkend="libtasn1"/>, an older
3.8.0 includes minitasn1 4.19 which is currnet at the moment. ken -->
Note that if you do not install <xref linkend="libtasn1"/>, a
version shipped in the <application>GnuTLS</application> tarball will be
version shipped in the GnuTLS tarball will be
used instead.
</para></note>
@ -105,7 +105,7 @@
<title>Installation of GnuTLS</title>
<para>
Install <application>GnuTLS</application> by running the
Install GnuTLS by running the
following commands:
</para>

14
shareddeps/dps/basicx/other/harfbuzz.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to HarfBuzz</title>
<para>
The <application>HarfBuzz</application> package contains an OpenType text
The HarfBuzz package contains an OpenType text
shaping engine.
</para>
@ -58,7 +58,7 @@
<title>Installation of HarfBuzz</title>
<para>
Install <application>HarfBuzz</application> by running the following
Install HarfBuzz by running the following
commands:
</para>
@ -89,7 +89,7 @@ ninja</userinput></screen>
<title>lib32 Installation of HarfBuzz</title>
<para>
Install lib32-<application>HarfBuzz</application> by running the following
Install lib32-HarfBuzz by running the following
commands:
</para>
@ -125,14 +125,14 @@ ldconfig</userinput></screen>
<para>
<parameter>-D cairo=disabled</parameter>: This switch forces this package
to not link against <application>Cairo</application> for the lib32 build
as it will mistakenly believe that lib32-<application>Cairo</application>
to not link against Cairo for the lib32 build
as it will mistakenly believe that lib32-Cairo
is installed if the 64-bit version is installed.
</para>
<para>
<parameter>-D graphite2=disabled</parameter>: This switch disables
<application>Graphite2</application> support, which isn't in GLFS.
Graphite2 support, which isn't in GLFS.
</para>
<para>
@ -143,7 +143,7 @@ ldconfig</userinput></screen>
<!--
<para>
<parameter>-Dbenchmark=disabled</parameter>: This switch disables
downloading and building the <application>google-benchmark</application>
downloading and building the google-benchmark
subproject, which requires <xref linkend="git"/>, and is of no
use for non developers.
</para>

18
shareddeps/dps/basicx/other/libpng.xml
View File

@ -24,7 +24,7 @@
<title>Introduction to libpng</title>
<para>
The <application>libpng</application> package contains libraries used
The libpng package contains libraries used
by other programs for reading and writing PNG files. The PNG format
was designed as a replacement for GIF and, to a lesser extent, TIFF,
with many improvements and extensions and lack of patent problems.
@ -48,11 +48,11 @@
<listitem>
<para>
Recommended patch to include animated png functionality in
<application>libpng</application> (required to use the system
<application>libpng</application> in
<application>Firefox</application>,
<application>Seamonkey</application>, and
<application>Thunderbird</application>): <ulink url="&apng-patch;"/>
libpng (required to use the system
libpng in
Firefox,
Seamonkey, and
Thunderbird): <ulink url="&apng-patch;"/>
</para>
</listitem>
</itemizedlist>
@ -69,7 +69,7 @@
<screen><userinput>gzip -cd ../libpng-&apng-version;-apng.patch.gz | patch -p1</userinput></screen>
<para>
Install <application>libpng</application> by running the following
Install libpng by running the following
commands:
</para>
@ -94,7 +94,7 @@ cp -v README libpng-manual.txt /usr/share/doc/libpng-&libpng-version;</userinput
<title>lib32 Installation of libpng</title>
<para>
Install lib32-<application>libpng</application> by running the following
Install lib32-libpng by running the following
commands:
</para>
@ -187,7 +187,7 @@ ldconfig</userinput></screen>
<para>
is a shell script that provides configuration information
for applications wanting to use
<application>libpng</application>
libpng
</para>
<indexterm zone="libpng libpng-config">
<primary sortas="b-libpng-config">libpng-config</primary>

6
shareddeps/dps/basicx/other/libunwind.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to libunwind</title>
<para>
The <application>libunwind</application> package contains a portable and
The libunwind package contains a portable and
efficient C programming interface (API) to determine the call-chain of a
program. The API additionally provides the means to manipulate the
preserved (callee-saved) state of each call-frame and to resume execution
@ -64,7 +64,7 @@
<screen><userinput>patch -Np1 -i ../libunwind-&libunwind-version;-fix_malloc.patch</userinput></screen>
<para>
Install <application>libunwind</application> by running the following
Install libunwind by running the following
commands:
</para>
@ -89,7 +89,7 @@ make</userinput></screen>
<title>lib32 Installation of libunwind</title>
<para>
Install lib32-<application>libunwind</application> by running the following
Install lib32-libunwind by running the following
commands:
</para>

4
shareddeps/dps/basicx/other/nettle.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Nettle</title>
<para>
The <application>Nettle</application> package contains a low-level
The Nettle package contains a low-level
cryptographic library that is designed to fit easily in many contexts.
</para>
@ -44,7 +44,7 @@
<title>Installation of Nettle</title>
<para>
Install <application>Nettle</application> by running the following
Install Nettle by running the following
commands:
</para>

4
shareddeps/dps/basicx/other/pixman.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Pixman</title>
<para>
The <application>Pixman</application> package contains a library that
The Pixman package contains a library that
provides low-level pixel manipulation features such as image
compositing and trapezoid rasterization.
</para>
@ -45,7 +45,7 @@
<title>Installation of Pixman</title>
<para>
Install <application>Pixman</application> by running the following
Install Pixman by running the following
commands:
</para>

4
shareddeps/dps/basicx/other/which.xml
View File

@ -35,7 +35,7 @@
<para>
The first option is to install the actual GNU
<application>which</application> package.
which package.
</para>
<itemizedlist spacing="compact">
@ -57,7 +57,7 @@
<title>Installation of Which</title>
<para>
Install <application>which</application> by running the following
Install which by running the following
commands:
</para>

26
shareddeps/dps/basicx/x/basic-xorg-7.xml
View File

@ -17,8 +17,8 @@
<para>
<application>Xorg</application> is a freely redistributable,
open-source implementation of the <application>X</application> Window
Xorg is a freely redistributable,
open-source implementation of the X Window
System. This system provides a client/server interface between display
hardware (the mouse, keyboard, and video displays) and the desktop
environment, while also providing both the windowing infrastructure and a
@ -28,15 +28,15 @@
<para>
This section however doesn't install <xref linkend="xorg-server"/>, but
instead installs basic software that a lot of other software depend on,
including the <application>Xorg</application> server, compositors, window
including the Xorg server, compositors, window
managers or desktop environments, and <xref linkend="xwayland"/>.
</para>
<note><para>
<application>Xwayland</application> is a necessary part of Wayland if you
want to use <application>Xorg</application>-only software like <xref
Xwayland is a necessary part of Wayland if you
want to use Xorg-only software like <xref
linkend="steam"/>. <xref linkend="wine"/> has an experimental
<application>Wayland</application> mode but it is still a good idea to
Wayland mode but it is still a good idea to
install <xref linkend="xwayland"/> for now.
</para></note>
@ -50,7 +50,7 @@
packages that need to be fetched from the download location. To assist
with such a large task, installing <xref linkend="wget"/> is strongly
recommended for downloading the needed files. A complete
<application>wget</application> file list is provided for each page
wget file list is provided for each page
that includes multiple packages.
</para>
@ -74,12 +74,12 @@
work well with each other. Further, the wget file lists contain comments
for specific packages that are deprecated or are not recommended to
install. Newer packages are likely intended for the
next release of <application>Xorg</application> and have already proved
next release of Xorg and have already proved
to be incompatible with current versions of software installed in GLFS.
The installed size of <application>Xorg</application> can be reduced
The installed size of Xorg can be reduced
considerably by installing only the packages that you will need and use,
however, the GLFS book cannot account for all dependencies and build
options for the individual <application>Xorg</application> packages.
options for the individual Xorg packages.
The instructions assume that all packages have been built.
</para>
</note>
@ -97,7 +97,7 @@
package needs to get installed. The last accommodation is allow you
to build and install each package as the <systemitem class="username">root
</systemitem> user. This is not recommended but is an option if you
don't want to install <application>sudo</application> and don't want
don't want to install sudo and don't want
to type a password again and again.
</para>
@ -149,9 +149,9 @@ EOF
chmod 644 /etc/profile.d/xorg.sh</userinput></screen>
<para>
If you've installed <application>sudo</application>, ensure that
If you've installed sudo, ensure that
<envar>XORG_CONFIG</envar> is available
in the <application>sudo</application> environment. As the
in the sudo environment. As the
<systemitem class="username">root</systemitem> user, run the following
command:
</para>

6
shareddeps/dps/basicx/x/libXau.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to libXau</title>
<para>
The <application>libXau</application> package contains a library
The libXau package contains a library
implementing the X11 Authorization Protocol. This is useful for
restricting client access to the display.
</para>
@ -53,7 +53,7 @@
<title>Installation of libXau</title>
<para>
Install <application>libXau</application> by running the following
Install libXau by running the following
commands:
</para>
@ -76,7 +76,7 @@ make</userinput></screen>
<title>lib32 Installation of libXau</title>
<para>
Install lib32-<application>libXau</application> by running the following
Install lib32-libXau by running the following
commands:
</para>

6
shareddeps/dps/basicx/x/libXdmcp.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to libXdmcp</title>
<para>
The <application>libXdmcp</application> package contains a library
The libXdmcp package contains a library
implementing the X Display Manager Control Protocol. This is useful for
allowing clients to interact with the X Display Manager.
</para>
@ -53,7 +53,7 @@
<title>Installation of libXdmcp</title>
<para>
Install <application>libXdmcp</application> by running the following
Install libXdmcp by running the following
commands:
</para>
@ -76,7 +76,7 @@ make</userinput></screen>
<title>lib32 Installation of libXdmcp</title>
<para>
Install lib32-<application>libXdmcp</application> by running the following
Install lib32-libXdmcp by running the following
commands:
</para>

6
shareddeps/dps/basicx/x/libxcb.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to libxcb</title>
<para>
The <application>libxcb</application> package provides an interface to
The libxcb package provides an interface to
the X Window System protocol, which replaces the current Xlib interface.
Xlib can also use XCB as a transport layer, allowing software to make
requests and receive responses with both.
@ -56,7 +56,7 @@
<title>Installation of libxcb</title>
<para>
Install <application>libxcb</application> by running the following
Install libxcb by running the following
commands:
</para>
@ -90,7 +90,7 @@ make</userinput></screen>
<title>lib32 Installation of libxcb</title>
<para>
Install lib32-<application>libxcb</application> by running the following
Install lib32-libxcb by running the following
commands:
</para>

6
shareddeps/dps/basicx/x/libxcvt.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to libxcvt</title>
<para>
<application>libxcvt</application> is a library providing a standalone
libxcvt is a library providing a standalone
version of the X server implementation of the VESA CVT standard timing
modelines generator. It is meant to be a direct replacement to the
version formerly provided by the Xorg server.
@ -54,7 +54,7 @@
<title>Installation of libxcvt</title>
<para>
Install <application>libxcvt</application> by running the following
Install libxcvt by running the following
commands:
</para>
@ -80,7 +80,7 @@ ninja</userinput></screen>
<title>lib32 Installation of libxcvt</title>
<para>
Install lib32-<application>libxcvt</application> by running the following
Install lib32-libxcvt by running the following
commands:
</para>

8
shareddeps/dps/basicx/x/util-macros.xml
View File

@ -22,9 +22,9 @@
<title>Introduction to util-macros</title>
<para>
The <application>util-macros</application> package contains the
<application>m4</application> macros used by all of the
<application>Xorg</application> packages.
The util-macros package contains the
m4 macros used by all of the
Xorg packages.
</para>
<itemizedlist spacing="compact">
@ -55,7 +55,7 @@
<title>Installation of util-macros</title>
<para>
Install <application>util-macros</application> by running the following
Install util-macros by running the following
commands:
</para>

14
shareddeps/dps/basicx/x/x7lib.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Xorg Libraries</title>
<para>
The <application>Xorg</application> libraries provide library
The Xorg libraries provide library
routines that are used within all X Window applications.
</para>
@ -106,7 +106,7 @@ libXpresent-&libXpresent-version;.tar.xz</literal>
EOF</userinput></screen>
<para>
<application>libFS</application> is commented out and will not be built
libFS is commented out and will not be built
unless you go out of your way to uncomment it. It is not needed for any
packages in the LFS books and only necessary for some Xorg apps.
</para>
@ -141,10 +141,10 @@ grep -v '^#' ../lib-&xorg-version;-list | wget -i- -c \
<screen><userinput>grep -A9 summary *make_check.log</userinput></screen>
<para>
GLFS developers have confirmed that <application>libX11</application>,
<application>libXt</application>, <application>libXmu</application>,
<application>libXpm</application>, and
<application>libxshmfence</application> are distributed with working test
GLFS developers have confirmed that libX11,
libXt, libXmu,
libXpm, and
libxshmfence are distributed with working test
suites.
</para>
@ -296,7 +296,7 @@ done</userinput></screen>
<para>
<parameter>--disable-open-zfile</parameter>: Allow
<application>libXpm</application> to build without the
libXpm to build without the
optional <command>compress</command> command present.
</para>

6
shareddeps/dps/basicx/x/xcb-proto.xml
View File

@ -22,8 +22,8 @@
<title>Introduction to xcb-proto</title>
<para>
The <application>xcb-proto</application> package provides the
XML-XCB protocol descriptions that <application>libxcb</application>
The xcb-proto package provides the
XML-XCB protocol descriptions that libxcb
uses to generate the majority of its code and API.
</para>
@ -59,7 +59,7 @@
<title>Installation of xcb-proto</title>
<para>
Install <application>xcb-proto</application> by running the following
Install xcb-proto by running the following
commands:
</para>

4
shareddeps/dps/basicx/x/xorgproto.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to xorgproto</title>
<para>
The <application>xorgproto</application> package provides the
The xorgproto package provides the
header files required to build the X Window system, and to allow other
applications to build against the installed X Window system.
</para>
@ -53,7 +53,7 @@
<title>Installation of xorgproto</title>
<para>
Install <application>xorgproto</application> by running the
Install xorgproto by running the
following commands:
</para>

4
shareddeps/dps/wl/wayland-protocols.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Wayland-Protocols</title>
<para>
The <application>Wayland-Protocols</application> package contains
The Wayland-Protocols package contains
additional Wayland protocols that add functionality outside of
protocols already in the Wayland core.
</para>
@ -52,7 +52,7 @@
<title>Installation of Wayland-Protocols</title>
<para>
Install <application>Wayland-Protocols</application> by running the following
Install Wayland-Protocols by running the following
commands:
</para>

14
shareddeps/dps/wl/wayland.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Wayland</title>
<para>
<application>Wayland</application> is a project to define a protocol
Wayland is a project to define a protocol
for a compositor to talk to its clients as well as a library
implementation of the protocol.
</para>
@ -52,7 +52,7 @@
<title>Installation of Wayland</title>
<para>
Install <application>Wayland</application> by running the following
Install Wayland by running the following
commands:
</para>
@ -87,7 +87,7 @@ ninja</userinput></screen>
<title>lib32 Installation of Wayland</title>
<para>
Install lib32-<application>Wayland</application> by running the following
Install lib32-Wayland by running the following
commands:
</para>
@ -180,7 +180,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libwayland-client</filename></term>
<listitem>
<para>
contains API functions for writing <application>Wayland</application>
contains API functions for writing Wayland
applications
</para>
<indexterm zone="wayland libwayland-client">
@ -193,7 +193,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libwayland-cursor</filename></term>
<listitem>
<para>
contains API functions for managing cursors in <application>Wayland</application>
contains API functions for managing cursors in Wayland
applications
</para>
<indexterm zone="wayland libwayland-cursor">
@ -207,7 +207,7 @@ ldconfig</userinput></screen>
<listitem>
<para>
contains API functions for handling OpenGL calls in
<application>Wayland</application> applications
Wayland applications
</para>
<indexterm zone="wayland libwayland-egl">
<primary sortas="c-libwayland-egl">libwayland-egl</primary>
@ -219,7 +219,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libwayland-server</filename></term>
<listitem>
<para>
contains API functions for writing <application>Wayland</application>
contains API functions for writing Wayland
compositors
</para>
<indexterm zone="wayland libwayland-server">

4
shareddeps/dps/x/libepoxy.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to libepoxy</title>
<para>
<application>libepoxy</application> is a library for handling OpenGL
libepoxy is a library for handling OpenGL
function pointer management.
</para>
@ -51,7 +51,7 @@
<title>Installation of libepoxy</title>
<para>
Install <application>libepoxy</application> by running the following
Install libepoxy by running the following
commands:
</para>

6
shareddeps/dps/x/libevdev.xml
View File

@ -25,7 +25,7 @@
<title>Introduction to libevdev</title>
<para>
The <application>libevdev</application> package contains common
The libevdev package contains common
functions for Xorg input drivers.
</para>
@ -64,7 +64,7 @@
<title>Installation of libevdev</title>
<para>
Install <application>libevdev</application> by running the following
Install libevdev by running the following
commands:
</para>
@ -106,7 +106,7 @@ ninja</userinput></screen>
<para>
<parameter>-D tests=disabled</parameter>: This switch disables building
tests as they depend on <application>Check</application>.
tests as they depend on Check.
</para>
</sect3>

6
shareddeps/dps/x/libinput.xml
View File

@ -27,7 +27,7 @@
<title>Introduction to Libinput</title>
<para>
<application>libinput</application> is a library that handles
libinput is a library that handles
input devices for display servers and other applications that
need to directly deal with input devices.
</para>
@ -59,7 +59,7 @@
<title>Installation of Libinput</title>
<para>
Install <application>libinput</application> by running the following
Install libinput by running the following
commands:
</para>
@ -153,7 +153,7 @@ cp -rv Documentation/* /usr/share/doc/libinput-&libinput-version;/html</userinpu
<listitem>
<para>
is a set of tools to interface with the
<application>libinput</application> library
libinput library
</para>
<indexterm zone="libinput libinput-prog">
<primary sortas="b-libinput-prog">libinput</primary>

4
shareddeps/dps/x/mtdev.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to mtdev</title>
<para>
The <application>mtdev</application> package contains Multitouch
The mtdev package contains Multitouch
Protocol Translation Library which is used to transform all
variants of kernel MT (Multitouch) events to the slotted type B
protocol.
@ -46,7 +46,7 @@
<title>Installation of mtdev</title>
<para>
Install <application>mtdev</application> by running the following
Install mtdev by running the following
commands:
</para>

8
shareddeps/dps/x/x7app.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Xorg Applications</title>
<para>
The <application>Xorg</application> applications provide the
The Xorg applications provide the
expected applications available in previous X Window implementations.
</para>
@ -143,7 +143,7 @@ done</userinput></screen>
<para>
Remove an undocumented script which is reported to be broken
(<command>xkeystone</command> provided by the
<application>xrandr</application> package):
xrandr package):
</para>
<screen><userinput>as_root rm -f /usr/bin/xkeystone</userinput></screen>
@ -155,9 +155,9 @@ done</userinput></screen>
<para>
<command>sed -e 's/\$(CPP) \$(DEFS)/$(CPP) -P $(DEFS)/' -i
man/Makefile.in</command>: with <application>gcc-5</application> the
man/Makefile.in</command>: with gcc-5 the
behavior of <command>cpp</command> was changed to emit line numbers.
That results in unterminated <application>sed</application> commands in
That results in unterminated sed commands in
<filename>filenames.sed</filename>. Adding <literal>-P</literal> restores
the old behavior.
</para>

4
shareddeps/dps/x/x7driver-evdev.xml
View File

@ -25,7 +25,7 @@
<title>Introduction to Xorg Evdev Driver</title>
<para>
The <application>Xorg Evdev Driver</application> package contains a Generic
The Xorg Evdev Driver package contains a Generic
Linux input driver for the Xorg X server. It handles keyboard, mouse, touchpads
and wacom devices, though for touchpad and wacom advanced handling,
additional drivers are required.
@ -84,7 +84,7 @@
<title>Installation of Xorg Evdev Driver</title>
<para>
Install <application>Xorg Evdev Driver</application> by running the following
Install Xorg Evdev Driver by running the following
commands:
</para>

4
shareddeps/dps/x/x7driver-libinput.xml
View File

@ -25,7 +25,7 @@
<title>Introduction to Xorg Libinput Driver</title>
<para>
The <application>X.Org Libinput Driver</application> is a thin wrapper
The X.Org Libinput Driver is a thin wrapper
around libinput and allows for libinput to be used for input devices in
X. This driver can be used as drop-in replacement for evdev and
synaptics.
@ -58,7 +58,7 @@
<title>Installation of Xorg Libinput Driver</title>
<para>
Install <application>Xorg Libinput Driver</application> by running the following
Install Xorg Libinput Driver by running the following
commands:
</para>

4
shareddeps/dps/x/x7driver-synaptics.xml
View File

@ -25,7 +25,7 @@
<title>Introduction to Xorg Synaptics Driver</title>
<para>
The <application>Xorg Synaptics Driver</application> package contains
The Xorg Synaptics Driver package contains
the X.Org Input Driver, support programs and SDK for Synaptics
touchpads. Even though the evdev driver can handle touchpads very well,
this driver is required if you want to use advanced features like multi
@ -60,7 +60,7 @@
<title>Installation of Xorg Synaptics Driver</title>
<para>
Install <application>Xorg Synaptics Driver</application> by running the following
Install Xorg Synaptics Driver by running the following
commands:
</para>

6
shareddeps/dps/x/x7driver-wacom.xml
View File

@ -25,10 +25,10 @@
<title>Introduction to Xorg Wacom Driver</title>
<para>
The <application>Xorg Wacom Driver</application> package contains the
The Xorg Wacom Driver package contains the
X.Org X11 driver and SDK for Wacom and Wacom-like tablets. It is not
required to use a Wacom tablet, the
<application>xf86-input-evdev</application> driver can handle these
xf86-input-evdev driver can handle these
devices without problems.
</para>
@ -76,7 +76,7 @@
<title>Installation of Xorg Wacom Driver</title>
<para>
Install <application>Xorg Wacom Driver</application> by running the following
Install Xorg Wacom Driver by running the following
commands:
</para>

2
shareddeps/dps/x/x7driver.xml
View File

@ -19,7 +19,7 @@
<title>Introduction to Xorg Input Drivers</title>
<para>
The <application>Xorg Input Drivers</application> page contains the
The Xorg Input Drivers page contains the
instructions for building Xorg input drivers that are necessary in
order for Xorg Server to respond user inputs.
</para>

4
shareddeps/dps/x/x7font.xml
View File

@ -21,8 +21,8 @@
<title>Introduction to Xorg Fonts</title>
<para>
The <application>Xorg</application> font packages provide some scalable
fonts and supporting packages for <application>Xorg</application>
The Xorg font packages provide some scalable
fonts and supporting packages for Xorg
applications. Many people will want to install other TTF or OTF fonts in
addition to, or instead of, these. Some are listed at <ulink
url="&blfs-svn;/x/TTF-and-OTF-fonts.html">TTF-and-OTF-fonts</ulink>.

4
shareddeps/dps/x/xbitmaps.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to xbitmaps</title>
<para>
The <application>xbitmaps</application> package contains bitmap
The xbitmaps package contains bitmap
images used by multiple applications built in Xorg chapter.
</para>
@ -51,7 +51,7 @@
<title>Installation of xbitmaps</title>
<para>
Install <application>xbitmaps</application> by running the
Install xbitmaps by running the
following commands:
</para>

2
shareddeps/dps/x/xcb-utils.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to XCB Utils</title>
<para>
The <application>XCB</application> collection of utilities provide
The XCB collection of utilities provide
useful libraries for developers to use for X window manager and Wayland
compositor development. The installed packages below should be good
enough for most packages.

4
shareddeps/dps/x/xcursor-themes.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to xcursor-themes</title>
<para>
The <application>xcursor-themes</application> package contains the
The xcursor-themes package contains the
redglass and whiteglass animated cursor themes.
</para>
@ -51,7 +51,7 @@
<title>Installation of xcursor-themes</title>
<para>
Install <application>xcursor-themes</application> by running the
Install xcursor-themes by running the
following commands:
</para>

4
shareddeps/dps/x/xinit.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to xinit</title>
<para>
The <application>xinit</application> package contains a usable script
The xinit package contains a usable script
to start the xserver.
</para>
@ -51,7 +51,7 @@
<title>Installation of xinit</title>
<para>
Install <application>xinit</application> by running the
Install xinit by running the
following commands:
</para>

4
shareddeps/dps/x/xkeyboard-config.xml
View File

@ -22,7 +22,7 @@
<title>Introduction to XKeyboard-Config</title>
<para>
The <application>XKeyboard-Config</application> package contains
The XKeyboard-Config package contains
the keyboard configuration database for the X Window System.
</para>
@ -52,7 +52,7 @@
<title>Installation of XKeyboard-Config</title>
<para>
Install <application>XKeyboard-Config</application> by running the
Install XKeyboard-Config by running the
following commands:
</para>

20
shareddeps/dps/x/xorg-config.xml
View File

@ -65,19 +65,19 @@
</warning>
<para>
To test the <application>Xorg</application> installation, issue
To test the Xorg installation, issue
<command>startx</command>. This command brings up a rudimentary window
manager called <emphasis>twm</emphasis> with three xterm windows and one
xclock window. The xterm window in the upper left is a login terminal and
running <emphasis>exit</emphasis> from this terminal will exit the
<application>X Window</application> session. The third xterm window may
X Window session. The third xterm window may
be obscured on your system by the other two xterms.
</para>
<note>
<para>
When testing <application>Xorg</application> with the
<application>twm</application> window manager, there will be several
When testing Xorg with the
twm window manager, there will be several
warnings in the Xorg log file, <!--<filename revision="sysv">
/var/log/Xorg.0.log</filename><filename revision="systemd">-->
$HOME/.local/share/xorg/Xorg.0.log<!--</filename>-->, about missing font
@ -99,7 +99,7 @@
<para>
Generally, there is no specific configuration required for
<application>Xorg</application>, but customization is possible. For
Xorg, but customization is possible. For
details, see <xref linkend='xconfig'/> below.
</para>
@ -113,8 +113,8 @@
<para>
DRI is a framework for allowing software to access graphics hardware in
a safe and efficient manner. It is installed in
<application>X</application> by default (using
<application>Mesa</application>) if you have a supported video card.
X by default (using
Mesa) if you have a supported video card.
</para>
<para>
@ -294,12 +294,12 @@ usermod -a -G video &lt;user running xorg&gt;</userinput></screen>
<para>
In order to use PRIME for GPU switching, make sure that you are using
Linux Kernel 3.4 or later (recommended). You will need latest DRI and
DDX drivers for your hardware and <application>Xorg Server</application>
DDX drivers for your hardware and Xorg Server
1.13 or later.
</para>
<para>
<application>Xorg Server</application> should load both GPU drivers
Xorg Server should load both GPU drivers
automatically. You can check that by running:
</para>
@ -327,7 +327,7 @@ Provider 1: id: 0x56 cap: 0xf, Source Output, Sink Output, Source Offload, Sink
<note>
<para>
With the <application>Xorg</application> modesetting driver,
With the Xorg modesetting driver,
which is DRI3 capable, the above command is no longer
necessary. It does no harm however.
</para>

2
shareddeps/dps/x/xorg-server.xml
View File

@ -25,7 +25,7 @@
<title>Introduction to Xorg Server</title>
<para>
The <application>Xorg</application> Server is the core
The Xorg Server is the core
of the X Window system.
</para>

4
shareddeps/dps/x/xwayland.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Xwayland</title>
<para>
The <application>Xwayland</application> package is an Xorg server
The Xwayland package is an Xorg server
running on top of the wayland server. It has been separated from the
main Xorg server package. It allows running X clients inside a
wayland session.
@ -66,7 +66,7 @@
<title>Installation of Xwayland</title>
<para>
Install <application>xwayland</application> by running the following
Install xwayland by running the following
commands:
</para>

34
shareddeps/drivers/aboutgl.xml
View File

@ -24,14 +24,14 @@
</para>
<para>
So, <application>Mesa</application> came in and implemented drivers and
So, Mesa came in and implemented drivers and
functions for OpenGL. They also implement GLX and EGL which provide
interfaces to window systems like <application>Xorg</application>.
interfaces to window systems like Xorg.
However, their method doesn't dispatch the calls in a vendor-neutral way.
For the most part, this approach is fine and doesn't lead to any issues.
<application>NVIDIA</application> has decided that this was a bad enough
NVIDIA has decided that this was a bad enough
approach to warrant making another implementation of OpenGL called
<application>libglvnd</application>. It only provides the implementations
libglvnd. It only provides the implementations
for OpenGL, OpenGL ES, GLX, and EGL. This had led to legacy OpenGL vs new
OpenGL on Linux.
</para>
@ -50,7 +50,7 @@
<para>
This is only a problem for binary only packages and some
<application>CMake</application> build systems. For this book and in
CMake build systems. For this book and in
BLFS, you shouldn't run into any of those issues unless you wish to use
<xref linkend="nvidia"/>, which specifically requires <xref
linkend="libglvnd"/>. SLFS aims to work around issues that arise from
@ -62,7 +62,7 @@
url="https://www.shipofharkinian.com/">Ship of Harkinian</ulink>, a PC
port of the Nintendo 64 game, Legend of Zelda: Ocarina of Time, links
against new OpenGL and will be broken with only
<application>Mesa</application> installed; furthermore, trying to get
Mesa installed; furthermore, trying to get
around the issue by building from source also leads to many issues.
However, the binary of the PC port made from statically recompiling the
Nintendo 64 game, Legend of Zelda: Majora's Mask, called <ulink
@ -75,11 +75,11 @@
If you only want legacy OpenGL, you can just install <xref
linkend="mesa"/>. If you want new OpenGL, support for some binary-only
packages, <xref linkend="nvidia"/>, and get past some
<application>CMake</application> build systems, install <xref
CMake build systems, install <xref
linkend="libglvnd"/>. If you want a driver from <xref
linkend="mesa"/>, you can build that after
<application>libglvnd</application>. <application>Mesa</application> will
auto-detect <application>libglvnd</application> and will skip building
libglvnd. Mesa will
auto-detect libglvnd and will skip building
its OpenGL implementations.
</para>
@ -113,11 +113,11 @@
<para>
GLES, specifically v2 and v3, are used sometimes, but mostly in one
area. Such an area is in <application>Wayland</application>
area. Such an area is in Wayland
compositors and compositor libraries, such as
<application>Hyprland</application>, <application>Mutter</application>,
<application>Wayfire</application>, and
<application>Wlroots</application>. While compositors can utilize
Hyprland, Mutter,
Wayfire, and
Wlroots. While compositors can utilize
Vulkan, most compositors require GLES rendering and don't offer a Vulkan
solution, or any other rendering API solution. GLESv1 on the otherhand
is an outdated specification of the GLES API that has been phased out
@ -131,12 +131,12 @@
<title>History of Wayland and GLES</title>
<para>
When the <application>Wayland</application> set of protocols were made, a
When the Wayland set of protocols were made, a
reference implementation had to be made for it to show what was possible,
and how to create a compositor for the new protocol. The result was
<application>Weston</application>. For its rendering API, it used, and
Weston. For its rendering API, it used, and
uses, GLES and EGL. This was done so that the dependency on the
libraries from the <application>X</application> Window System wasn't
libraries from the X Window System wasn't
needed, that a Wayland-only setup was possible. A small benefit of using
GLES was that it could run on embedded systems like Raspberry Pis.
</para>
@ -168,7 +168,7 @@
</para>
<para>
On the otherhand, if you are using the <application>X</application>
On the otherhand, if you are using the X
Window System, GLES will almost never be used and that support for the
API can be disabled without much worry. However, you kill off the
ability to use Wayland compositors that require GLES rendering if you

2
shareddeps/drivers/amdgpu-pro.xml
View File

@ -27,7 +27,7 @@
</para></important>
<para>
The <application>AMDGPU PRO</application> proprietary driver contains
The AMDGPU PRO proprietary driver contains
userland drivers and libraries, providing hardware acceleration encoding,
EGL, OpenGL, GLES, and Vulkan support <emphasis>FOR</emphasis> AMDGPU
cards. If you do not have an AMDGPU card, you can skip this page.

6
shareddeps/drivers/cbindgen.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Cbindgen</title>
<para>
<application>Cbindgen</application> can be used to generate C bindings for
Cbindgen can be used to generate C bindings for
Rust code.
</para>
@ -52,7 +52,7 @@
<sect2 role="installation">
<title>Installation of cbindgen</title>
<para>
Install <application>cbindgen</application> by running the following
Install cbindgen by running the following
commands:
</para>
@ -102,7 +102,7 @@
<term><command>cbindgen</command></term>
<listitem>
<para>
generates C bindings for <application>Rust</application> code
generates C bindings for Rust code
</para>
<indexterm zone="cbindgen cbindgen-prog">
<primary sortas="b-cbindgen">cbindgen</primary>

16
shareddeps/drivers/cython.xml
View File

@ -21,8 +21,8 @@
<title>Introduction to Cython</title>
<para>
The <application>Cython</application> package provides a compiler for
writing C extensions for the <application>Python</application> language.
The Cython package provides a compiler for
writing C extensions for the Python language.
</para>
&long-build-time;
@ -91,7 +91,7 @@
<term><command>cydbg</command></term>
<listitem>
<para>
is the <application>Cython</application> debugger
is the Cython debugger
</para>
<indexterm zone="cython cydbg">
<primary sortas="b-cydbg">cydbg</primary>
@ -103,8 +103,8 @@
<term><command>cython</command></term>
<listitem>
<para>
is a compiler for code written in the <application>Cython
</application> language. It outputs a C/C++ program which can be
is a compiler for code written in the Cython
language. It outputs a C/C++ program which can be
compiled with a C/C++ compiler
</para>
<indexterm zone="cython cython-bin">
@ -117,9 +117,9 @@
<term><command>cythonize</command></term>
<listitem>
<para>
is a compiler for code written in the <application>Cython
</application> language. It outputs an extension module which is
directly importable from <application>Python</application>
is a compiler for code written in the Cython
language. It outputs an extension module which is
directly importable from Python
</para>
<indexterm zone="cython cythonize">
<primary sortas="b-cythonize">cythonize</primary>

18
shareddeps/drivers/gbm.xml
View File

@ -21,21 +21,21 @@
<title>Introduction to GBM</title>
<para>
The <application>GBM</application>
The GBM
<footnote><para>
Graphics Buffer Manager.
</para></footnote>
library provides API functions for graphical rendering and is supplied by
<application>Mesa</application>. Most drivers on Linux distributions come
from <application>Mesa</application>, so <application>GBM</application>
Mesa. Most drivers on Linux distributions come
from Mesa, so GBM
will get installed along those drivers. On the other hand, <xref
linkend="nvidia"/> does not need the full <application>Mesa</application>
stack, but it still needs the <application>GBM</application> library. As
linkend="nvidia"/> does not need the full Mesa
stack, but it still needs the GBM library. As
such, you can install just what you need. You will not need to install
the full <xref linkend="mesa"/> stack if you want to install <xref
linkend="nvidia"/>, but you can if you so choose. It can be a good idea
to do so as to have a fallback (Zink Gallium3D + Nouveau Vulkan). If you
are not installing <application>NVIDIA</application>, skip to <xref
are not installing NVIDIA, skip to <xref
linkend="llvm"/> and keep going till you reach <xref
linkend="mesa"/> to get a complete installation of drivers and other
libraries.
@ -43,7 +43,7 @@
<note>
<para>
<application>Mesa</application> is updated relatively often. You may
Mesa is updated relatively often. You may
want to use the latest available &mesa-major-minor;.x mesa version.
</para>
</note>
@ -84,7 +84,7 @@
<title>Installation of GBM</title>
<para>
Install the <application>GBM</application> by running the following
Install the GBM by running the following
commands:
</para>
@ -122,7 +122,7 @@ fi</userinput></screen>
<title>lib32 Installation of GBM</title>
<para>
Install lib32-<application>GBM</application> by running the following
Install lib32-GBM by running the following
commands:
</para>

4
shareddeps/drivers/hwdata.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to hwdata</title>
<para>
The <application>hwdata</application> package contains
The hwdata package contains
current PCI and vendor id data.
</para>
@ -44,7 +44,7 @@
<title>Installation of hwdata</title>
<para>
Install <application>hwdata</application> by
Install hwdata by
running the following commands:
</para>

4
shareddeps/drivers/libclc.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to libclc</title>
<para>
The <application>libclc</application> package contains library requirements
The libclc package contains library requirements
of the OpenCL C programming language (provides header files but no
libraries itself).
</para>
@ -53,7 +53,7 @@
<title>Installation of libclc</title>
<para>
Install <application>libclc</application> by running the following
Install libclc by running the following
commands:
</para>

8
shareddeps/drivers/libdrm.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Libdrm</title>
<para>
<application>Libdrm</application> provides a userspace library for
Libdrm provides a userspace library for
accessing the direct rendering manager (DRM) on operating systems that
support the ioctl interface. Libdrm is a low-level library, typically used
by graphics drivers such as the Mesa DRI drivers, the X drivers, libva and
@ -68,7 +68,7 @@
-->
<para>
Install <application>libdrm</application> by running the following
Install libdrm by running the following
commands:
</para>
@ -96,7 +96,7 @@ ninja</userinput></screen>
<title>lib32 Installation of Libdrm</title>
<para>
Install lib32-<application>libdrm</application> by running the following
Install lib32-libdrm by running the following
commands:
</para>
@ -138,7 +138,7 @@ ldconfig</userinput></screen>
<para>
<parameter>-D udev=true</parameter>: This parameter enables support for using
<application>Udev</application> instead of <command>mknod</command>.
Udev instead of <command>mknod</command>.
</para>
<para>

18
shareddeps/drivers/libglvnd.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to libglvnd</title>
<para>
The <application>libglvnd</application> package provides OpenGL
The libglvnd package provides OpenGL
implementations that dispatch API calls to a given driver vendor. Some of
the libraries are simply wrappers to the main dispatcher.
</para>
@ -142,14 +142,14 @@ ldconfig</userinput></screen>
While installing this package can help prevent a lot of issues down the
road, this package can come with some caveats and all of them are in
relation to BLFS. BLFS naturally expects that the only OpenGL vendor is
<application>Mesa</application>, so the instructions will thus assume
Mesa, so the instructions will thus assume
that this package has not been installed. The following have known
issues, and solutions:
</para>
<itemizedlist>
<listitem>
<para><application>Mesa:</application> In BLFS, a patch is listed in
<para>Mesa: In BLFS, a patch is listed in
the <ulink url="&blfs-svn;/x/mesa.html">Mesa</ulink> page and will
instruct you to apply it. This will cause an issue unless you explictly
tell the build system not to link against this package's libraries,
@ -160,23 +160,23 @@ ldconfig</userinput></screen>
package it tries to link against.</para>
<para>Either don't apply that patch or follow this book's <xref
linkend="mesa"/> page instead. Thanks to
<application>Mesa's</application> build system autodetecting if
<application>libglvnd</application> is installed, the installation
Mesa's build system autodetecting if
libglvnd is installed, the installation
instructions don't change that much between this book and BLFS. The
main differences are lib32 support and not listing the demos
patch.</para>
</listitem>
<listitem>
<para><application>GLU:</application> In BLFS, the <ulink
<para>GLU: In BLFS, the <ulink
url="&blfs-svn;/x/glu.html">GLU</ulink> page explictly sets the GL
vendor to be <application>Mesa</application> as the build system will
otherwise expect <application>libglvnd</application> and
vendor to be Mesa as the build system will
otherwise expect libglvnd and
<filename class="libraryfile">libOpenGL</filename> to be installed.
While the BLFS page instructions lead to a successful compilation, the
resulting library does not function properly. You should follow the
<ulink url="&slfs-website;/general/glu.html">SLFS GLU</ulink> page
instead. It also does check if the vendor is
<application>Mesa</application>.</para>
Mesa.</para>
</listitem>
</itemizedlist>

6
shareddeps/drivers/libva.xml
View File

@ -25,7 +25,7 @@
<title>Introduction to libva</title>
<para>
The <application>libva</application> package contains a library which
The libva package contains a library which
provides access to hardware accelerated video processing, using hardware
to accelerate video processing in order to offload the central
processing unit (CPU) to decode and encode compressed digital video. The VA
@ -102,7 +102,7 @@
</caution>
-->
<para>
Install <application>libva</application> by running the following
Install libva by running the following
commands:
</para>
@ -128,7 +128,7 @@ ninja</userinput></screen>
<title>lib32 Installation of libva</title>
<para>
Install lib32-<application>libva</application> by running the following
Install lib32-libva by running the following
commands:
</para>

6
shareddeps/drivers/libvdpau-va-gl.xml
View File

@ -25,7 +25,7 @@
<title>Introduction to libvdpau-va-gl</title>
<para>
The <application>libvdpau-va-gl</application> package contains a library
The libvdpau-va-gl package contains a library
which implements the VDPAU library. Libvdpau_va_gl uses OpenGL under the
hood to accelerate drawing and scaling and the VA-API (if available) to
accelerate video decoding. For now VA-API is available on some Intel
@ -62,7 +62,7 @@
<title>Installation of libvdpau-va-gl</title>
<para>
Install <application>libvdpau-va-gl</application> by running the following
Install libvdpau-va-gl by running the following
commands:
</para>
@ -93,7 +93,7 @@ make</userinput></screen>
<title>lib32 Installation of libvdpau-va-gl</title>
<para>
Install lib32-<application>libvdpau-va-gl</application> by running the
Install lib32-libvdpau-va-gl by running the
following commands:
</para>

6
shareddeps/drivers/libvdpau.xml
View File

@ -25,7 +25,7 @@
<title>Introduction to libvdpau</title>
<para>
The <application>libvdpau</application> package contains a library which
The libvdpau package contains a library which
implements the VDPAU library.
</para>
@ -101,7 +101,7 @@
<title>Installation of libvdpau</title>
<para>
Install <application>libvdpau</application> by running the following
Install libvdpau by running the following
commands:
</para>
@ -130,7 +130,7 @@ ninja</userinput></screen>
<title>lib32 Installation of libvdpau</title>
<para>
Install lib32-<application>libvdpau</application> by running the following
Install lib32-libvdpau by running the following
commands:
</para>

4
shareddeps/drivers/libyaml.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to libyaml</title>
<para>
The <application>yaml</application> package contains a C
The yaml package contains a C
library for parsing and emitting YAML (YAML Ain't Markup
Language) code.
</para>
@ -52,7 +52,7 @@
<title>Installation of libyaml</title>
<para>
Install <application>libyaml</application> by running the following
Install libyaml by running the following
commands:
</para>

84
shareddeps/drivers/llvm.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to LLVM</title>
<para>
The <application>LLVM</application> package contains a collection of
The LLVM package contains a collection of
modular and reusable compiler and toolchain technologies. The Low Level
Virtual Machine (LLVM) Core libraries provide a modern source and
target-independent optimizer, along with code generation support for many
@ -31,18 +31,18 @@
</para>
<para>
<application>Clang</application> provides new C, C++, Objective C
and Objective C++ front-ends for <application>LLVM</application> and is
Clang provides new C, C++, Objective C
and Objective C++ front-ends for LLVM and is
required by some desktop packages such as
<ulink url="&blfs-svn;/xsoft/firefox.html">Firefox</ulink>
and for <xref linkend="rustc"/> if that is built using the system
<application>LLVM</application>.
LLVM.
</para>
<para>
The <application>Compiler RT</application> package provides
The Compiler RT package provides
runtime sanitizer and profiling libraries for developers who use
<application>Clang</application> and <application>LLVM</application>.
Clang and LLVM.
</para>
<para>
@ -146,7 +146,7 @@ sed '/LLVM_THIRD_PARTY_DIR/s@../third-party@third-party-&llvm-version;.src@' \
-i cmake/modules/HandleLLVMOptions.cmake</userinput></screen>
<para>
Extract <application>clang</application> into
Extract clang into
the source tree by running the following commands:
</para>
@ -154,7 +154,7 @@ sed '/LLVM_THIRD_PARTY_DIR/s@../third-party@third-party-&llvm-version;.src@' \
mv tools/clang-&llvm-version;.src tools/clang</userinput></screen>
<para>
Extract <application>compiler-rt</application> into
Extract compiler-rt into
the source tree by running the following commands:
</para>
@ -164,7 +164,7 @@ mv projects/compiler-rt-&llvm-version;.src projects/compiler-rt</userinput></scr
<para>
There are many Python scripts in this package which use
<command>/usr/bin/env python</command> to access the system Python
which on LFS is <application>Python3</application>. Use the following
which on LFS is Python3. Use the following
command to fix these scripts:
</para>
@ -179,7 +179,7 @@ mv projects/compiler-rt-&llvm-version;.src projects/compiler-rt</userinput></scr
<screen><userinput>sed 's/utility/tool/' -i utils/FileCheck/CMakeLists.txt</userinput></screen>
<para>
Install <application>LLVM</application> by running the following
Install LLVM by running the following
commands:
</para>
@ -264,8 +264,8 @@ ldconfig</userinput></screen>
<para>
<parameter>-D LLVM_ENABLE_FFI=ON</parameter>: This switch allows
<application>LLVM</application> to use
<application>libffi</application>.
LLVM to use
libffi.
</para>
<para>
@ -273,7 +273,7 @@ ldconfig</userinput></screen>
the libraries as static and links all of them into an unique shared one.
This is the recommended way of building a shared library and is required
by <xref linkend="rustc"/> in order to build against the system-installed
<application>LLVM</application>.
LLVM.
</para>
<para>
@ -345,7 +345,7 @@ ldconfig</userinput></screen>
<option>-D BUILD_SHARED_LIBS=ON</option>: if used instead of
<parameter>-D LLVM_BUILD_LLVM_DYLIB=ON</parameter> and
<parameter>-D LLVM_LINK_LLVM_DYLIB=ON</parameter>, builds all the
<application>LLVM</application> libraries (about 60) as shared
LLVM libraries (about 60) as shared
libraries instead of static.
</para>
@ -362,7 +362,7 @@ ldconfig</userinput></screen>
files to make <xref linkend='gSSP'/> enabled by default for
<command>clang</command> and <command>clang++</command>, so
the default configuration of their SSP feature will be consistent
with <application>GCC</application>:
with GCC:
</para>
<screen role='root'><userinput>mkdir -pv /etc/clang &amp;&amp;
@ -491,7 +491,7 @@ done</userinput></screen>
<term><command>clang</command></term>
<listitem>
<para>
is the <application>Clang</application> C, C++,
is the Clang C, C++,
and Objective-C compiler
</para>
<indexterm zone="llvm clang">
@ -709,7 +709,7 @@ done</userinput></screen>
<term><command>llc</command></term>
<listitem>
<para>
is the <application>LLVM</application> static compiler
is the LLVM static compiler
</para>
<indexterm zone="llvm llc">
<primary sortas="b-llc">llc</primary>
@ -722,7 +722,7 @@ done</userinput></screen>
<listitem>
<para>
is used to directly execute programs from
<application>LLVM</application> bitcode
LLVM bitcode
</para>
<indexterm zone="llvm lli">
<primary sortas="b-lli">lli</primary>
@ -747,7 +747,7 @@ done</userinput></screen>
<term><command>llvm-ar</command></term>
<listitem>
<para>
is the <application>LLVM</application> archiver
is the LLVM archiver
</para>
<indexterm zone="llvm llvm-ar">
<primary sortas="b-llvm-ar">llvm-ar</primary>
@ -759,7 +759,7 @@ done</userinput></screen>
<term><command>llvm-as</command></term>
<listitem>
<para>
is the <application>LLVM</application> assembler
is the LLVM assembler
</para>
<indexterm zone="llvm llvm-as">
<primary sortas="b-llvm-as">llvm-as</primary>
@ -771,7 +771,7 @@ done</userinput></screen>
<term><command>llvm-bcanalyzer</command></term>
<listitem>
<para>
is the <application>LLVM</application> bitcode analyzer
is the LLVM bitcode analyzer
</para>
<indexterm zone="llvm llvm-bcanalyzer">
<primary sortas="b-llvm-bcanalyzer">llvm-bcanalyzer</primary>
@ -821,7 +821,7 @@ done</userinput></screen>
<term><command>llvm-config</command></term>
<listitem>
<para>
Prints <application>LLVM</application> compilation options
Prints LLVM compilation options
</para>
<indexterm zone="llvm llvm-config">
<primary sortas="b-llvm-config">llvm-config</primary>
@ -943,7 +943,7 @@ done</userinput></screen>
<term><command>llvm-diff</command></term>
<listitem>
<para>
is the <application>LLVM</application> structural
is the LLVM structural
'<command>diff</command>'
</para>
<indexterm zone="llvm llvm-diff">
@ -956,7 +956,7 @@ done</userinput></screen>
<term><command>llvm-dis</command></term>
<listitem>
<para>
is the <application>LLVM</application> disassembler
is the LLVM disassembler
</para>
<indexterm zone="llvm llvm-dis">
<primary sortas="b-llvm-dis">llvm-dis</primary>
@ -1031,7 +1031,7 @@ done</userinput></screen>
<listitem>
<para>
is used to extract a function from an
<application>LLVM</application> module
LLVM module
</para>
<indexterm zone="llvm llvm-extract">
<primary sortas="b-llvm-extract">llvm-extract</primary>
@ -1108,7 +1108,7 @@ done</userinput></screen>
<term><command>llvm-link</command></term>
<listitem>
<para>
is the <application>LLVM</application> linker
is the LLVM linker
</para>
<indexterm zone="llvm llvm-link">
<primary sortas="b-llvm-link">llvm-link</primary>
@ -1132,7 +1132,7 @@ done</userinput></screen>
<term><command>llvm-lto</command></term>
<listitem>
<para>
is the <application>LLVM</application> LTO (link time optimization)
is the LLVM LTO (link time optimization)
linker
</para>
<indexterm zone="llvm llvm-lto">
@ -1219,7 +1219,7 @@ done</userinput></screen>
<term><command>llvm-nm</command></term>
<listitem>
<para>
is used to list <application>LLVM</application> bitcode
is used to list LLVM bitcode
and object file's symbol table
</para>
<indexterm zone="llvm llvm-nm">
@ -1244,7 +1244,7 @@ done</userinput></screen>
<term><command>llvm-objdump</command></term>
<listitem>
<para>
is an <application>LLVM</application> object file dumper
is an LLVM object file dumper
</para>
<indexterm zone="llvm llvm-objdump">
<primary sortas="b-llvm-objdump">llvm-objdump</primary>
@ -1305,7 +1305,7 @@ done</userinput></screen>
<term><command>llvm-ranlib</command></term>
<listitem>
<para>
is used to generate an index for a <application>LLVM</application>
is used to generate an index for a LLVM
archive
</para>
<indexterm zone="llvm llvm-ranlib">
@ -1381,7 +1381,7 @@ done</userinput></screen>
<term><command>llvm-rtdyld</command></term>
<listitem>
<para>
is the <application>LLVM</application> MC-JIT tool
is the LLVM MC-JIT tool
</para>
<indexterm zone="llvm llvm-rtdyld">
<primary sortas="b-llvm-rtdyld">llvm-rtdyld</primary>
@ -1393,7 +1393,7 @@ done</userinput></screen>
<term><command>llvm-size</command></term>
<listitem>
<para>
is the <application>LLVM</application> object size dumper
is the LLVM object size dumper
</para>
<indexterm zone="llvm llvm-size">
<primary sortas="b-llvm-size">llvm-size</primary>
@ -1405,7 +1405,7 @@ done</userinput></screen>
<term><command>llvm-split</command></term>
<listitem>
<para>
is the <application>LLVM</application> module splitter
is the LLVM module splitter
</para>
<indexterm zone="llvm llvm-split">
<primary sortas="b-llvm-split">llvm-split</primary>
@ -1455,7 +1455,7 @@ done</userinput></screen>
<term><command>llvm-tblgen</command></term>
<listitem>
<para>
is the <application>LLVM</application> Target Description
is the LLVM Target Description
To C++ Code Generator
</para>
<indexterm zone="llvm llvm-tblgen">
@ -1468,7 +1468,7 @@ done</userinput></screen>
<term><command>llvm-tli-checker</command></term>
<listitem>
<para>
is the <application>LLVM</application> TargetLibraryInfo
is the LLVM TargetLibraryInfo
versus SDK checker
</para>
<indexterm zone="llvm llvm-tli-checker">
@ -1519,7 +1519,7 @@ done</userinput></screen>
<term><command>opt</command></term>
<listitem>
<para>
is the <application>LLVM</application> optimizer
is the LLVM optimizer
</para>
<indexterm zone="llvm opt">
<primary sortas="b-opt">opt</primary>
@ -1555,8 +1555,8 @@ done</userinput></screen>
<term><command>scan-build</command></term>
<listitem>
<para>
is a <application>Perl</application> script that invokes the
<application>Clang</application> static analyzer
is a Perl script that invokes the
Clang static analyzer
</para>
<indexterm zone="llvm scan-build">
<primary sortas="b-scan-build">scan-build</primary>
@ -1568,8 +1568,8 @@ done</userinput></screen>
<term><command>scan-build-py</command></term>
<listitem>
<para>
is a <application>Python</application> script that invokes the
<application>Clang</application> static analyzer
is a Python script that invokes the
Clang static analyzer
</para>
<indexterm zone="llvm scan-build-py">
<primary sortas="b-scan-build-py">scan-build-py</primary>
@ -1581,7 +1581,7 @@ done</userinput></screen>
<term><command>scan-view</command></term>
<listitem>
<para>
is a viewer for <application>Clang</application> static analyzer
is a viewer for Clang static analyzer
results
</para>
<indexterm zone="llvm scan-view">
@ -1594,7 +1594,7 @@ done</userinput></screen>
<term><command>verify-uselistorder</command></term>
<listitem>
<para>
is the <application>LLVM</application> tool to verify use-list
is the LLVM tool to verify use-list
order
</para>
<indexterm zone="llvm verify-uselistorder">

2
shareddeps/drivers/mako.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to Mako</title>
<para>
<application>Mako</application> is a Python module that implements hyperfast
Mako is a Python module that implements hyperfast
and lightweight templating for the Python platform.
</para>

26
shareddeps/drivers/mesa.xml
View File

@ -20,14 +20,14 @@
<title>Introduction to Mesa</title>
<para>
<application>Mesa</application> offers a wide variety of graphic
Mesa offers a wide variety of graphic
software, like the OpenGL libraries and drivers, Vulkan drivers,
and other drivers.
</para>
<para>
Every driver from this package works with <xref linkend="libglvnd"/>. The
package will auto-detect a <application>libglvnd</application>
package will auto-detect a libglvnd
installation if present and will link against the libraries provided by
that package. Thus, the OpenGL libraries provided by this package will
not be built, only the drivers for OpenGL.
@ -43,7 +43,7 @@
<note>
<para>
<application>Mesa</application> is updated relatively often. You may
Mesa is updated relatively often. You may
want to use the latest available &mesa-major-minor;.x mesa version.
</para>
</note>
@ -112,8 +112,8 @@
<para>
<xref role="first" linkend="libva"/> (to provide VA-API support for some
Gallium3D drivers, note that there is a circular dependency. You must
build <application>libva</application> first without EGL and GLX support,
install this package, and rebuild <application>libva</application>)
build libva first without EGL and GLX support,
install this package, and rebuild libva)
</para>
</listitem>
<listitem>
@ -159,7 +159,7 @@
<xref linkend="nettle"/>,
<ulink url="&blfs-svn;/general/valgrind.html">valgrind</ulink>,
<ulink url="&slfs-website;/general/mesa-demos.html">Mesa-Demos</ulink>
(provides more than 300 demos to test <application>Mesa</application>),
(provides more than 300 demos to test Mesa),
<ulink url="https://omxilurceforge.net/">Bellagio OpenMAX Integration
Layer</ulink> (for mobile platforms), and
<ulink url="https://github.com/tizonia/tizonia-openmax-il/wiki/Tizonia-OpenMAX-IL/">
@ -172,7 +172,7 @@
<title>Installation of Mesa</title>
<para>
Install <application>Mesa</application> by running the following
Install Mesa by running the following
commands:
</para>
@ -219,7 +219,7 @@ ninja</userinput></screen>
<title>lib32 Installation of Mesa</title>
<para>
Install lib32-<application>Mesa</application> by running the following
Install lib32-Mesa by running the following
commands:
</para>
@ -316,7 +316,7 @@ ldconfig</userinput></screen>
<listitem>
<para>
<literal>virgl</literal> (for QEMU virtual GPU
with <application>virglrender</application> support)
with virglrender support)
</para>
</listitem>
<listitem>
@ -332,7 +332,7 @@ ldconfig</userinput></screen>
<listitem>
<para>
<literal>llvmpipe</literal> (<literal>softpipe</literal> but uses
<application>LLVM</application> to increase performance)
LLVM to increase performance)
</para>
</listitem>
<listitem>
@ -398,7 +398,7 @@ ldconfig</userinput></screen>
<para>
<literal>nouveau</literal> (for GTX 16XX, RTX 20XX, or newer NVIDIA GPUs;
this driver is maturing and is already quite performant, although less so
than the <application>NVIDIA</application> driver; however, it is a good
than the NVIDIA driver; however, it is a good
replacement, especially when used with <literal>zink</literal>)
</para>
</listitem>
@ -627,7 +627,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libgbm</filename></term>
<listitem>
<para>
is the <application>Mesa</application> Graphics Buffer
is the Mesa Graphics Buffer
Manager library
</para>
<indexterm zone="mesa libgbm">
@ -640,7 +640,7 @@ ldconfig</userinput></screen>
<term><filename class="libraryfile">libglapi</filename></term>
<listitem>
<para>
is <application>Mesa's</application> implementation of the OpenGL
is Mesa's implementation of the OpenGL
API; provided if <xref linkend="libglvnd"/> is not installed
</para>
<indexterm zone="mesa libglapi">

6
shareddeps/drivers/nvidia-egl.xml
View File

@ -18,8 +18,8 @@
<title>Introduction to NVIDIA EGL Libraries</title>
<para>
The <application>NVIDIA EGL Libraries</application> allow the EGL drivers
for the <application>NVIDIA</application> driver to function properly. If
The NVIDIA EGL Libraries allow the EGL drivers
for the NVIDIA driver to function properly. If
you are not installing <xref linkend="nvidia"/>, skip this package.
</para>
@ -149,7 +149,7 @@ done</userinput></screen>
<term><filename class="libraryfile">libnvidia-egl-wayland</filename></term>
<listitem>
<para>
provides client-side <application>Wayland</application> EGL
provides client-side Wayland EGL
application support
</para>
<indexterm zone="nvidia-egl libnvidia-egl-wayland">

58
shareddeps/drivers/nvidia.xml
View File

@ -20,7 +20,7 @@
<title>Introduction to NVIDIA</title>
<para>
The <application>NVIDIA</application> proprietary driver contains
The NVIDIA proprietary driver contains
firmware, kernel drivers, userland drivers pertaining to OpenGL,
Vulkan, and hardware acceleration, and provides useful utilites for
NVIDIA cards. If you don't have a NVIDIA GPU, skip to the next package.
@ -159,7 +159,7 @@
</para></important>
<para>
Extract the <application>NVIDIA</application> driver runfile and
Extract the NVIDIA driver runfile and
navigate to the extracted directory:
</para>
@ -169,7 +169,7 @@ cd NVIDIA-Linux-x86_64-&nvidia-version;</userinput></screen>
<!--
<para>
Apply a patch for the proprietary kernel module type for the driver for
compatibility with <application>linux-6.15</application>:
compatibility with linux-6.15:
</para>
<screen><userinput>patch -d kernel -Np1 -i ../../NVIDIA-&nvidia-version;-kernel_gpl_cachyos-1.patch</userinput></screen>
@ -269,7 +269,7 @@ cd NVIDIA-Linux-x86_64-&nvidia-version;</userinput></screen>
<important>
<para>
When you rebuild/upgrade the kernel, you will also need to reinstall
the <application>NVIDIA</application> kernel modules.
the NVIDIA kernel modules.
</para>
<para>
@ -366,7 +366,7 @@ install -vm644 ../manifest-NVIDIA-&nv-manifest-version; \
<sect2 revision="sysv">
<title>Installation of NVIDIA-Powerd</title>
<para>
If you want <application>NVIDIA-Powerd</application>, which can suspend
If you want NVIDIA-Powerd, which can suspend
and hibernate if asked to, then run the following commands as the &root;
user to install the daemon and the bootscripts:
</para>
@ -385,7 +385,7 @@ rm -rf NVIDIA-sysv-bootscripts-&nv-sysv-bs;</userinput></screen>
<sect2 revision="systemd">
<title>Installation of NVIDIA-Powerd</title>
<para>
If you want <application>NVIDIA-Powerd</application>, which can suspend
If you want NVIDIA-Powerd, which can suspend
and hibernate if asked to, then run the following commands as the &root;
user to install the daemon and the Systemd unit files:
</para>
@ -565,9 +565,9 @@ EOF</userinput></screen>
Direct Rendering Infrastructure.
</para></footnote>
drivers or driver stubs. Likewise, it does not install a
<application>pkgconf</application> file saying where to find the
pkgconf file saying where to find the
associated files. The files aren't needed with this driver. However,
some applications expect the <application>pkg-config</application> file
some applications expect the pkg-config file
to exist, namely <xref linkend="xorg-server"/>. Create one now as the
&root; user:
</para>
@ -590,7 +590,7 @@ EOF</userinput></screen>
any library in <filename class="libraryfile">/usr/lib/dri</filename>.
If you are worried that an application will try to link against
non-existent libraries, you can compile <xref linkend="mesa"/> to get
these libraries and a real <application>pkg-config</application> file.
these libraries and a real pkg-config file.
Note that those libraries will not be used when this driver is in use.
</para>
@ -747,9 +747,9 @@ EOF</userinput></screen>
<term><command>nvidia-xconfig</command></term>
<listitem>
<para>
manipulates <application>X11</application> configuration files
to allow the <application>NVIDIA</application> driver to be used
when starting <application>X11</application>
manipulates X11 configuration files
to allow the NVIDIA driver to be used
when starting X11
</para>
<indexterm zone="nvidia nvidia-xconfig">
<primary sortas="b-nvidia-xconfig">nvidia-xconfig</primary>
@ -761,7 +761,7 @@ EOF</userinput></screen>
<term><filename class="libraryfile">libcudadebugger</filename></term>
<listitem>
<para>
allows debugging <application>CUDA</application> applications
allows debugging CUDA applications
</para>
<indexterm zone="nvidia libcudadebugger">
<primary sortas="c-libcudadebugger">libcudadebugger</primary>
@ -774,7 +774,7 @@ EOF</userinput></screen>
<listitem>
<para>
provides support for applications that use
<application>CUDA</application>
CUDA
</para>
<indexterm zone="nvidia libcuda">
<primary sortas="c-libcuda">libcuda</primary>
@ -786,7 +786,7 @@ EOF</userinput></screen>
<term><filename class="libraryfile">libEGL_nvidia</filename></term>
<listitem>
<para>
provides the <application>NVIDIA</application> implementation
provides the NVIDIA implementation
of EGL
</para>
<indexterm zone="nvidia libEGL_nvidia">
@ -799,7 +799,7 @@ EOF</userinput></screen>
<term><filename class="libraryfile">libGLESv2_nvidia</filename></term>
<listitem>
<para>
provides the <application>NVIDIA</application> implementation
provides the NVIDIA implementation
of OpenGL ES v2
</para>
<indexterm zone="nvidia libGLESv2_nvidia">
@ -812,7 +812,7 @@ EOF</userinput></screen>
<term><filename class="libraryfile">libGLX_nvidia</filename></term>
<listitem>
<para>
provides the <application>NVIDIA</application> implementation
provides the NVIDIA implementation
of GLX
</para>
<indexterm zone="nvidia libGLX_nvidia">
@ -825,7 +825,7 @@ EOF</userinput></screen>
<term><filename class="libraryfile">libglxserver_nvidia</filename></term>
<listitem>
<para>
is the <application>NVIDIA</application> X11 GLX extension module
is the NVIDIA X11 GLX extension module
</para>
<indexterm zone="nvidia libglxserver_nvidia">
<primary sortas="c-libglxserver_nvidia">libglxserver_nvidia</primary>
@ -923,7 +923,7 @@ EOF</userinput></screen>
<listitem>
<para>
provides an interface to capture and optionally encode the
framebuffer of an <application>X11</application> server screen
framebuffer of an X11 server screen
</para>
<indexterm zone="nvidia libnvidia-fbc">
<primary sortas="c-libnvidia-fbc">libnvidia-fbc</primary>
@ -987,7 +987,7 @@ EOF</userinput></screen>
<listitem>
<para>
for <command>nvidia-settings</command>; utilizes
<application>GTK-3</application>
GTK-3
</para>
<indexterm zone="nvidia libnvidia-gtk3">
<primary sortas="c-liblnvidia-gtk3">libnvidia-gtk3</primary>
@ -1035,7 +1035,7 @@ EOF</userinput></screen>
<term><filename class="libraryfile">libnvidia-opencl</filename></term>
<listitem>
<para>
provides <application>NVIDIA</application>'s implementation of
provides NVIDIA's implementation of
the OpenCL API standard
</para>
<indexterm zone="nvidia libnvidia-opencl">
@ -1100,8 +1100,8 @@ EOF</userinput></screen>
<term><filename class="libraryfile">libnvidia-tls</filename></term>
<listitem>
<para>
provides TLS support for the <application>NVIDIA
</application> OpenGL implementations
provides TLS support for the NVIDIA
OpenGL implementations
</para>
<indexterm zone="nvidia libnvidia-tls">
<primary sortas="c-libnvidia-tls">libnvidia-tls</primary>
@ -1114,7 +1114,7 @@ EOF</userinput></screen>
<listitem>
<para>
is required for <command>nvidia-settings</command> on
<application>Wayland</application>
Wayland
</para>
<indexterm zone="nvidia libnvidia-wayland-client">
<primary sortas="c-libnvidia-wayland-client">libnvidia-wayland-client</primary>
@ -1126,7 +1126,7 @@ EOF</userinput></screen>
<term><filename class="libraryfile">libvdpau_nvidia</filename></term>
<listitem>
<para>
provides the <application>NVIDIA</application> implementation for
provides the NVIDIA implementation for
the VDPAU API
</para>
<indexterm zone="nvidia libvdpau_nvidia">
@ -1151,7 +1151,7 @@ EOF</userinput></screen>
<term><filename class="libraryfile">nvngx</filename></term>
<listitem>
<para>
provides DLSS support for use with <application>Wine</application>
provides DLSS support for use with Wine
</para>
<indexterm zone="nvidia nvngx">
<primary sortas="c-nvngx">nvngx</primary>
@ -1175,7 +1175,7 @@ EOF</userinput></screen>
<term><filename class="libraryfile">nvidia-drm_gbm</filename></term>
<listitem>
<para>
is the <application>NVIDIA</application> GBM driver
is the NVIDIA GBM driver
</para>
<indexterm zone="nvidia nvidia-drm_gbm">
<primary sortas="c-nvidia-drm_gbm">nvidia-drm_gbm</primary>
@ -1187,8 +1187,8 @@ EOF</userinput></screen>
<term><filename class="libraryfile">nvidia_drv</filename></term>
<listitem>
<para>
is the <application>NVIDIA</application> <application>X11
</application> driver
is the NVIDIA X11
driver
</para>
<indexterm zone="nvidia nvidia_drv">
<primary sortas="c-nvidia_drv">nvidia_drv</primary>

4
shareddeps/drivers/pciutils.xml
View File

@ -21,7 +21,7 @@
<title>Introduction to PCI Utils</title>
<para>
The <application>PCI Utils</application> package contains
The PCI Utils package contains
a set of programs for listing PCI devices, inspecting
their status and setting their configuration registers.
</para>
@ -60,7 +60,7 @@
-i Makefile</userinput></screen>
<para>
Install <application>PCI Utils</application> by
Install PCI Utils by
running the following commands:
</para>

Some files were not shown because too many files have changed in this diff Show More