ndk: Hard-code the TARGET_RELEASE
Trunk stable builds require a TARGET_RELEASE to be set, but this variable doesn't have a real meaning for NDK builds. So we hard-core it here so individual build setups don't need to configure it. Bug: 309900087 Test: Treehugger Change-Id: I17a2e463db0b561aea57417bc2b469070ba2062d
This commit is contained in:
parent
c31b24977e
commit
a0b356f6b0
1 changed files with 2 additions and 0 deletions
|
@ -19,9 +19,11 @@ if [ -z "${OUT_DIR}" ]; then
|
|||
exit 1
|
||||
fi
|
||||
|
||||
# Note: NDK doesn't support flagging APIs, so we hardcode it to trunk_staging.
|
||||
# TODO: remove ALLOW_MISSING_DEPENDENCIES=true when all the riscv64
|
||||
# dependencies exist (currently blocked by http://b/273792258).
|
||||
# TODO: remove BUILD_BROKEN_DISABLE_BAZEL=1 when bazel supports riscv64 (http://b/262192655).
|
||||
TARGET_RELEASE=trunk_staging \
|
||||
ALLOW_MISSING_DEPENDENCIES=true \
|
||||
BUILD_BROKEN_DISABLE_BAZEL=1 \
|
||||
TARGET_PRODUCT=ndk build/soong/soong_ui.bash --make-mode --soong-only ${OUT_DIR}/soong/ndk.timestamp
|
||||
|
|
Loading…
Reference in a new issue