Although ninja is a meson dependency, some OSes do not have support to
meson. Knowning that, let's explicitly add a "ninja" mapping so we get
it installed even when "meson" is not supported. It'll help us, later
on, when we install meson from pip.

Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com>
---
 guests/vars/mappings.yml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/guests/vars/mappings.yml b/guests/vars/mappings.yml
index 8daa65c..10d0cb2 100644
--- a/guests/vars/mappings.yml
+++ b/guests/vars/mappings.yml
@@ -455,6 +455,10 @@ mappings:
     Ubuntu16:
     Ubuntu18:
 
+  ninja:
+   default: ninja-build
+   FreeBSD: ninja
+
   mingw32-curl:
     Fedora: mingw32-curl
 
-- 
2.23.0

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Tue, 2019-10-01 at 16:28 +0200, Fabiano Fidêncio wrote:
> +++ b/guests/vars/mappings.yml
> @@ -455,6 +455,10 @@ mappings:
> +  ninja:
> +   default: ninja-build
> +   FreeBSD: ninja

Doing this would be a good idea regardless, since we invoke ninja
directly.

Reviewed-by: Andrea Bolognani <abologna@redhat.com>

-- 
Andrea Bolognani / Red Hat / Virtualization

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list