1*9e94795aSAndroid Build Coastguard Worker#!/bin/bash 2*9e94795aSAndroid Build Coastguard Worker 3*9e94795aSAndroid Build Coastguard Worker# locate some directories 4*9e94795aSAndroid Build Coastguard Workercd "$(dirname $0)" 5*9e94795aSAndroid Build Coastguard WorkerSCRIPT_DIR="${PWD}" 6*9e94795aSAndroid Build Coastguard Workercd ../.. 7*9e94795aSAndroid Build Coastguard WorkerTOP="${PWD}" 8*9e94795aSAndroid Build Coastguard Worker 9*9e94795aSAndroid Build Coastguard Workermessage='usage: tapas [<App1> <App2> ...] [arm|x86|arm64|x86_64] [eng|userdebug|user] [devkeys] 10*9e94795aSAndroid Build Coastguard Worker 11*9e94795aSAndroid Build Coastguard Workertapas selects individual apps to be built by the Android build system. Unlike 12*9e94795aSAndroid Build Coastguard Worker"lunch", "tapas" does not request the building of images for a device. 13*9e94795aSAndroid Build Coastguard WorkerAdditionally, an app built with "tapas" will have its dex file inside its apk, 14*9e94795aSAndroid Build Coastguard Workerwhich should cause it to be suitable for installing on any api-compatible 15*9e94795aSAndroid Build Coastguard Workerdevice. In other words, "tapas" configures the build of unbundled apps. 16*9e94795aSAndroid Build Coastguard Worker 17*9e94795aSAndroid Build Coastguard WorkerThe names <App1> <App2> ... should match LOCAL_PACKAGE_NAME as defined in an 18*9e94795aSAndroid Build Coastguard WorkerAndroid.mk 19*9e94795aSAndroid Build Coastguard Worker 20*9e94795aSAndroid Build Coastguard WorkerThe usage of the other arguments matches that of the rest of the platform 21*9e94795aSAndroid Build Coastguard Workerbuild system and can be found by running `m help`' 22*9e94795aSAndroid Build Coastguard Worker 23*9e94795aSAndroid Build Coastguard Workerecho "$message" 24