| commit | b7f55afdc683f7c52f7ffd09488ed74bb454e746 | [log] [tgz] |
|---|---|---|
| author | Chirayu Desai <chirayudesai1@gmail.com> | Thu Sep 27 18:11:25 2012 +0530 |
| committer | Jackeagle <jackeagle102@gmail.com> | Wed Aug 08 12:27:43 2018 -0400 |
| tree | 72bc23c2ee35191b1ef5a3fc6ecdaac5e9024a49 | |
| parent | 613a4c38172c5a50a77c2b3bc58a117359096014 [diff] |
envsetup: set OUT_DIR to an absolute path always OUT_DIR was set to $(TOPDIR)out previously, but $(TOPDIR) was null, so it was a relative path. This broke releasetools, inline kernel building, etc since they require absolute paths. Fix it so that it is set to $(shell readlink -f .)/out if $(TOPDIR) is null. Also remove hacks which checked if (OUT_DIR) was out and changed it to $(ANDROID_BUILD_TOP)/out to workaround the aforementioned problem. Change-Id: I459a3b1325a1bbea0565cd73f6acf160d4ed9b39 build: work around missing readlink -f on Mac Change-Id: I5d56366cf33a2b02f1886c87815d00cff279779d envsetup: use $(CURDIR) for getting current directory Change-Id: I5f00faf64ec31d86dd2e48ec038748ce8499380b
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.