2016-06-24 21:22:27 +02:00
|
|
|
################################################################################
|
|
|
|
|
#
|
|
|
|
|
# ninja
|
|
|
|
|
#
|
|
|
|
|
################################################################################
|
|
|
|
|
|
package: remove 'v' prefix from github-fetched packages
On Github, a large number of projects name their tag vXYZ (i.e v3.0,
v0.1, etc.). In some packages we do:
<pkg>_VERSION = v0.3
<pkg>_SITE = $(call github foo,bar,$(<pkg>_VERSION))
And in some other packages we do:
<pkg>_VERSION = 0.3
<pkg>_SITE = $(call github foo,bar,v$(<pkg>_VERSION))
I.e in one case we consider the version to be v0.3, in the other case
we consider 0.3 to be the version.
The problem with v0.3 is that when used in conjunction with
release-monitoring.org, it doesn't work very well, because
release-monitoring.org has the concept of "version prefix" and using
that they drop the "v" prefix for the version.
Therefore, a number of packages in Buildroot have a version that
doesn't match with release-monitoring.org because Buildroot has 'v0.3'
and release-monitoring.org has '0.3'.
Since really the version number of 0.3, is makes sense to update our
packages to drop this 'v'.
This commit only addresses the (common) case of github packages where
the prefix is simply 'v'. Other cases will be handled by separate
commits. Also, there are a few cases that couldn't be handled
mechanically that aren't covered by this commit.
Signed-off-by: Victor Huesca <victor.huesca@bootlin.com>
[Arnout: don't change flatbuffers, json-for-modern-cpp, libpagekite,
python-scapy3k, softether]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-06-12 08:42:06 +02:00
|
|
|
NINJA_VERSION = 1.9.0
|
|
|
|
|
NINJA_SITE = $(call github,ninja-build,ninja,v$(NINJA_VERSION))
|
2016-06-24 21:22:27 +02:00
|
|
|
NINJA_LICENSE = Apache-2.0
|
|
|
|
|
NINJA_LICENSE_FILES = COPYING
|
|
|
|
|
|
2019-05-13 23:53:37 +02:00
|
|
|
# Although Ninja supports both Python2 and Python3, we enforce Python3
|
|
|
|
|
# on the host for the following reason: Meson is the only package
|
|
|
|
|
# using Ninja so far and Meson requires Python3. In this way, we
|
|
|
|
|
# prevent both Python2 and Python3 from being created on the host,
|
|
|
|
|
# which is time consuming and without benefit.
|
|
|
|
|
HOST_NINJA_DEPENDENCIES = host-python3
|
2016-06-24 21:22:27 +02:00
|
|
|
|
|
|
|
|
define HOST_NINJA_BUILD_CMDS
|
|
|
|
|
(cd $(@D); ./configure.py --bootstrap)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define HOST_NINJA_INSTALL_CMDS
|
2017-07-05 13:14:19 +02:00
|
|
|
$(INSTALL) -m 0755 -D $(@D)/ninja $(HOST_DIR)/bin/ninja
|
2016-06-24 21:22:27 +02:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
$(eval $(host-generic-package))
|
