From 0d9dca99e9839b2867eb4df7c4b00471d440e743 Mon Sep 17 00:00:00 2001
From: Jordan Petridis <jpetridis@gnome.org>
Date: Thu, 4 Oct 2018 04:58:57 +0300
Subject: [PATCH] Meson: capture the output of the custom target

Previously meson would withhold the stdout output, and only
print it once the job was finished. This was a bit problematic
with the current way we wire cargo into meson, cause you have
no output of whats going on till then causing a degraded UX.

With this change output is printed directly to stdout and
behaves as expected.

https://mesonbuild.com/Reference-manual.html#custom_target
---
 meson.build | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meson.build b/meson.build
index 2b7e472..d2854ee 100644
--- a/meson.build
+++ b/meson.build
@@ -53,6 +53,7 @@ cargo_release = custom_target('cargo-build',
                         output: ['gnome-podcasts'],
                         install: true,
                         install_dir: podcasts_bindir,
+                        console: true,
                         command: [cargo_script,
                                   '@CURRENT_SOURCE_DIR@',
                                   '@OUTPUT@',