From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=FROM_EXCESS_BASE64, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4187CC48BD6 for ; Thu, 27 Jun 2019 12:54:09 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1156D2085A for ; Thu, 27 Jun 2019 12:54:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1156D2085A Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:50458 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgTui-0002g0-8q for qemu-devel@archiver.kernel.org; Thu, 27 Jun 2019 08:54:08 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:54300) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgTs8-00012X-5b for qemu-devel@nongnu.org; Thu, 27 Jun 2019 08:51:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hgTs2-0006KL-HZ for qemu-devel@nongnu.org; Thu, 27 Jun 2019 08:51:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:10056) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hgTs1-0005ec-QV for qemu-devel@nongnu.org; Thu, 27 Jun 2019 08:51:22 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 4A4E618DF7C for ; Thu, 27 Jun 2019 12:50:49 +0000 (UTC) Received: from redhat.com (ovpn-112-68.ams2.redhat.com [10.36.112.68]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 44F0A5D707; Thu, 27 Jun 2019 12:50:48 +0000 (UTC) Date: Thu, 27 Jun 2019 13:50:45 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Markus Armbruster Message-ID: <20190627125045.GG12358@redhat.com> References: <1560165301-39026-1-git-send-email-pbonzini@redhat.com> <1560165301-39026-4-git-send-email-pbonzini@redhat.com> <20190627090353.GA24929@redhat.com> <87blyjfc87.fsf@dusky.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87blyjfc87.fsf@dusky.pond.sub.org> User-Agent: Mutt/1.11.4 (2019-03-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Thu, 27 Jun 2019 12:50:49 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.132.183.28 Subject: Re: [Qemu-devel] [PATCH 3/7] configure: integrate Meson in the build system X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Cc: Paolo Bonzini , qemu-devel@nongnu.org Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Thu, Jun 27, 2019 at 02:23:52PM +0200, Markus Armbruster wrote: > Paolo Bonzini writes: > > But for now, since rules are > > written half in meson and half in make, ninja2make seems the most > > transparent way to integrate the two. > > > >> Part of the downside of our current build system is that although it > >> uses make, the usage is wierd and QEMU specific structure. It would > >> be a shame to pick meson and then again use it is a way that is wierd > >> and QEMU specific. > > > > I agree, this is why it's important to have at least a standard meson.build. > > > > Some knowledge of config-host.mak is needed, because meson.build uses > > declare_dependency() instead of dependency() to link with libraries that > > were already found by configure, but that's it. > > Ignorant question: could the switch to Meson enable doing less in > configure? It's big and sloooow. At a conceptual level meson is supposed to take over the role of both configure and automake, so you have a single domain specific language covering all aspects of your build system (though sometimes needs some external python helper scripts to cover missing features in meson). IOW, in a proper conversion, I'd expect configure to go away. I can imagine that being one of the last steps in QEMU's conversion though Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|