diff options
author | Dimitris Apostolou <dimitris.apostolou@icloud.com> | 2020-07-05 16:57:33 +0300 |
---|---|---|
committer | Jan Niklas Hasse <jhasse@bixense.com> | 2020-07-07 13:00:22 +0200 |
commit | 6c5e886aacd98766fe43539c2c8ae7f3ca2af2aa (patch) | |
tree | 65675f90debdf1a963c91bfa871d7f723f1e19cc | |
parent | 48a9fb5d0de6f7bb850863d122ba736b62546746 (diff) | |
download | ninja-6c5e886aacd98766fe43539c2c8ae7f3ca2af2aa.tar.gz |
Fix typos
-rw-r--r-- | doc/manual.asciidoc | 4 | ||||
-rw-r--r-- | src/build.cc | 2 | ||||
-rw-r--r-- | src/ninja.cc | 4 |
3 files changed, 5 insertions, 5 deletions
diff --git a/doc/manual.asciidoc b/doc/manual.asciidoc index 9976ce4..e1ae083 100644 --- a/doc/manual.asciidoc +++ b/doc/manual.asciidoc @@ -899,7 +899,7 @@ set environment variables. On Windows, commands are strings, so Ninja passes the `command` string directly to `CreateProcess`. (In the common case of simply executing a compiler this means there is less overhead.) Consequently the -quoting rules are deterimined by the called program, which on Windows +quoting rules are determined by the called program, which on Windows are usually provided by the C library. If you need shell interpretation of the command (such as the use of `&&` to chain multiple commands), make the command execute the Windows shell by @@ -935,7 +935,7 @@ There are three types of build dependencies which are subtly different. 1. _Explicit dependencies_, as listed in a build line. These are available as the `$in` variable in the rule. Changes in these files - cause the output to be rebuilt; if these file are missing and + cause the output to be rebuilt; if these files are missing and Ninja doesn't know how to build them, the build is aborted. + This is the standard form of dependency to be used e.g. for the diff --git a/src/build.cc b/src/build.cc index a16593b..db28e65 100644 --- a/src/build.cc +++ b/src/build.cc @@ -183,7 +183,7 @@ void BuildStatus::BuildLoadDyndeps() { // it considers a portion of the graph to be out of date. Normally // this is done before the build starts, but our caller is about to // load a dyndep file during the build. Doing so may generate more - // exlanation lines (via fprintf directly to stderr), but in an + // explanation lines (via fprintf directly to stderr), but in an // interactive console the cursor is currently at the end of a status // line. Start a new line so that the first explanation does not // append to the status line. After the explanations are done a diff --git a/src/ninja.cc b/src/ninja.cc index 1429639..00e3a5c 100644 --- a/src/ninja.cc +++ b/src/ninja.cc @@ -91,7 +91,7 @@ struct NinjaMain : public BuildLogUser { /// Loaded state (rules, nodes). State state_; - /// Functions for accesssing the disk. + /// Functions for accessing the disk. RealDiskInterface disk_interface_; /// The build directory, used for storing the build log etc. @@ -1050,7 +1050,7 @@ bool DebugEnable(const string& name) { } } -/// Set a warning flag. Returns false if Ninja should exit instead of +/// Set a warning flag. Returns false if Ninja should exit instead of /// continuing. bool WarningEnable(const string& name, Options* options) { if (name == "list") { |