| commit | 76def243ecbb60a781f0c3da026444b897b34427 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Nov 21 09:25:31 2017 -0800 |
| committer | Tao Bao <tbao@google.com> | Thu Jul 19 10:39:05 2018 -0700 |
| tree | 278a57c083505d2955d10c2fcbb70b6b2e1ee3df | |
| parent | 401fada3f59c6fc8de8429765b1fba373d6d939a [diff] |
releasetools: Make scripts pylint clean. Clean up the following scripts. blockimgdiff.py common.py edify_generator.py img_from_target_files.py ota_from_target_files.py Seems we don't have a way to force pylint-ing the scripts using per-directory pylintrc files (and we don't have pylint tool in AOSP repo), per https://android.googlesource.com/platform/tools/repohooks/#todo_limitations. Test: `m dist` Test: pylint --rcfile=pylintrc <script.py> Change-Id: Ia6fd1ddc86f4d84c68e500f225d4a89d0fea8ec7
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.