commit ae7c701d1c7facba978bef4ada8d8979d517468c
author Gurchetan Singh <gurchetansingh@google.com> Thu Jun 27 09:09:51 2024 -0700
committer Gurchetan Singh <gurchetansingh@google.com> Thu Jun 27 10:23:08 2024 -0700
tree f110900a94d25bb4f377c50ea2469c65af1c566b
parent 35880a2bd7891ffaedb8ffc83b1641b27ad068fc

gfxstream: fix VERBOSE logging change

Breaks meson build.  Two issues:

1) It requires a new API from AEMU base, which for the
   meson build doesn't work since it likes to keep working
   with AEMU v0.1.2

2) The logging facade itself is too QEMU 2.12 centric.  Upstream
   QEMU and crosvm's logging handlers are hooked into
   stream_renderer_{error, warn, info}, example:

https://github.com/qemu/qemu/blob/master/hw/display/virtio-gpu-rutabaga.c#L933

So VERBOSE shouldn't be AEMU anyways if you want a generic
host-side logging facade.

BUG=317816825
TEST=meson build

Change-Id: I659e10d8b2920b6478043df0ba5fff80ada05b1d

host/RendererImpl.cpp

diff --git a/host/RendererImpl.cpp b/host/RendererImpl.cpp
index a1b49ac..aaec95e 100644
--- a/host/RendererImpl.cpp
+++ b/host/RendererImpl.cpp
@@ -126,9 +126,11 @@
 
 bool RendererImpl::initialize(int width, int height, gfxstream::host::FeatureSet features,
                               bool useSubWindow, bool egl2egl) {
+#ifdef CONFIG_AEMU
     if (android::base::getEnvironmentVariable("ANDROID_EMUGL_VERBOSE") == "1") {
         set_gfxstream_enable_verbose_logs();
     }
+#endif
 
     if (mRenderWindow) {
         return false;