dd3a27394f
This architecture only existed for unbundled use, but even the NDK is removing support in their r17 release, so just remove support for it. Test: build/soong/build_test.bash -only-config Test: check buildserver configs, I don't see anything still using armv5 Change-Id: Ic183b510c9ada94438bd4cc2b9362fa438a29ced
24 lines
806 B
Bash
Executable File
24 lines
806 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# locate some directories
|
|
cd "$(dirname $0)"
|
|
SCRIPT_DIR="${PWD}"
|
|
cd ../..
|
|
TOP="${PWD}"
|
|
|
|
message='usage: tapas [<App1> <App2> ...] [arm|x86|mips|arm64|x86_64|mips64] [eng|userdebug|user]
|
|
|
|
tapas selects individual apps to be built by the Android build system. Unlike
|
|
"lunch", "tapas" does not request the building of images for a device.
|
|
Additionally, an app built with "tapas" will have its dex file inside its apk,
|
|
which should cause it to be suitable for installing on any api-compatible
|
|
device. In other words, "tapas" configures the build of unbundled apps.
|
|
|
|
The names <App1> <App2> ... should match LOCAL_PACKAGE_NAME as defined in an
|
|
Android.mk
|
|
|
|
The usage of the other arguments matches that of the rest of the platform
|
|
build system and can be found by running `m help`'
|
|
|
|
echo "$message"
|