commit | ec5e3b8d28df4b683633095c3f3bdc8551e59b0e | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Wed Mar 15 16:33:46 2023 -0400 |
committer | Dan Willemsen <dwillemsen@google.com> | Wed Mar 15 20:06:59 2023 -0400 |
tree | a8aeea8287b37107b6a588fd31514344aa20fb9a | |
parent | 4fac9d776c54e8e0b66933cea856f7db0f743bcf [diff] |
Rename rbcrun/cmd to make `go install` work properly The standard go tooling assumes that a package's binary name should be the name of the containing folder. Before this change, `go install` or `go build` (without `-o`) names this binary `cmd`. Also run `go mod tidy` while we're here, so the tooling doesn't try to download github.com/nbutton23/zxcvbn-go, which we don't have a local copy of. Test: treehugger Change-Id: I8f79724e928720caf961cdad128655ef31c3e9b2
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.