Lines Matching refs:Ninja
19 // 1. A Ninja binary
28 // used to generate the Ninja file that describes how to build the entire source
80 // 2. The bootstrap Ninja file template
89 // The bootstrap Ninja file template describes the build actions necessary to
91 // of placeholder Ninja variable values that get filled in by the bootstrap
92 // script to create a usable Ninja file. It can be created by running the
95 // create a bootstrap Ninja file template named 'build.ninja.in'.
99 // is responsible for filling in the bootstrap Ninja file template with some
102 // the template file to produce a usable build.ninja file.
107 // Ninja file. The states are referred to as the "bootstrap" state and the
109 // the build.ninja file with one that will perform the build actions for the
115 // Ninja file into the build directory as "build.ninja". It also performs a set
125 // @@BootstrapManifest@@ - The path to the source bootstrap Ninja file
128 // build state. In this state, running Ninja may perform the following build
133 // - Run minibp to generate .bootstrap/bootstrap.ninja.in
135 // - Run the primary builder to generate .bootstrap/main.ninja.in
136 // - Run the bootstrap script to "copy" .bootstrap/main.ninja.in to build.ninja
142 // - Copy .bootstrap/bootstrap.ninja.in to the source bootstrap Ninja location
143 // - Run the bootstrap script to "copy" the source bootstrap Ninja file to
144 // build.ninja
147 // Updating the Bootstrap Ninja File Template
149 // The main purpose of the bootstrap state is to generate the Ninja file for the
151 // Ninja file template at .bootstrap/bootstrap.ninja.in. When generating this
152 // file, minibp will compare the new bootstrap Ninja file contents with the
157 // This is done so that in the main state if the bootstrap Ninja file template
159 // however, that we can't have the main state generate the new bootstrap Ninja
162 // circular dependence), so if a new bootstrap Ninja file template were
167 // into the build process and that changes that require a new bootstrap Ninja
