All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Marie" <cedric.marie@openmailbox.org>
To: buildroot@busybox.net
Subject: [Buildroot] ninja/python-meson packages
Date: Wed, 9 Nov 2016 23:01:12 +0100	[thread overview]
Message-ID: <37cfb466-91a2-2434-24a4-dbd13ddfbc0f@openmailbox.org> (raw)
In-Reply-To: <20161109212812.39399895@free-electrons.com>

Hi,

+ Eric Le Bihan who first proposed ninja/meson support.

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.


>> 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.

Roughly, add dependency on ninja, add an option in cmake configure step 
(-G ninja) and use ninja instead of make in build and install commands.


> 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?

That sounds good to me :)

An option in "Build options" is definitely more appropriate. In the 
first place I had just added it in package/cmake/Config.in - which made 
it appear in target development tools.
Then I will check with several existing CMake packages in buildroot.

Regarding Meson integration, I think that Eric - if he's still 
interested in working on that - is the right person. I understand that 
his patches didn't provide pkg-meson.mk yet, but he proposed to do so. 
Am I right?


-- 
C?dric

  reply	other threads:[~2016-11-09 22:01 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 [this message]
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=37cfb466-91a2-2434-24a4-dbd13ddfbc0f@openmailbox.org \
    --to=cedric.marie@openmailbox.org \
    --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.