From: Andrey Yurovsky <yurovsky@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Add support for Meson build
Date: Fri, 6 Oct 2017 15:39:03 -0700 [thread overview]
Message-ID: <CAAkeqgWMAYm3B72AggbyamW3C6tEd27WdfyyW=EoBx4uFNhOyw@mail.gmail.com> (raw)
In-Reply-To: <20170727165026.4a5f59a1@windsurf.lan>
Hi,
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.
next prev parent reply other threads:[~2017-10-06 22:39 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 [this message]
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
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='CAAkeqgWMAYm3B72AggbyamW3C6tEd27WdfyyW=EoBx4uFNhOyw@mail.gmail.com' \
--to=yurovsky@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.