Add support for Meson build
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 0/3] Add support for Meson build
Hi Eric,
Quoted 39 lines · Eric Le Bihan
Hi all!
Quoted 27 lines · Andrey Yurovsky
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.
Quoted 8 lines
I was able to add a
package/pkg-meson.mkwrapper (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
Quoted 6 lines
I resubmitted the series, with a version bump to 0.43.0 and other suggested changes.
@J?rg: in your respin of the series, why was the github helper dropped in favor of a direct tarball download?
As Arnout has responded in a follow-up review, we prefer an uploaded tarball because the github tarballs might change from time to time. Furthermore, the uploaded tarballs often contains autogenerated files which frees us from doing autoreconf for the package.
Quoted 11 lines
Quoted 8 lines
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?
@Andrey: I'll be happy to test your patches.
Best regards,
J?rg Krause