aconfig: fix build issue

When trying to advance the CHECK_API flag, the build failed (so the CL
couldn't submit) with an error that Build is not found. This happened
because for the Flags template, I only gated the import statement on
library_exported, not the SDK check itself. Fixed this and added a test
to make sure SDK check is not added to Flags in internal codegen, even
when the flag is on the finalized list.

Also remove a build import from FeatureFlagsImpl where it was unused.

Change-Id: I6474a67665169c9da1fc6325017eeaa9d5847048
Test: atest aconfig.test
3 files changed
tree: 81cb27706c59695b5ed29c0762b7acd12d048dc4
  1. backported_fixes/
  2. ci/
  3. common/
  4. core/
  5. packaging/
  6. target/
  7. teams/
  8. tests/
  9. tools/
  10. .gitignore
  11. Android.bp
  12. banchanHelp.sh
  13. buildspec.mk.default
  14. Changes.md
  15. CleanSpec.mk
  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.