Changeset 5c7f2497 for x/lib

Timestamp:

02/19/2019 06:16:11 AM (5 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.4, 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:

0891321

Parents:

6dd3533

Message:

Archive ninja. It offers very little more than what is iun LFS.
Tag two packages.

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

File:

• x/lib/qtwebengine.xml (modified) (1 diff)

x/lib/qtwebengine.xml

@@ -245 +245 @@
       <option>NINJAJOBS=4 make</option>: If you patched system ninja in LFS to
       recognize the NINJAJOBS environment variable, this command will run system
-      ninja with the specified number of jobs (i.e. 4). Among the reasons why
-      you might want to do this are: building on a subset of CPUs, either to
-      measure the build time for that number of processors or to run other
-      CPU-intensive tasks on other cores, or to improve the build speed on a
-      less-well endowed 4-core machine. On a machine with a powerful CPU and
-      plenty of RAM, running N+2 jobs (the ninja default for 4+ cores) for the
-      large working sets of the C++ compiles in this package is typically only
-      marginally faster than running N jobs at a time.  But for a machine with
-      less memory it can be much slower.
-    </para>
+      ninja with the specified number of jobs (i.e. 4). 
+      There are several reasons why you might want to do this:</para>
+      
+      <itemizedlist>
+        <listitem>
+          <para> Building on a subset of CPUs allows measuring the build time
+          for that number of processors or to run other CPU-intensive tasks on
+          other cores.</para>
+        </listitem>
+        <listitem>
+          <para>Improving the build speed on a less-well endowed 4-core
+          machine.  On a machine with a powerful CPU and plenty of RAM, running
+          N+2 jobs (the ninja default for 4+ cores) for the large working sets
+          of the C++ compiles in this package is typically only marginally
+          faster than running N jobs at a time.  But for a machine with less
+          memory it can be much slower.</para>
+        </listitem>
+        <listitem>
+          <para>Reducing the number of cores being used on long running, CPU
+          intensive packages may alleviate heat problems.</para>
+        </listitem>
+      </itemizedlist>
 
   </sect2>