[Buildroot] [PATCH 0/3] Add support for Meson build

From: Adam Duskett <aduskett@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Add support for Meson build
Date: Fri, 13 Oct 2017 07:49:59 -0400	[thread overview]
Message-ID: <CAFSsvmqgku41Jdd47B3GEOY39BS9OzC+fZhUfFSRG2p0nUDN4w@mail.gmail.com> (raw)
In-Reply-To: <1507790553.8783.2.camel@embedded.rocks>

Hey all;

gstreamer is also moving to meson as well, so I am glad to see this
hapening sooner than later!

Adam

On Thu, Oct 12, 2017 at 2:42 AM, J?rg Krause
<joerg.krause@embedded.rocks> wrote:
> Hi Eric,
>
> On Wed, 2017-10-11 at 08:55 +0200, Eric Le Bihan wrote:
>> Hi all!
>>
>> On 17-10-10 20:51:55, Andrey Yurovsky wrote:
>> > Hi,
>> >
>> > On Sat, Oct 7, 2017 at 6:06 AM, Romain Naour <romain.naour@smile.fr> wrote:
>> > > Thomas, Andrey, All,
>> > >
>> > > Le 07/10/2017 ? 13:58, Thomas Petazzoni a ?crit :
>> > > > Hello,
>> > > >
>> > > > On Fri, 6 Oct 2017 15:39:03 -0700, Andrey Yurovsky wrote:
>> > > >
>> > > > > On Thu, Jul 27, 2017 at 7:50 AM, Thomas Petazzoni
>> > > > > <thomas.petazzoni@free-electrons.com> wrote:
>> > > > > > 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.
>> > > >
>> > > > 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
>>
>> 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.
>
>> > 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
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot