fischerling

I have a two branches introducing meson as a build system on top of [master](https://github.com/fischerling/liburing/tree/meson) as well as [liburing-2.0](https://github.com/fischerling/liburing/tree/2.0-meson) containing the suggested changes from @ntonnaett. The branch based on liburing-2.0...

> meson file for each folder is probably too much (I mean for include dir mostly). What is the reason to drop the include/meson.build file? To reduce the diff because...

For anyone interested I updated the meson build code for liburing-2.2 at [fischerling/liburing/meson-liburing-2.2](https://github.com/fischerling/liburing/tree/meson-liburing-2.2) and submitted a [pull request](https://github.com/mesonbuild/wrapdb/pull/510) to update the version included in the meson wrapdb.

> > included in the meson wrapdb. > > I prefer the idea of upstreaming current PR instead do it for wrapdb. I also prefer having the meson changes upstream....

If I am not alone maintaining and being responsible for the meson code as @tp-m comment shows, I would also happily maintain and provide help for a build system based...

I am thinking about the minimum required meson version. meson >= 0.60 would allow implementing the current `make install-tests` make target using meson [installation tags](https://mesonbuild.com/Installing.html#installation-tags). Currently we require meson >=...

> > improve meson test tooling for running the tests in a loop > > do we have an issue on the meson tracker? I really want to avoid any...

> > Build test / build (x86_64, clang, clang, clang, clang++) > > still failed Sorry about that. The unnecessary explicit setting of the FLAGS in the workflow overrode the...

> ``` > io_uring_prep_recv_multishot.3 > ``` Strange since the file was added with 8e182bbdff0f5d6e1640190f713ed11060470b5f. And it works without problems on my system. Could you check if the file does indead...

> NAK. > > > ```diff > > # x86 (32-bit) gcc > > - - arch: i686 > > + - arch: x86 > > + cpu: i686 >...