commit | d42a053aa8ecaba6cd920d2d8ef281f8dc3d4d25 | [log] [tgz] |
---|---|---|
author | Luca Farsi <lucafarsi@google.com> | Wed Jan 17 15:24:59 2024 -0800 |
committer | Luca Farsi <lucafarsi@google.com> | Wed Jan 17 15:25:18 2024 -0800 |
tree | fc51f97708450d43caf79816c7d7e5e02f187cfd | |
parent | 7cd5b313f6f40911e31d62e9cdc0fe52af1bb9dd [diff] |
Make build script executable via python Add shebang line to make build test suties script callable via command line without needing python. Test: ./build/make/ci/build_test_suites --target_product aosp_x86_64 --target_release trunk_staging --with_dexpreopt_boot_img_and_system_server_only --dist_dir <dist_dir> --change_info <change_info_file> <extra_targets> Change-Id: I94422993e864e021b036a4eb1673b463ad4b86d4
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.