Remove empty rules for hostname and build_number

These files are created by soong_ui and not by the primary ninja
execution. Empty rules are currently added to the ninja file to prevent
"Test for dangling rules" from flagging this as an error.

In preparation for turning on "Test for dangling rules" check in `m
--soong-only`, these files will be added to an allowlist in soong_ui's
test_build.go. Therefore, we can clean these up now.

Test: m checkbuild --soong-only
Test: presubmits
Bug: 394096939
Change-Id: I6fd3717fa52ff2461965c3d401860edfbc0cf57d
1 file changed
tree: d5a7ec1bbb42f0111e2422fd4fd5549b9ad2676e
  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.