87b17d1ff4
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
44 lines
1.3 KiB
Bash
Executable file
44 lines
1.3 KiB
Bash
Executable file
#!/bin/bash
|
|
|
|
set -e
|
|
|
|
# Switch to the build directory
|
|
cd $(dirname "${BASH_SOURCE[0]}")
|
|
|
|
# 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}
|
|
|
|
# Let Blueprint know that the Ninja we're using performs multiple passes that
|
|
# can regenerate the build manifest.
|
|
export BLUEPRINT_NINJA_HAS_MULTIPASS=1
|
|
|
|
# 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
|
|
|
|
"prebuilts/ninja/${PREBUILTOS}/ninja" -f "${BUILDDIR}/build.ninja" "$@"
|