From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] ninja/python-meson packages
Date: Sun, 13 Nov 2016 22:24:15 +0100 [thread overview]
Message-ID: <b4463231-ea51-a135-0cdd-dfc938898ee9@mind.be> (raw)
In-Reply-To: <CAHCOiUTEDHwLTqF6_UE2nWuYc+zgstCqYLbSpHY0_tBzF=v5+A@mail.gmail.com>
On 10-11-16 11:28, Thijs Vermeir wrote:
> Hi,
>
> On Wed, Nov 9, 2016 at 11:13 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Hello,
>>
>> On Wed, 9 Nov 2016 23:01:12 +0100, C?dric Marie wrote:
>>
>>> Le 09/11/2016 ? 21:28, Thomas Petazzoni a ?crit :
>>>> We are definitely fine with supporting the meson build system in
>>>> Buildroot. The only reason we didn't merge the patches that were
>>>> proposed is because no package was using them. As soon as we have one
>>>> package using this build system in Buildroot, we will of course happily
>>>> merge patches adding support for it.
>>>
>>> The current gstreamer1 version in Buildroot is 1.8.3.
>>> The support for meson was added in 1.9.2. So upgrading gstreamer1 is
>>> certainly necessary before merging Meson support.
>>
>> OK. However, isn't 1.9.x considered a "development" branch from the
>> point of view of GStreamer? At least for Glib/Gtk, the releases with
>> an odd are development ones if I remember correctly.
>
> Yes, that is correct. GStreamer 1.10.0 is now the latest stable
> release. Note that the
> support for the meson build system is only experimental and not on par
> with the autotools
> based build system.
Perhaps then it would be good for the GStreamer project if the meson build
system would be (build)-tested by the buildroot autobuild infrastructure, no?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-11-13 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 15:26 [Buildroot] ninja/python-meson packages Cédric Marie
2016-11-09 20:28 ` Thomas Petazzoni
2016-11-09 22:01 ` Cédric Marie
2016-11-09 22:13 ` Thomas Petazzoni
2016-11-10 10:28 ` Thijs Vermeir
2016-11-10 20:49 ` Cédric Marie
2016-11-13 21:24 ` Arnout Vandecappelle [this message]
2016-11-10 4:42 ` Baruch Siach
2016-11-10 8:18 ` Thomas Petazzoni
2016-11-10 10:05 ` Cédric Marie
2017-03-22 12:53 ` Fatih Aşıcı
2017-07-03 15:17 ` Vicente Olivert Riera
2017-07-03 22:08 ` Peter Korsgaard
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=b4463231-ea51-a135-0cdd-dfc938898ee9@mind.be \
--to=arnout@mind.be \
--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.