Adjusted sections pertaining and fix link issue.

Link issue has to deal with /introduction/welcome/important.xml where var &blfs-svn; was spelt as &blvs-svn;.
This commit is contained in:
Zeckmathederg 2024-07-06 05:47:01 -06:00
parent 74e832535a
commit 054deb517a
4 changed files with 41 additions and 32 deletions

View File

@ -42,6 +42,9 @@
<listitem>
<para>July 6th, 2024</para>
<itemizedlist>
<listitem>
<para>[Zeckmathederg] - Adjusted sections pertaining and fix link issue.</para>
</listitem>
<listitem>
<para>[Zeckmathederg] - Added '--disable-static' to lib32-libvorbis.</para>
</listitem>

View File

@ -13,7 +13,7 @@
<para>
BLFS has more information regarding compilation, /usr vs /usr/local,
boot scripts, etc. at
<ulink url="&blvs-svn;/introduction/important.html"/>.
<ulink url="&blfs-svn;/introduction/important.html"/>.
Unlike this book, this would be a chapter in BLFS.
A lot of that information has been omitted as this book is more linear
and doesn't follow how BLFS follows. However, we will cover some bases

View File

@ -11,34 +11,40 @@
<title>Meson Toolchain Files</title>
<para>
Most applications that rely on the <application>Meson</application>
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>
binary (or rather symlink that uses a certain personality file) to use,
<command>llvm-config</command> to use, etc. This is required for Mesa's
Nouveau and/or Swrast Vulkan drivers. It is also needed for Gstreamer
(not in the book), which is a recommended dependency of
<xref linkend="wine"/>.
</para>
<sect2>
<title>Introduction to Meson Toolchain Files</title>
<para>
Most applications that rely on the <application>Meson</application>
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>
binary (or rather symlink that uses a certain personality file) to use,
<command>llvm-config</command> to use, etc. This is required for Mesa's
Nouveau and/or Swrast Vulkan drivers. It is also needed for Gstreamer
(not in the book), which is a recommended dependency of
<xref linkend="wine"/>.
</para>
<para>
There are two <application>Meson</application> files: the cross
toolchain file and the native toolchain file. There are different situations
for using either.
</para>
<para>
There are two <application>Meson</application> files: the cross
toolchain file and the native toolchain file. There are different situations
for using either.
</para>
<para>
The instructions below will show how to create and use the files if
necessary.
</para>
<bridgehead renderas="sect3">Meson Toolchain File Dependencies</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
<xref linkend="pkgconf"/> (runtime)
</para>
</sect2>
<sect2 role="installation">
<title>Creating the Cross Toolchain File</title>

View File

@ -26,15 +26,15 @@
</para>
<sect2>
<title>Creating the personalites</title>
<title>Creating the personalites</title>
<para>
Create the following personalties as the
<systemitem class="username">root</systemitem>
user:
Create the following personalties as the
<systemitem class="username">root</systemitem>
user:
</para>
<screen role="root"><userinput>mkdir -pv /usr/share/pkgconfig/personality.d
<screen role="root"><userinput>mkdir -pv /usr/share/pkgconfig/personality.d
cat &gt; /usr/share/pkgconfig/personality.d/x86_64-pc-linux-gnu.personality &lt;&lt; "EOF"
<literal>Triplet: x86_64-pc-linux-gnu