| commit | 00cf045c85263309324ebf74807db5ccc8748fd3 | [log] [tgz] |
|---|---|---|
| author | Mårten Kongstad <amhk@google.com> | Fri May 26 16:48:01 2023 +0200 |
| committer | Mårten Kongstad <amhk@google.com> | Fri May 26 17:09:10 2023 +0200 |
| tree | 54d5322ba6a6e9257cc44cb7ea3203591057c656 | |
| parent | aa977fb083c7259ff696ecd2f941854cab995e07 [diff] |
aconfig: restrict valid namespace and flag names The namespace and flag names will be used as identifiers in the auto-generated code. Place restrictions on what constitutes a valid name. Valid identifiers are those that match /[a-z][a-z0-9_]/. aconfig explicitly does not implement any automatic translation to make names valid identifiers: this sidesteps potential conflicts such as "foo.bar" and "foo_bar" mapping to the same name if dots were translated to underscores. Bug: b/284252015 Test: atest aconfig.test Change-Id: I38d005a74311e5829e540063404d1565071e6e96
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.