From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch v3 1/3] ninja: new package
Date: Mon, 26 Mar 2018 23:48:45 +0200 [thread overview]
Message-ID: <20180326234845.6049b5ca@windsurf.home> (raw)
In-Reply-To: <1466796149-25218-2-git-send-email-eric.le.bihan.dev@free.fr>
Hello Eric,
On Fri, 24 Jun 2016 21:22:27 +0200, Eric Le Bihan wrote:
> +NINJA_VERSION = v1.7.1
> +NINJA_SITE = $(call github,ninja-build,ninja,$(NINJA_VERSION))
> +NINJA_LICENSE = Apache-2.0
> +NINJA_LICENSE_FILES = COPYING
> +
> +HOST_NINJA_DEPENDENCIES = $(if $(BR2_PACKAGE_PYTHON3),host-python3,host-python)
Sorry for reviving such an old thread, but do you remember why you need
host-python3 or host-python ?
Indeed, this indicates that ninja supports both Python 2.x and Python
3.x, and Buildroot already guarantees that either Python 2.x or Python
3.x is available on the system, without the need to build host-python
or host-python3.
Therefore, why do we have this dependency ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-26 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 19:22 [Buildroot] [Patch v3 0/3] Ninja, Meson: new build systems Eric Le Bihan
2016-06-24 19:22 ` [Buildroot] [Patch v3 1/3] ninja: new package Eric Le Bihan
2016-07-03 19:31 ` Yann E. MORIN
2016-07-03 20:27 ` Peter Korsgaard
2018-03-26 21:48 ` Thomas Petazzoni [this message]
2016-06-24 19:22 ` [Buildroot] [Patch v3 2/3] python-meson: " Eric Le Bihan
2016-06-26 3:53 ` Baruch Siach
2016-07-03 20:24 ` Yann E. MORIN
2016-07-09 13:06 ` Eric Le Bihan
2016-06-24 19:22 ` [Buildroot] [Patch v3 3/3] docs/manual: document meson-based packages Eric Le Bihan
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=20180326234845.6049b5ca@windsurf.home \
--to=thomas.petazzoni@bootlin.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