From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] ninja/python-meson packages
Date: Mon, 3 Jul 2017 16:17:45 +0100 [thread overview]
Message-ID: <6cbd72f3-e32d-6b85-0c64-47b9c2664f59@imgtec.com> (raw)
In-Reply-To: <d309c350-d2df-4eb0-8114-bea29d3a05dd@gmail.com>
libinput is another package that will migrate to meson, and it will stop
supporting autotools. From
https://lists.freedesktop.org/archives/wayland-devel/2017-June/034286.html :
"The first RC for libinput 1.8 is now available.
The biggest change in this release is that libinput has switched to
meson as primary build system, the 1.8.x releases are the last ones to
support (and be released with) autotools so you're encouraged to start
switching your build processes over to meson."
Regards,
Vincent
On 22/03/17 12:53, Fatih A??c? wrote:
> On Wednesday, November 9, 2016 6:26:38 PM +03, C?dric Marie wrote:
>> Hi,
>>
>> Regarding python-meson package that was proposed here:
>> http://lists.busybox.net/pipermail/buildroot/2016-June/163437.html
>>
>>>> However, I could provide a real package infrastructure named
>>>> "meson-package",
>>>> but as stated in the discussion about adding support for Cargo (the
>>>> Rust
>>>> package manager), to provide such infrastructure, at least one
>>>> package using
>>>> it should also be provided (it is sensible to have a working example of
>>>> the infrastructure).
>>
>>> I would not say one, but at least 4-5 packages, with a pretty good
>>> confidence that more packages would be added later on.
>>
>> Gstreamer has added Meson as an alternative build system (to
>> Autotools) since August 2016:
>>
>> https://cgit.freedesktop.org/gstreamer/gstreamer/commit/meson.build?id=b2f9808722a0254acba17ef98a612a2792184e12
>>
>
> libepoxy is also another project that uses Meson build system. Since 1.4.0,
> the "Building" section in README.md has commands to build with Meson:
>
> https://github.com/anholt/libepoxy/tree/1.4.1#building
>
> Regards,
> Fatih
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2017-07-03 15:17 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
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 [this message]
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=6cbd72f3-e32d-6b85-0c64-47b9c2664f59@imgtec.com \
--to=vincent.riera@imgtec.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.