commit 2d2e4dba53eb425c7f4914234b19aced6f21e057
author Alan Stokes <alanstokes@google.com> Fri Jan 28 16:41:52 2022 +0000
committer Alan Stokes <alanstokes@google.com> Mon Jan 31 11:22:19 2022 +0000
tree bd9e1bcb878b98c1edc21a6c5e23d53afd71f789
parent 4382754aa87e94b5205500579d64a6c31268624f

Use --force-compile for tests

The test uses --force-compile outside the VM, so we also need to
inside the VM. But we want --compile for the normal case of
compilation, so we only produce exactly the required artifacts.

That means we have to pass whether we are testing or not from the host
to guest, so lots of plumbing is needed.

(Also figured out how to solve a problem with type deduction that the
me of a few months ago was baffled by.)

Bug: 211458160
Test: atest ComposTestCase
Change-Id: Ie7e36bc3fab40744e9f9ea5e5928126899d9060d

compos/Android.bp

diff --git a/compos/Android.bp b/compos/Android.bp
index c54348a..0bcbcdd 100644
--- a/compos/Android.bp
+++ b/compos/Android.bp
@@ -28,6 +28,7 @@
         "libprotobuf",
         "libregex",
         "libring",
+        "librustutils",
         "libscopeguard",
     ],
     prefer_rlib: true,