Changeset 367853f

Timestamp:

03/30/2019 10:51:46 PM (5 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 9.0, 9.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

178639f

Parents:

ba31c2b

Message:

Minor wording changes in sw notes

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@21417 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• introduction/important/building-notes.xml (modified) (11 diffs)

introduction/important/building-notes.xml

@@ -460 +460 @@
       There are now three different build systems in common use for
       converting C or C++ source code into compiled programs or
-      libraries, and their details (particularly, finding out about available
+      libraries and their details (particularly, finding out about available
       options and their default values) differ. It may be easiest to understand
-      the issues caused by some choices (typically, slow execution, or
-      unexpected use of, or omission of, optimizatons) by starting with the item
-      which drew attention to this, the CFLAGS and CXXFLAGS.
+      the issues caused by some choices (typically slow execution or
+      unexpected use of, or omission of, optimizatons) by starting with 
+      the CFLAGS and CXXFLAGS environment variables.
     </para>
 
@@ -470 +470 @@
       Most LFS and BLFS builders are probably aware of the basics of CFLAGS
       and CXXFLAGS for altering how a program is compiled. Typically, some
-      form of optimization is used for a released program (-O2 or -O3),
-      sometimes with the creation of debug symbols (-g) when using -O2.
+      form of optimization is used by upstream developers (-O2 or -O3),
+      sometimes with the creation of debug symbols (-g), as defaults.
     </para>
 
@@ -477 +477 @@
       If there are contradictory flags (e.g. multiple different -O values),
       the <emphasis>last</emphasis> value will be used. Sometimes this means
-      that flags specifiedi in environment variables will be picked up before
+      that flags specified in environment variables will be picked up before
       values hardcoded in the Makefile, and therefore ignored.  For example,
       where a user specifies '-O2' and that is followed by '-O3' the build will
@@ -495 +495 @@
     </para>
 
-    <bridgehead renderas="sect3">Autotools with Make</bridgehead>
+    <bridgehead renderas="sect3" id="autotools-info">Autotools with Make</bridgehead>
 
       <para>
@@ -504 +504 @@
 
       <para>
-        Sometimes, running <command>./configure --help</command> will produce
+        Sometimes running <command>./configure --help</command> will produce
         useful options about switches which might be used.  At other times,
-        after looking at the output from a run of configure you may need to look
+        after looking at the output from configure you may need to look
         at the details of the script to find out what it was actually searching
         for.
@@ -516 +516 @@
        any flags which would otherwise be used (<emphasis>variously</emphasis>:
        ignored, used to replace the programmer's suggestion, used before the
-       programmer's suggestion, used after the programmer's suggestion).
+       programmer's suggestion, or used after the programmer's suggestion).
       </para>
 
@@ -528 +528 @@
      </para>
 
-    <bridgehead renderas="sect3">CMake</bridgehead>
+    <bridgehead renderas="sect3" id="cmake-info">CMake</bridgehead>
 
       <para>
@@ -548 +548 @@
         of CMAKE_BUILD_TYPE values, and these affect the flags. The default
         is that this is not set and no flags are generated. Any CFLAGS or
-        CXXFLAGS in the environment will be used. If  the programmer has coded
+        CXXFLAGS in the environment will be used. If the programmer has coded
         any debug assertions, those will be enabled unless -DNDEBUG is used.
         The following CMAKE_BUILD_TYPE values will generate the flags shown,
@@ -575 +575 @@
       </para>
 
-    <bridgehead renderas="sect3">Meson</bridgehead>
+    <bridgehead renderas="sect3" id="meson-info">Meson</bridgehead>
 
       <para>
         Meson has some similarities to CMake, but many differences. To get
-        details of the definesthat you may wish to change is slightly involved
-        using meson-0.49.2:
-      </para>
-
-<screen><userinput>meson ..
+        details of the defines that you may wish to change ypu need to do:
+      </para>
+
+<screen><userinput>mkdir build
+cd    build
+meson ..
 meson configure | less</userinput></screen>
 
       <para>
-        After identifying what to set, meson then needs to be reconfigured:
-      </para>
-
-<screen><userinput>meson --prefix=/usr -Dsome_option=true -Dother_option=false --reconfigure</userinput></screen>
+        After identifying what to set, meson then needs to be reconfigured.
+        For example:
+      </para>
+
+<screen><userinput>meson --prefix=/usr -Dbuildtype=&lt;type&gt; -Dother_option=false --reconfigure</userinput></screen>
 
       <para>
         Alternatively, you could remove the build directory where you did this,
-        recreate it, and then run meson with the desired switches.
+        recreate it, and then run meson with the desired options.
       </para>
 
@@ -622 +624 @@
 
       <para>
-        Although the release buildtype is described as enabling -DNDEBUG, and all
+        Although the 'release' buildtype is described as enabling -DNDEBUG, and all
         CMake Release builds pass that, it has so far only been observed (in
         verbose builds) for <xref linkend="mesa"/>. That suggests that it might
@@ -635 +637 @@
       <para>
         To see the details of the commands which are being run in a package using
-        meson, again use 'ninja -v'.
+        meson, use 'ninja -v'.
       </para>