From a3ebe8aa2b3bd19ec757706269fd7e15e5c9c55b Mon Sep 17 00:00:00 2001 From: David Bryant Date: Thu, 8 Dec 2022 17:23:07 -0600 Subject: 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. --- chapter08/ninja.xml | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'chapter08/ninja.xml') diff --git a/chapter08/ninja.xml b/chapter08/ninja.xml index 4f3a25e88..7c72b9598 100644 --- a/chapter08/ninja.xml +++ b/chapter08/ninja.xml @@ -36,10 +36,10 @@ - This section is not strictly required for LFS if not using - systemd. On the other hand, ninja associated to meson makes + This section is not strictly required when LFS does not use + systemd. On the other hand, Ninja, along with Meson, makes a powerful build system combination, - which is expected to be used more and more often. It is required for + which will probably be used more and more often. It is required for several packages in the BLFS book. @@ -49,12 +49,12 @@ Installation of Ninja - When run, ninja normally runs a maximum number of processes - in parallel. By default this is the number of cores on the system - plus two. In some cases this can overheat a CPU or run a system out - of memory. If run from the command line, passing a -jN parameter - will limit the number of parallel processes, but some packages - embed the execution of ninja and do not pass a -j parameter. + When run, ninja normally utilizes the greatest possible number of processes + in parallel. By default this is the number of cores on the system, + plus two. This may overheat the CPU, or make the system run out + of memory. When ninja is invoked from the command line, passing the -jN parameter + will limit the number of parallel processes. Some packages + embed the execution of ninja, and do not pass the -j parameter on to it. Using the optional procedure below allows a user to limit the number of parallel processes via an environment variable, @@ -64,8 +64,8 @@ will limit ninja to four parallel processes. - If desired, add the capability to use the environment variable - NINJAJOBS by running: + If desired, make ninja recognize the environment variable + NINJAJOBS by running the stream editor: sed -i '/int Guess/a \ int j = 0;\ @@ -84,7 +84,7 @@ --bootstrap - This parameter forces ninja to rebuild itself for the current + This parameter forces Ninja to rebuild itself for the current system. -- cgit v1.2.3-54-g00ecf From 4640b37d9680598de7979b830c0c9dc05615d9cd Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Fri, 9 Dec 2022 15:40:14 +0800 Subject: ninja: style "ninja" (for the program) with Or the mix up of "ninja" and "Ninja" will seem puzzling... --- chapter08/ninja.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'chapter08/ninja.xml') diff --git a/chapter08/ninja.xml b/chapter08/ninja.xml index 7c72b9598..74626e30c 100644 --- a/chapter08/ninja.xml +++ b/chapter08/ninja.xml @@ -49,12 +49,12 @@ Installation of Ninja - When run, ninja normally utilizes the greatest possible number of processes - in parallel. By default this is the number of cores on the system, + When run, ninja normally utilizes the greatest + possible number of processes in parallel. By default this is the number of cores on the system, plus two. This may overheat the CPU, or make the system run out - of memory. When ninja is invoked from the command line, passing the -jN parameter + of memory. When ninja is invoked from the command line, passing the -jN parameter will limit the number of parallel processes. Some packages - embed the execution of ninja, and do not pass the -j parameter on to it. + embed the execution of ninja, and do not pass the -j parameter on to it. Using the optional procedure below allows a user to limit the number of parallel processes via an environment variable, @@ -62,9 +62,9 @@ export NINJAJOBS=4 - will limit ninja to four parallel processes. + will limit ninja to four parallel processes. - If desired, make ninja recognize the environment variable + If desired, make ninja recognize the environment variable NINJAJOBS by running the stream editor: sed -i '/int Guess/a \ -- cgit v1.2.3-54-g00ecf