e0879fc3ae
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
48 lines
1.6 KiB
Bash
Executable file
48 lines
1.6 KiB
Bash
Executable file
#!/bin/bash
|
|
|
|
set -e
|
|
|
|
# Switch to the build directory
|
|
cd $(dirname "${BASH_SOURCE[0]}")
|
|
|
|
if [ -z "$NO_DEPRECATION_WARNING" ]; then
|
|
echo '== WARNING: bootstrap.bash & ./soong are deprecated ==' >&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
|
|
fi
|
|
|
|
# The source directory path and operating system will get written to
|
|
# .soong.bootstrap by the bootstrap script.
|
|
|
|
BOOTSTRAP=".soong.bootstrap"
|
|
if [ ! -f "${BOOTSTRAP}" ]; then
|
|
echo "Error: soong script must be located in a directory created by bootstrap.bash"
|
|
exit 1
|
|
fi
|
|
|
|
source "${BOOTSTRAP}"
|
|
|
|
# Now switch to the source directory so that all the relative paths from
|
|
# $BOOTSTRAP are correct
|
|
cd ${SRCDIR_FROM_BUILDDIR}
|
|
|
|
# Ninja can't depend on environment variables, so do a manual comparison
|
|
# of the relevant environment variables from the last build using the
|
|
# soong_env tool and trigger a build manifest regeneration if necessary
|
|
ENVFILE="${BUILDDIR}/.soong.environment"
|
|
ENVTOOL="${BUILDDIR}/.bootstrap/bin/soong_env"
|
|
if [ -f "${ENVFILE}" ]; then
|
|
if [ -x "${ENVTOOL}" ]; then
|
|
if ! "${ENVTOOL}" "${ENVFILE}"; then
|
|
echo "forcing build manifest regeneration"
|
|
rm -f "${ENVFILE}"
|
|
fi
|
|
else
|
|
echo "Missing soong_env tool, forcing build manifest regeneration"
|
|
rm -f "${ENVFILE}"
|
|
fi
|
|
fi
|
|
|
|
BUILDDIR="${BUILDDIR}" NINJA="prebuilts/build-tools/${PREBUILTOS}/bin/ninja" build/blueprint/blueprint.bash "$@"
|