Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ninja/python-meson packages
Date: Wed, 9 Nov 2016 21:28:12 +0100	[thread overview]
Message-ID: <20161109212812.39399895@free-electrons.com> (raw)
In-Reply-To: <98b7a6164112ee321e9220d5b8c47a33@openmailbox.org>

Hello,

On Wed, 09 Nov 2016 16:26:38 +0100, C?dric Marie wrote:

> > 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
> 
> And I suppose that other projects are likely to switch... The decrease 
> of build time is really interesting compared to Autotools, CMake, and 
> even CMake with ninja backend.

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.

> By the way, is there any chance to give CMake package the possibility to 
> use ninja backend? (which will also decrease build time of CMake 
> packages)

I don't know exactly what is involved in such a change, but in
principle, I don't see why we wouldn't accept that.

> I have local modifications of my buildroot tree that achieve that, but 
> I'm not sure about the right way to propose it. I have added an option 
> (BR2_PACKAGE_CMAKE_NINJA) but it appears in target packages > 
> Development tools, while it is not intended for the target. Would it be 
> a better idea to create a specific package infra (pkg-cmake-ninja.mk)?

Can each and every CMake package use Ninja as a backend?

At first, it should probably just be an option under "Build options",
that affects the behavior of pkg-cmake. Once we get a better
understanding of what it means to use Ninja in terms of additional
dependencies to build, and number of CMake packages that work/don't
work with it, then we can decide what to do.

How does that sound?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-11-09 20:28 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 [this message]
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
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=20161109212812.39399895@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox