| commit | 37abbfca2a83cd4fa050f4aeeab092f9f08222f2 | [log] [tgz] |
|---|---|---|
| author | satayev <satayev@google.com> | Fri Jul 09 16:16:44 2021 +0100 |
| committer | satayev <satayev@google.com> | Tue Jul 13 11:46:53 2021 +0100 |
| tree | 1f776b4294c0f32a92568c646e8a7918270b1d18 | |
| parent | 6928345c14fb30d4a7e4c600f270372fa779b4f9 [diff] |
Introduce build script for mainline modules. The build_unbundled_mainline_module.sh builds for a given product a list of mainline modules. In AOSP it defaults to building all AOSP modules. Individual mainline_modules_<arch>.sh scripts are meant to build per product targets for individual invocation on build servers. For example, on AOSP presubmit we would want to build mainline_modules_x86_64. The build script is meant to be re-used from internal version of the scripts that would pass com.google variant of the modules. Note that the script excludes bundles and stubs, since those are not need to be built in AOSP. There will be a separate script internally for those. Bug: 191965323 Test: call the scripts, inspect out/dist/ directory. Change-Id: I13dc723dd26fd8a2a43f46c3186513bcf5519fb5
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.