| Martin Stjernholm | f692c75 | 2021-04-12 00:01:10 +0100 | [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: banchan <module> ... [arm|x86|arm64|x86_64] [eng|userdebug|user] |
| 10 | |
| 11 | banchan selects individual APEX modules to be built by the Android build system. |
| 12 | Like "tapas", "banchan" does not request the building of images for a device but |
| 13 | instead configures it for an unbundled build of the given modules, suitable for |
| 14 | installing on any api-compatible device. |
| 15 | |
| 16 | The difference from "tapas" is that "banchan" sets the appropriate products etc |
| 17 | for building APEX modules rather than apps (APKs). |
| 18 | |
| 19 | The module names should match apex{} modules in Android.bp files, typically |
| 20 | starting with "com.android.". |
| 21 | |
| 22 | The usage of the other arguments matches that of the rest of the platform |
| 23 | build system and can be found by running `m help`' |
| 24 | |
| 25 | echo "$message" |