| Jeff Gaston | 9fb05d8 | 2017-08-21 18:27:00 -0700 | [diff] [blame] | 1 | #!/bin/bash |
| 2 | |
| 3 | # locate some directories |
| 4 | cd "$(dirname $0)" |
| 5 | SCRIPT_DIR="${PWD}" |
| 6 | cd ../.. |
| 7 | TOP="${PWD}" |
| 8 | |
| 9 | message='usage: tapas [<App1> <App2> ...] [arm|x86|mips|armv5|arm64|x86_64|mips64] [eng|userdebug|user] |
| 10 | |
| 11 | tapas selects individual apps to be built by the Android build system. Unlike |
| 12 | "lunch", "tapas" does not request the building of images for a device. |
| 13 | Additionally, an app built with "tapas" will have its dex file inside its apk, |
| 14 | which should cause it to be suitable for installing on any api-compatible |
| 15 | device. In other words, "tapas" configures the build of unbundled apps. |
| 16 | |
| 17 | The names <App1> <App2> ... should match LOCAL_PACKAGE_NAME as defined in an |
| 18 | Android.mk |
| 19 | |
| 20 | The usage of the other arguments matches that of the rest of the platform |
| 21 | build system and can be found by running `m help`' |
| 22 | |
| 23 | echo "$message" |