Add support for Meson build

Hi,

Quoted 19 lines · Romain Naour

Thomas, Andrey, All,

Le 07/10/2017 ? 13:58, Thomas Petazzoni a ?crit :

Quoted 16 lines

Hello,

Quoted 11 lines · Andrey Yurovsky

Quoted 3 lines · Thomas Petazzoni

No, let's wait to have a few Meson-based packages in Buildroot, and then we'll have a package infrastructure. This will allow us to see what are the commonalities, what are the differences, etc.

systemd 235 is released (https://lwn.net/Articles/735691/) and it drops autoconf/automake and only has meson as the build system (in 234 they warned this would happen next) so perhaps that's a good starting point for buildroot to integrate meson support? I'm happy to help out if no one else was already working on it.

Quoted 4 lines

Quoted 1 line

This would indeed be a very compelling reason to support meson.

Also the next enlightenment release (0.22) will only support meson.

I was able to add a package/pkg-meson.mk wrapper (that seems to be missing from the Meson patch set, or did I completely miss it?) and built the previously submitted libmpdclient version bump via the $(eval $(meson-package)) wrapper. I'll work on version bumping systemd and converting it to use that wrapper as well. If possible I'd like to get this more or less right, what would a reasonable patch set look like? I was thinking, as a patch set:
1. resubmit the Meson patches (package/meson, documentation) by J?rg Krause

2. add package/pkg-meson.mk
3. resubmit the libmpdclient version bump patch by J?rg Krause but with $(eval $(meson-package)) changes
4. submit the systemd version bump and meson conversion patch(es)

That way we have the infrastructure, documentation, and two packages utilizing the infrastructure in one set to review. Does that sound alright?