| commit | 9c59c314991a960a86183bd3034aad24ba37952a | [log] [tgz] |
|---|---|---|
| author | Mårten Kongstad <amhk@google.com> | Tue May 30 11:15:02 2023 +0200 |
| committer | Mårten Kongstad <amhk@google.com> | Fri Jun 09 09:59:21 2023 +0200 |
| tree | c1c40a9262112ca4e035b96b65b47c2252ffae8b | |
| parent | a85c8a863a50e18a37aaab677a719fd604de3a4a [diff] |
aconfig: add Java integration tests Add integration tests for Java. This test setup verifies that - the build system calls aconfig to generate a Java library - the Java test compiles against the auto-generated library - the auto-generated code returns expected values Similar integration tests for C++ and Rust will be added in follow-up CLs. Note: the build does not currently support specifying that tests/*.values should be applied, so the test flags will all be assigned the defaults. A later CL will fix this. Bug: b/283911467 Test: atest aconfig.test aconfig.test.java Change-Id: Ia365e209261f4935a23e2dac9ef0ab5b60f76e52
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.