platform_build_blueprint/tests/bootstrap.bash

#!/bin/bash

export BOOTSTRAP="${BASH_SOURCE[0]}"
export SRCDIR=".."
export BOOTSTRAP_MANIFEST="src.build.ninja.in"
export WRAPPER="../blueprint.bash"

../bootstrap.bash "$@"
Add test suite for bootstrapping This only checks to make sure that for a given updated file, the bootstrap stage is properly run. It doesn't actually check to make sure that anything was rebuilt. Change-Id: I9cb6ff1d483264da30e43d5580361d93b148f42c 2015-07-23 02:05:51 +02:00			`#!/bin/bash`

			`export BOOTSTRAP="${BASH_SOURCE[0]}"`
			`export SRCDIR=".."`
			`export BOOTSTRAP_MANIFEST="src.build.ninja.in"`
Simplify bootstrap tl;dr: Read if you don't use the wrapper or use SKIP_NINJA Previously, we were relying on the ninja behavior of restarting the build when the build.ninja file was updated to switch between different bootstrap stages. But that means that every step that could produce a build.ninja must pass in order to switch to a different stage. That wasn't a big problem when we had a two stage build -- there was very little that could fail in the second stage before we chose to go back to the first stage. But when we had a three stage build, it was possible to get into a state (usually during development) where you were in the second stage, but the build was failing because the first stage needed to be run. This was fixed in d79f1af7423e0ef7a13573efdae5100a57fabc82 by adding a wrapper that always started building at the first stage. But this kept all of the complexity of using ninja restarts without any of the benefits, so this change removes that complexity and just runs each stage sequentially in the wrapper. So the wrapper is now required. Since we're no longer going through choosestage, we can also skip the template parsing for the later stages that don't need to be templated -- this can save a couple of seconds for large files. In addition to all of the above, this also lets Soong reduce the number of times the main ninja file is loaded. We had been running the wrapper once (3 stages), then running ninja again after combining the Soong-generated build.ninja with the Kati-generated build.ninja. This change lets us removing the intermediate parsing of Soong's build.ninja, so that we only execute ninja 3 times per build. It also lets us have dependencies on pools or rules from Kati in the primary builder, since we're never executing the main build.ninja without the Kati build.ninja. The wrapper has a new option, NINJA to provide the path to ninja. This used to be hardcoded to `ninja`, and will still default to that. But we'll be running the first two bootstrap stages with $NINJA even if SKIP_NINJA is set. The wrapper passes "-w dupbuild=err" to ninja now -- this really should always be turned on if you care about reliable builds. Change-Id: I6f656b74eb3d064b8b9e69d1d6dac1129d72b747 2016-08-13 21:42:11 +02:00			`export WRAPPER="../blueprint.bash"`
Add test suite for bootstrapping This only checks to make sure that for a given updated file, the bootstrap stage is properly run. It doesn't actually check to make sure that anything was rebuilt. Change-Id: I9cb6ff1d483264da30e43d5580361d93b148f42c 2015-07-23 02:05:51 +02:00
			`../bootstrap.bash "$@"`