Soong API: Implement Proto definition and DAO for Soong API
This CL establishes the core data layer for the Soong API.
It introduces the gRPC interface definition (.proto) and the Data Access
Object (DAO) responsible for querying the SQLite database generated by
the soong_api_db_loader.
Key changes:
1. Proto Definition (soong_api.proto):
- Defines the `Module` message and `SoongApiService`.
- APIs return `stream Module` to support scenarios where a single
query matches multiple distinct modules (e.g., name collisions
across namespaces or multiple modules installing the same file).
2. DAO Implementation (SoongApiDao.java):
- Implements query logic using SQLite JSON functions.
- Intelligent Aggregation: Rows with the same `Name` and `Path` are
treated as variants (e.g., x86/arm) and merged into a single
Module object (combining `install_files`).
- Distinct Separation: Rows with the same `Name` but different
`Path`s (e.g., source vs. prebuilt) are treated as distinct
modules and returned separately.
3. Hermetic Testing:
- Added `SoongApiDaoTest.java` using an in-memory SQLite database
(`jdbc:sqlite::memory:`). This ensures tests are fast, reliable,
and do not depend on external artifacts.
4. Rename metadata_db_loader:
- Rename `metadata_db_loader` to `soong_api_db_loader`
Bug: 467242563
Test: m soong_api_tests
Test: atest soong_api_tests --host
Change-Id: If7b924cea05b9693786fafd71bca2e5fe621d1d4
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.