All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] ninja: new package
Date: Wed, 8 Jun 2016 22:17:50 +0200	[thread overview]
Message-ID: <20160608221750.796aa97f@free-electrons.com> (raw)
In-Reply-To: <20160604200301.2205a07e@itchy>

Hello,

On Sat, 4 Jun 2016 20:03:01 +0200, Eric Le Bihan wrote:

> Ninja is used by Meson, which I also provide for the target. It is true
> that the "Development tools" section now only lists "make" as build
> system, since autotools have been removed. I do not know if Buildroot
> users frequently need build systems on their target, but I provided it
> anyway.

"make" was only kept in the development tools because it was needed to
be able to *run* the uClibc test suite on the target. This has been
changed a few days ago, so I believe we don't really need "make"
anymore as a target package.

> If the policy is to provide build system packages only for the host,
> I'm fine with it.

Yes, please provide them only as host packages. However, do you have a
target package that would use them? Without this, the host packages are
orphan and never tested by anything, which isn't good.

So could you submit ninja/python-meson together with at least one
target package that uses them?

Thanks!

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

  reply	other threads:[~2016-06-08 20:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-04 13:34 [Buildroot] [PATCH 0/2] Ninja, Meson: new build systems Eric Le Bihan
2016-06-04 13:34 ` [Buildroot] [PATCH 1/2] ninja: new package Eric Le Bihan
2016-06-04 15:50   ` Bernd Kuhls
2016-06-04 18:03     ` Eric Le Bihan
2016-06-08 20:17       ` Thomas Petazzoni [this message]
2016-06-08 20:16   ` Thomas Petazzoni
2016-06-04 13:34 ` [Buildroot] [PATCH 2/2] python-meson: " Eric Le Bihan
2016-06-08 20:22   ` Thomas Petazzoni
2016-06-09 17:59     ` Eric Le Bihan
2016-06-09 19:28       ` Thomas Petazzoni

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=20160608221750.796aa97f@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 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.