Add whitelist for mcts modules

Some MCTS modules should not be removed from CTS because they are
dependencies of both MCTS and CTS.

Add a whitelist as a short term solution.

Test: m cts EXCLUDE_MCTS=true
Bug: 349372705
BYPASS_INCLUSIVE_LANGUAGE_REASON=for mcts only
(cherry picked from https://android-review.googlesource.com/q/commit:9005bb61f7e955536ac786ccf38f41aae8f0665c)
Merged-In: I26ada6da95a8b3547de9e54781b744facb121b05
Change-Id: I26ada6da95a8b3547de9e54781b744facb121b05
1 file changed
tree: 6cb6748d616e9d5343780c83e6cc71c19a5f9042
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. Android.bp
  11. banchanHelp.sh
  12. buildspec.mk.default
  13. Changes.md
  14. CleanSpec.mk
  15. cogsetup.sh
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. Usage.txt
README.md

Android Make Build System

This is the Makefile-based portion of the Android Build System.

For documentation on how to run a build, see Usage.txt

For a list of behavioral changes useful for Android.mk writers see Changes.md

For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.

This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.