mk_payload is a host tool
Because virtualization service makes a microdroid payload disk image,
we don't need mk_payload any longer. But having a host tool might be
helpful for other uses. For example, ARCVM can use this tool for its own
use.
example_config.json:
{
"apexes": [
{ "name": "com.android.foo",
"path": "path/to/com.android.foo.apex" },
...
}
Bug: 189242583
Test: mk_payload example_config.json payload.img
Change-Id: I8d04701ed27782ddebb28449ba75e089309ec4c8
diff --git a/microdroid/payload/Android.bp b/microdroid/payload/Android.bp
index c7bc415..72711c3 100644
--- a/microdroid/payload/Android.bp
+++ b/microdroid/payload/Android.bp
@@ -49,30 +49,26 @@
],
}
-cc_binary {
+cc_binary_host {
name: "mk_payload",
srcs: [
"mk_payload.cc",
],
- shared_libs: [
+ static_libs: [
+ "lib_microdroid_metadata_proto",
"libbase",
+ "libcdisk_spec",
"libcuttlefish_fs",
"libcuttlefish_utils",
- "liblog",
- "libz",
- ],
- static_libs: [
- "lib_microdroid_metadata_proto_lite",
- "libcdisk_spec",
"libext2_uuid",
"libimage_aggregator",
"libjsoncpp",
+ "liblog",
+ "libprotobuf-cpp-full",
"libprotobuf-cpp-lite",
"libsparse",
"libxml2",
+ "libz",
],
- generated_sources: ["apex-info-list"],
- apex_available: [
- "com.android.virt",
- ],
+ static_executable: true,
}