commit | 14c6bd8c38632da95b82218c825ee68cd46a97dd | [log] [tgz] |
---|---|---|
author | Paul Duffin <paulduffin@google.com> | Thu Mar 17 18:10:24 2022 +0000 |
committer | Paul Duffin <paulduffin@google.com> | Mon Mar 21 12:53:14 2022 +0000 |
tree | 1b8026795d0e9d1e4d954c6db8716f1e4a6c6813 | |
parent | de60aeb525d7201c634b185f137d5e4e591603d8 [diff] |
Add --build-release option to mainline_modules_sdks.sh This change makes it easier to test the behavior of specific build releases. Bug: 218685706 Test: atest --host mainline_modules_sdks_test packages/modules/common/build/mainline_modules_sdks.sh packages/modules/common/build/mainline_modules_sdks.sh --build-release=S --build-release=latest pyformat -s 4 --force_quote_type double -i build/mainline_modules_sdks*.py /usr/bin/pylint --rcfile $ANDROID_BUILD_TOP/tools/repohooks/tools/pylintrc build/mainline_modules_sdks*.py Change-Id: Ib9ef2f35d27d10cd960c4b6225417d930cb10afc
This project includes mainline build and other utility code. Any library code intended for use by modules should go in frameworks/libs/modules-utils
instead.
This project uses a single source path for java code. All java code should go in the java
directory with subdirectories corresponding to the java package. Android.bp
files should go alongside the java source files, and should only include java source for a single java package to encourage good code hygiene.
Tests for java code should go in the javatests
directory and follow the same structure.