Remove UNBUNDLED_BUILD_SDKS_FROM_SOURCE=true setting.

It needs to be controlled by build instead:

- Prebuilt SDKs should be used for unbundled Mainline module builds, and
  is necessary on thin module branches to avoid dependencies on
  frameworks/base (e.g. framework-doc-stubs used by lint-check).

- Source SDKs are needed on master which can otherwise get problems
  with out of date prebuilts (see e.g. b/140162931).

Test: env TARGET_BUILD_APPS=com.android.art \
        packages/modules/common/build/build_unbundled_mainline_module.sh \
        --product module_arm --dist_dir out/dist
  using the thin master-art manifest
Bug: 202192894
Change-Id: Ia73ccc6e694caec64c7dd0d86246a258e2bb9239
1 file changed
tree: 696b53ec1cb5e6aad7bfbc6a935ef43c4391bfb2
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  9. MODULES_OWNERS
  10. OWNERS
  11. PREBUILTS_MODULE_OWNERS
  12. PREUPLOAD.cfg
  13. README.md
README.md

packages/modules/common

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.

java code

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.