I think it would be very interesting to see how a meson wine build would perform and affect the workflow. One benefit I don't see mentioned is the ability to generate compile_commands.json, which allows IDEs to perform intelli-sense on the codebase. Right now I use bear (https://github.com/rizsotto/Bear), but this requires you to regenerate the compile_commands.json whenever you add a file to wine.

If you can get past the technical hurdles mentioned above and more, I think many people would be interested in having it as an option alongside autotools.

On Mon, Jul 22, 2019 at 12:46 AM Nathan Singer <dundir@gmail.com> wrote:

Good Afternoon,

Over the last few days, I've been toying with the idea of converting the
existing build system for wine from autotools over to mesonbuild for the
additional flexibility in dependency compilation (i.e. autobuilding
dependencies as subprojects via wrapdb if shared libraries are not present).

Several other large projects are starting or have recently finished
similar conversion projects (Mesa3D) and if I move forward with this
task to completion, I'd like to clarify beforehand whether a pull
request for this would be considered?

Best Regards,
Nathan Singer