| commit | 9262b6fead81cec97cc8d2efa482b5a91ad6c025 | [log] [tgz] |
|---|---|---|
| author | Dan Albert <danalbert@google.com> | Thu Jan 11 13:24:32 2018 -0800 |
| committer | Dan Albert <danalbert@google.com> | Thu Jan 11 13:24:32 2018 -0800 |
| tree | 1a45ffe2b64a865de97ac70adb51e844f0323879 | |
| parent | 08e715967222e155d73e49f07fe83f3b57913b20 [diff] |
Disable availability macros in libc++ on Darwin. libc++'s headers are annotated with availability macros that indicate which version of Mac OS was the first to ship with a libc++ feature available in its *system's* libc++.dylib. We do not use the system's library, but rather ship our own. As such, these availability attributes are meaningless for us but cause build breaks when we try to use code that would not be available in the system's dylib. Test: removed the darwin check and checked showcommands on linux Bug: None Change-Id: I5f69f337baa29fcdf84b5e2fe46bf4f85904d1cd
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.