From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: Meson support in oe-core
Date: Mon, 07 Aug 2017 14:00:00 +0100 [thread overview]
Message-ID: <1502110800.18633.220.camel@linuxfoundation.org> (raw)
In-Reply-To: <41176f6a-807d-f488-7f55-38ee82cc48bf@linux.intel.com>
On Mon, 2017-08-07 at 15:19 +0300, Alexander Kanavin wrote:
> On 08/07/2017 03:09 PM, Jussi Kukkonen wrote:
> Looks like 2017 is when autotools is finally being replaced en masse
> by
> various projects, particularly those related to gnome stack. Even
> relatively large projects like gstreamer are going forward with it.
> The
> replacement is meson, whose advantages over autotools are major, and
> disadvantages are minor:
> http://mesonbuild.com/
>
> Ross and I have done some work on bringing meson support into oe-
> core.
> One recipe has been fully migrated to meson (including tricker bits
> like
> gtkdoc, and gobject introspection). Going forward that will be the
> default when a project has both that and autotools, and of course we
> should be ready for the situation when autotools support is removed
> from
> the upstream altogether.
>
> http://git.openembedded.org/meta-openembedded-contrib/log/?h=akanavin
> /meson
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavi
> n/meson
Thanks for looking at this. Whilst some project still have some support
for both, could we get timings of do_{configure|compile|install} for
autotools vs. meson?
Cheers,
Richard
next prev parent reply other threads:[~2017-08-07 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 12:09 [PATCH] libinput: Upgrade 1.7.3 -> 1.8.1 Jussi Kukkonen
2017-08-07 12:19 ` Meson support in oe-core Alexander Kanavin
2017-08-07 13:00 ` Richard Purdie [this message]
2017-08-07 13:47 ` Alexander Kanavin
2017-08-09 21:10 ` Randy MacLeod
2017-08-09 22:03 ` Burton, Ross
2017-08-09 23:17 ` Khem Raj
2017-08-10 10:11 ` Alexander Kanavin
2017-08-10 14:05 ` Leonardo Sandoval
2017-08-11 9:05 ` Alexander Kanavin
2017-08-08 21:07 ` [PATCH] libinput: Upgrade 1.7.3 -> 1.8.1 Richard Purdie
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=1502110800.18633.220.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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.