From: Florian Schmaus <[email protected]>
To: Bart Van Assche <[email protected]>, [email protected]
Subject: Re: [PATCH liburing] add additional meson build system support
Date: Fri, 29 Jul 2022 09:47:47 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <20220727205329.jgr5i5ou4oxc2ttc@pasture>
On 27.07.22 22:53, Florian Fischer wrote:
> On 27.07.2022 12:21, Bart Van Assche wrote:
>> On 7/27/22 08:27, Florian Fischer wrote:
>>> 11 files changed, 619 insertions(+), 4 deletions(-)
>>
>> To me this diffstat tells me that this patch series adds a lot of complexity
>> instead of removing complexity.
>
> That's because Jens wants to keep both build systems in the repository.
>
> .github/workflows/build.yml | 44 +++++--
> .gitignore | 2 +
> Makefile | 84 ------------
> Makefile.common | 6 -
> Makefile.quiet | 11 --
> configure | 467 -----------------------------------------------------------------
> examples/Makefile | 41 ------
> examples/meson.build | 19 +++
> man/meson.build | 116 ++++++++++++++++
> meson.build | 119 +++++++++++++++++
> meson_options.txt | 14 ++
> src/Makefile | 87 ------------
> src/include/liburing/compat.h.in | 7 +
> src/include/liburing/meson.build | 51 +++++++
> src/include/meson.build | 3 +
> src/meson.build | 28 ++++
> test/Makefile | 238 ---------------------------------
> test/meson.build | 219 +++++++++++++++++++++++++++++++
> 18 files changed, 609 insertions(+), 947 deletions(-)
>
> This is what the diffstat could look like if we would remove the old build system.
To point this out explicitly:
old Makefile-based build system: 947 LoC
new Meson-based build system: 609 LoC
That is a significant reduction in build-system complexity, while the
new Meson-based build system has more features, e.g., out-of-source
builds and a sensible test framework. For further features, see the
cover-letter of this patch set.
- Flow
prev parent reply other threads:[~2022-07-29 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 15:27 [PATCH liburing] add additional meson build system support Florian Fischer
2022-07-27 15:27 ` [PATCH liburing 1/9] add Meson build system Florian Fischer
2022-07-27 15:27 ` [PATCH liburing 2/9] meson: update meson build files for liburing 2.3 Florian Fischer
2022-07-27 15:27 ` [PATCH liburing 3/9] meson: update available tests to " Florian Fischer
2022-07-27 15:27 ` [PATCH liburing 4/9] meson: update installed manpages " Florian Fischer
2022-07-27 15:27 ` [PATCH liburing 5/9] meson: add default test setup running each test once Florian Fischer
2022-07-27 15:27 ` [PATCH liburing 6/9] meson: support building without libc Florian Fischer
2022-07-27 15:27 ` [PATCH liburing 7/9] meson: add 'raw' test suite Florian Fischer
2022-07-27 15:27 ` [PATCH liburing 8/9] github bot: add jobs for meson Florian Fischer
2022-07-27 15:27 ` [PATCH liburing 9/9] meson: update available examples to liburing 2.3 Florian Fischer
2022-07-27 19:21 ` [PATCH liburing] add additional meson build system support Bart Van Assche
2022-07-27 20:53 ` Florian Fischer
2022-07-29 7:47 ` Florian Schmaus [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox