e12c862013
Path conflicts could happen when following conditions are met. 1) a java library named "foo" is not installable. 2) a java library named "bar" is installable, and its stem is set to "foo". Then the notice file for 1) becomes foo.jar.txt following its LOCAL_MODULE, while the notice file for 2) becomes foo.jar.txt following its stem. Since the file for 1) is a synthetic one, the actual name isn't important. Avoid the conflict by appending a suffix (_non_installable, but could be anything) to the file name for 1). There still is a chance for the conflict; if the stem for "bar" is set to "foo_non_installable". But practically, the chances are very low. Bug: 139391334 Bug: 143700028 Test: m Change-Id: Id50b30774bbf65cc180baf963a95ea56fe6eb74f
Android Make Build System
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.