Ignore:
Timestamp:
12/09/2022 07:53:09 AM (17 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
xry111/arm64, xry111/arm64-12.0
Children:
ca4faad
Parents:
dfe9593 (diff), 4640b37d (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Merge remote-tracking branch 'origin/trunk' into xry111/arm64

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter08/ninja.xml

    rdfe9593 ra747ea2  
    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, <command>ninja</command> normally utilizes the greatest
     53    possible number of processes 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 <command>ninja</command> 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 <command>ninja</command>, 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
     
    6363    <screen>export NINJAJOBS=4</screen>
    6464
    65     will limit ninja to four parallel processes.</para>
     65    will limit <command>ninja</command> 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 <command>ninja</command> 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.