| commit | fd6406c066e5de2c6f0976fe120d76aafdb0c86e | [log] [tgz] |
|---|---|---|
| author | Nelson Li <nelsonli@google.com> | Wed May 29 06:31:35 2024 +0000 |
| committer | Nelson Li <nelsonli@google.com> | Tue Jun 04 03:34:27 2024 +0000 |
| tree | a11a4304367d784a6068971565b3f09efcafaf4f | |
| parent | 08445aada2d7a2b93331aaecdfa57f104bdd8c1d [diff] |
Convert appcompat.sh to a Python binary
Previously, to use `appcompat.sh`, we hardcoded absolute paths for many
dependencies in the `build/core/definitions.mk` file, and the same was
done in `art/tools/veridex/Android.mk`.
This change converts `appcompat.sh` to `appcompat.py` and packages the
necessary files into a `Python binary`. This not only resolves the
issue of hardcoding absolute dependency paths but also allows users to
use the tool directly without having to specify dependency paths,
making it more convenient.
Bug: 343105310
Test: 1. m appcompat
2. m CarrierConfig (any module with appcompat)
3. appcompat --dex-file=<apk path>
Change-Id: I6215f42241f58ba7fc6f4ae5846c4b71d9c1be4f
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.