| commit | c8771bef56a46a6b0989af22ef8e759a9abff474 | [log] [tgz] |
|---|---|---|
| author | Alessandro Astone <ales.astone@gmail.com> | Sun May 10 11:27:57 2020 +0200 |
| committer | Alessandro Astone <ales.astone@gmail.com> | Tue Oct 27 13:39:59 2020 +0100 |
| tree | 5f3d7dab26a28cc43eebd2e59de49059d37bc2a0 | |
| parent | 2c892f87008dac1f991691a5ba15f3e2cccec332 [diff] |
build: allow refreshmod with external out directory Get a relative path to out by using $(get_build_var PRODUCT_OUT) instead of hardcoding it to out/target/product/$TARGET_DEVICE. That will correctly return the path to the out directory when setting an external OUT_DIR_COMMON_BASE. Change-Id: I8a990b710222bc72755c6b6b88fd0c9e80711e14
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.