platform_build_soong/bootstrap.bash

#!/bin/bash

echo '==== ERROR: bootstrap.bash & ./soong are obsolete ====' >&2
echo 'Use `m --skip-make` with a standalone OUT_DIR instead.' >&2
echo 'Without envsetup.sh, use:' >&2
echo '  build/soong/soong_ui.bash --make-mode --skip-make' >&2
echo '======================================================' >&2
exit 1
Initial soong This creates the infrastructure that will be used to bootstrap the soong primary builder through blueprint and ninja. Change-Id: Iebed8f369e4db41b207d0b2a48a7a54a4dd7d45d 2015-01-27 01:30:13 +01:00			`#!/bin/bash`

Obsolete bootstrap.bash and ./soong wrappers 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 2017-08-05 01:04:04 +02:00			`echo '==== ERROR: bootstrap.bash & ./soong are obsolete ====' >&2`
			echo 'Use `m --skip-make` with a standalone OUT_DIR instead.' >&2
			`echo 'Without envsetup.sh, use:' >&2`
			`echo ' build/soong/soong_ui.bash --make-mode --skip-make' >&2`
			`echo '======================================================' >&2`
			`exit 1`
Use SRCDIR as a working directory 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 2015-07-14 09:39:06 +02:00