| commit | 0ac530459825bc31a71acbd901575effbd88d681 | [log] [tgz] |
|---|---|---|
| author | Mårten Kongstad <amhk@google.com> | Thu Sep 28 10:16:29 2023 +0200 |
| committer | Mårten Kongstad <amhk@google.com> | Fri Oct 13 09:49:40 2023 +0200 |
| tree | 384b959ca3900bb52ac7ceab5ca6f1cc03f2ecda | |
| parent | 9ef1caabedc04720a3e2a03ee28a6e194d39d4b6 [diff] |
Do not generate aconfig_flags.textproto The /<partition>/etc/aconfig_flags.textproto files are no longer needed (all clients have migrated to use /<partition>/etc/aconfig_flags.pb). Stop generating them. Also update how an empty file is generated in case there are no flags for a given partition. Previously echo "" > file was used, which resulted in a file containing a newline, which caused `printflags` to error out. Change the command to echo -n > file to create an empty file. Bug: 302452801 Bug: 304278614 Test: m nothing Change-Id: I2f7d23df4e888046651b4155b75c5006d0b5e1d7
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.