| commit | 35f4ebc957fba01063218a21e98c61a60eacdd3f | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Thu Sep 27 15:31:11 2018 -0700 |
| committer | Tao Bao <tbao@google.com> | Thu Sep 27 18:06:59 2018 -0700 |
| tree | f8628ed585f17becd2356d3c7b05dde3299f674b | |
| parent | 2f12a5659315e3866aca0504172c0d1dfecee7c4 [diff] |
releasetools: Clean up the use of `partition_size`. Unless using dynamic partitions, `partition_size` should be a fixed value that equals to the partition size in BoardConfig. It should stay the same when building an image for that partition. Only the actual image size that's used to hold the filesystem could be adjusted. This CL cleans up the uses of `partition_size` and `image_size` to better reflect such logic. With dynamic partitions, the only thing that changes is the need to compute `partition_size` upfront. Once that's done, `partition_size` should remain unchanged. Test: `m dist` Test: `python -m unittest test_add_img_to_target_files` Test: `python -m unittest test_validate_target_files` Change-Id: Idedb3e018c95e8f63dc4d9c423be27f30ebb584f
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.