From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Add support for Meson build
Date: Thu, 12 Oct 2017 08:42:33 +0200 [thread overview]
Message-ID: <1507790553.8783.2.camel@embedded.rocks> (raw)
In-Reply-To: <20171011065502.GA29633@itchy>
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
next prev parent reply other threads:[~2017-10-12 6:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 9:45 [Buildroot] [PATCH 0/3] Add support for Meson build Jörg Krause
2017-07-27 9:45 ` [Buildroot] [PATCH v2 1/3] meson: new package Jörg Krause
2017-07-27 9:45 ` [Buildroot] [PATCH v2 2/3] docs/manual: document meson-based packages Jörg Krause
2017-07-27 9:45 ` [Buildroot] [PATCH 3/3] libmpdclient: bump to version 2.13 Jörg Krause
2017-07-27 10:11 ` [Buildroot] [PATCH 0/3] Add support for Meson build Vicente Olivert Riera
2017-07-27 10:13 ` Jörg Krause
2017-07-27 10:19 ` Vicente Olivert Riera
2017-07-27 14:50 ` Thomas Petazzoni
2017-10-06 22:34 ` Andrey Yurovsky
2017-10-06 22:39 ` Andrey Yurovsky
2017-10-07 11:58 ` Thomas Petazzoni
2017-10-07 13:06 ` Romain Naour
2017-10-11 3:51 ` Andrey Yurovsky
2017-10-11 6:55 ` Eric Le Bihan
2017-10-12 6:42 ` Jörg Krause [this message]
2017-10-13 11:49 ` Adam Duskett
2017-10-11 20:38 ` Arnout Vandecappelle
2017-10-11 21:21 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1507790553.8783.2.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox