bpmodify isn't safe for multi processes env because it doesn't use any lock mechanism even with -w option(in-place change) So, added -j1 option as a temp solution. Bug: 190577319 Bug: 229413853 Test: run aidl-freeze-api with -j1 Change-Id: I7fabfa1224ea0bb8d71538f4c8012255df28a3e8
32 lines
838 B
Bash
Executable File
32 lines
838 B
Bash
Executable File
#!/bin/bash
|
|
|
|
set -e
|
|
|
|
source "$(dirname "$0")"/envsetup.sh
|
|
|
|
# default target to modify tree and build SDK
|
|
lunch aosp_arm64-userdebug
|
|
|
|
set -x
|
|
|
|
# This script is WIP and only finalizes part of the Android branch for release.
|
|
# The full process can be found at (INTERNAL) go/android-sdk-finalization.
|
|
|
|
# VNDK snapshot (TODO)
|
|
# SDK snapshots (TODO)
|
|
# Update references in the codebase to new API version (TODO)
|
|
# ...
|
|
|
|
# Adding -j1 option because of file(Android.bp) race condition.
|
|
AIDL_TRANSITIVE_FREEZE=true m aidl-freeze-api -j1
|
|
|
|
m check-vndk-list || update-vndk-list.sh # for new versions of AIDL interfaces
|
|
|
|
# for now, we simulate the release state for AIDL, but in the future, we would want
|
|
# to actually turn the branch into the REL state and test with that
|
|
AIDL_FROZEN_REL=true m # test build
|
|
|
|
# Build SDK (TODO)
|
|
# lunch sdk...
|
|
# m ...
|