Ignore:
Timestamp:
12/08/2022 11:23:07 PM (17 months ago)
Author:
David Bryant <davidbryant@…>
Branches:
11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/update-glibc
Children:
3c07bb9
Parents:
d988306
Message:

Corrected capitalization of the package name. This was hard to do
because some references appear to refer to the program itself, and
not to the package. Corrected English idiom here and there.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter08/ninja.xml

    rd988306 ra3ebe8a  
    3737
    3838    <tip revision="sysv">
    39       <para>This section is not strictly required for LFS if not using
    40       systemd. On the other hand, ninja associated to meson makes
     39      <para>This section is not strictly required when LFS does not use
     40      systemd. On the other hand, Ninja, along with Meson, makes
    4141      a powerful build system combination,
    42       which is expected to be used more and more often. It is required for
     42      which will probably be used more and more often. It is required for
    4343      several packages in <ulink url="&blfs-book;">the BLFS
    4444      book</ulink>.</para>
     
    5050    <title>Installation of Ninja</title>
    5151
    52     <para>When run, ninja normally runs a maximum number of processes
    53     in parallel.  By default this is the number of cores on the system
    54     plus two.  In some cases this can overheat a CPU or run a system out
    55     of memory.  If run from the command line, passing a -jN parameter
    56     will limit the number of parallel processes, but some packages
    57     embed the execution of ninja and do not pass a -j parameter.</para>
     52    <para>When run, ninja normally utilizes the greatest possible number of processes
     53    in parallel.  By default this is the number of cores on the system,
     54    plus two.  This may overheat the CPU, or make the system run out
     55    of memory.  When ninja is invoked from the command line, passing the -jN parameter
     56    will limit the number of parallel processes. Some packages
     57    embed the execution of ninja, and do not pass the -j parameter on to it.</para>
    5858
    5959    <para>Using the <emphasis>optional</emphasis> procedure below allows a user to
     
    6565    will limit ninja to four parallel processes.</para>
    6666
    67     <para>If desired, add the capability to use the environment variable
    68     NINJAJOBS by running:</para>
     67    <para>If desired, make ninja recognize the environment variable
     68    NINJAJOBS by running the stream editor:</para>
    6969
    7070<screen><userinput remap="pre">sed -i '/int Guess/a \
     
    8585        <term><parameter>--bootstrap</parameter></term>
    8686        <listitem>
    87           <para>This parameter forces ninja to rebuild itself for the current
     87          <para>This parameter forces Ninja to rebuild itself for the current
    8888          system.</para>
    8989        </listitem>
Note: See TracChangeset for help on using the changeset viewer.