build_soong/bootstrap.bash, branch android-10.0.0_r6

Add license headers to all go and shell files

2017-11-17T23:05:26+00:00

Test: none
Change-Id: I75c443e05f2b1e17fcb6823182717d2e6f5df7c4

Obsolete bootstrap.bash and ./soong wrappers

2017-08-18T17:13:22+00:00

We can call directly into the blueprint bootstrap.bash using values that
soong_ui has already calculated.

Instead of calling into blueprint.bash, build minibp with microfactory,
and directly run ninja. This allows us to get individual tracing data
from each component.

Test: m -j blueprint_tools
Test: m clean; m -j blueprint_tools
Change-Id: I2239943c9a8a3ad6e1a40fa0dc914421f4b5202c

Add --skip-make to replace Soong's blueprint wrapper with soong_ui

2017-08-09T05:49:28+00:00

This way we only have one way to start a build, which always has logging
/ tracing / etc, even if we don't need Kati.

There's two ways to use this:

As a direct replacement for mkdir out; cd out; ../bootstrap.bash;
./soong -- as long as --skip-make is always passed, we'll never run
Kati, and Soong will run outside of it's "make" mode. This preserves
most of the speed, and allows full user control over the Soong
configuration.

A (experimental, dangerous) way to temporarily bypass the product
variable and kati steps of a build. As long as a user is sure that
nothing has changed from the last build, and they know exactly which
Ninja targets they want to build (which may not be the same as the
arguments normally passed to 'm'), this can lead to shorter build
startup times.

Test: rm -rf out; m --skip-make libc
Test: rm -rf out; m libc; m --skip-make libc
Test: rm -rf out; mkdir out; cd out; ../bootstrap.bash; ./soong libc
Test: build/soong/scripts/build-ndk-prebuilts.sh
Change-Id: Ic0f91167b5779dba3f248a379fbaac67a75a946e

Switch to blueprint's microfactory

2017-07-24T22:29:14+00:00

Bug: 63720725
Test: m -j nothing
Test: mkdir o; ../bootstrap.bash; ./soong
Change-Id: Id1f8312678f36afd08b49f8511fec3e6e5ba8de2

Move shell and python scripts to scripts/ directory

2016-04-29T20:59:56+00:00

Change-Id: Icdff44a54d14ddfc2266d99cf0578a8105716918

Improve BUILDDIR handling with symlinks

2016-03-23T02:53:36+00:00

If BUILDDIR is a local symlink to another directory in the same parent
directory (out -> out.angler), then using out and .. as relative paths
to get back and forth work.

But if BUILDDIR is a symlink to another directory altogether (out ->
/mnt/sdd/out.master), then we shouldn't be relying on relative paths (so
that the source directory can still be moved).

Change-Id: I946c8116090410ab2b935eafba9b6e96f5f2f1dd

Use SRCDIR as a working directory

2015-09-18T06:42:25+00:00

The existing behavior of using the build directory as the working
directory is useful if you want to move/copy the output directory around
and SRCDIR still refers the the source. But, it's more useful to have
the source directory be the working directory. Tools like cpp(__FILE__)
and other debug prints embed relative paths from the working directory.
We also have tools that expect the working directory to be $TOP.

Change-Id: Ia0f1d3c6b7df72d61cf5628efa2baa98bd19775b

Build and run tests during bootstrap

2015-06-26T18:51:03+00:00

Change-Id: If40489d74136af4d15d4ff26210a50975a462497

Fix bootstrap.bash -r with Android.bp

2015-06-11T01:07:39+00:00

Change-Id: I8182e57105b1c17254e082f6b72d2504befb7870

Fix soong scripts to support directories with spaces

2015-04-10T22:50:37+00:00

Using a path with a space to execute soong is unlikely, but it
might as well work.  Quote all the paths in the soong scripts.

Soong and blueprint will still both fail if the relative path between
the soong script and the source directory has a space in it, but this
is even more unlikely.

Change-Id: I8986f10115209d69b09b82ffea26e4b10d29c197