From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 33AED6DE0360 for ; Sun, 12 Jan 2020 04:20:17 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.066 X-Spam-Level: X-Spam-Status: No, score=-0.066 tagged_above=-999 required=5 tests=[AWL=-0.065, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nuRV05o3yWOb for ; Sun, 12 Jan 2020 04:20:16 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id D14776DE0243 for ; Sun, 12 Jan 2020 04:20:15 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1iqcDx-0007P7-I2; Sun, 12 Jan 2020 07:20:09 -0500 Received: (nullmailer pid 3749612 invoked by uid 1000); Sun, 12 Jan 2020 12:20:07 -0000 From: David Bremner To: Jani Nikula , notmuch@notmuchmail.org Subject: Re: [RFC PATCH] build: add meson build system In-Reply-To: <20200111164049.8237-1-jani@nikula.org> References: <20200111164049.8237-1-jani@nikula.org> X-List-To: notmuch Date: Sun, 12 Jan 2020 08:20:07 -0400 Message-ID: <87r2043lzc.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jan 2020 12:20:17 -0000 Jani Nikula writes: > This is a draft patch adding basic configure, build and test support > for the binaries. Everything else is left out for now. It would be a > considerable amount of work to convert everything, and I don't expect > it to be possible in one go anyway. If there's interest in adding > meson support, it would have to happen gradually, side-by-side with > the current system, with a reasonably long transition period. But > there's no point in going beyond the patch at hand if folks decide the > focus should remain on the current system. Personally I think the idea is worth pursuing, but I admit I don't have much experience with meson/ninja. How much churn can we expect from meson changes? It seems there is something like one meson point release per month. Are the tests supposed to be working fully in this version? When I run % meson && cd build && ninja && ninja test I get failures in T010, T351, T356, T357, T391, T395, and T710. At a glance it looks like mainly out-of-tree related problems to finding e.g. json_check_nodes.py and message-id-parse. It also looks like a few variables like TEST_RUBY and NOTMUCH_HAVE_PYTHON3_CFFI are not being set. d