| commit | f7554e37355e2abc63ea180b0659372910b241e3 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Mon Aug 21 11:47:39 2023 -0700 |
| committer | Cole Faust <colefaust@google.com> | Mon Aug 21 11:47:39 2023 -0700 |
| tree | 0b2b469b2e2a271124d29652ec042edc8c348a31 | |
| parent | 7e730893f1ab473874ef5f701e44adae5dc257bd [diff] |
Ignore vndk compat symlinks in artifact path requirements A change is being made to properly track apex compat symlinks in the installation logic, which causes the artifact path requirements to start complaining about them. Exclude them from the artifact path requirements. Bug: 205632228 Test: m nothing Change-Id: I46150c3b7a4eaac16c2daa80fec2a5640e32b61b
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.