| commit | c777eaa779fd171abb80640656e2164b15dbc63b | [log] [tgz] |
|---|---|---|
| author | Mark Salyzyn <salyzyn@google.com> | Tue Jan 08 10:08:04 2019 -0800 |
| committer | Mark Salyzyn <salyzyn@google.com> | Thu Jan 10 14:49:12 2019 -0800 |
| tree | 66dee9ee272419449319b1e1d8e9ad3427de351c | |
| parent | 1b8939b94657e5f70ef70030e7c68913d35f10cb [diff] |
build_image: hard code set inode size to 256 inode-size will jump around based on filesystem size, however readonly Android system partitions have a specific pattern of xattr associated with sepolicy and 256 is the most efficient at absorbing the content. Test: manual Bug: 122328872 Change-Id: I06dd6a503067ab6477293b386d56a89dd86b0e83
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.