| commit | a1b215cf2a52945747a1db3a6f5848b73de2eb30 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Thu Jul 21 08:08:32 2022 -0700 |
| committer | Cole Faust <colefaust@google.com> | Thu Jul 21 08:08:32 2022 -0700 |
| tree | d6f974c59f2dee628e57cc4089f0e5de2f09a365 | |
| parent | e8b97242001a53b1b05e43ea35f0d6faa6d89dda [diff] |
Remove leading whitespace from dump-variables-rbc results For some reason, some internal products were failing the quick rbc ci check purely because of indentation differences in the variable dump file. That file has a lot of wonky leading indentation due to the foreaches and line breaks in the function implementation that I couldn't figure out how to remove. Instead, use a sed command to remove leading spaces after writing the file. Bug: 239453560 Test: build/bazel/ci/rbc_dashboard.py --quick on a new internal-only product Change-Id: I4b34d8e0b5dbbfcbb9ed35345d216ca11a5a1198
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.