| commit | 5e55e4577c686b990f47eef57e8031ee9f018b3a | [log] [tgz] |
|---|---|---|
| author | Marybeth Fair <marybethfair@google.com> | Thu Oct 03 18:08:49 2024 +0000 |
| committer | Marybeth Fair <marybethfair@google.com> | Thu Oct 03 18:08:49 2024 +0000 |
| tree | 1cc53324168af895a33bfc60d7aac216f544343d | |
| parent | 20ed2074e836a0de9051beee4996e534cda5d8a9 [diff] |
Move test files from tests/ to data/v1/. This way when I re-submit aosp/3287421, I can run tests on v1 and v2 storage files to enforce that we can read both. Test: atest (this change just moves the files) Change-Id: I8618e0ed56a91a0ad2cbb0725c7a5c0ec2a8b513
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.