From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [RFC PATCH] build: add meson build system
Date: Sun, 12 Jan 2020 08:20:07 -0400 [thread overview]
Message-ID: <87r2043lzc.fsf@tethera.net> (raw)
In-Reply-To: <20200111164049.8237-1-jani@nikula.org>
Jani Nikula <jani@nikula.org> 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
next prev parent reply other threads:[~2020-01-12 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 16:40 [RFC PATCH] build: add meson build system Jani Nikula
2020-01-12 12:20 ` David Bremner [this message]
2020-01-12 13:42 ` Jani Nikula
2020-01-12 15:07 ` Tomi Ollila
2020-02-17 11:10 ` [RFC PATCH] build: Add meson.build for Ruby bindings Thomas Schneider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2043lzc.fsf@tethera.net \
--to=david@tethera.net \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).