69808c7536
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>
29 lines
983 B
Makefile
29 lines
983 B
Makefile
################################################################################
|
|
#
|
|
# glog
|
|
#
|
|
################################################################################
|
|
|
|
GLOG_VERSION = 0.3.5
|
|
GLOG_SITE = $(call github,google,glog,v$(GLOG_VERSION))
|
|
GLOG_INSTALL_STAGING = YES
|
|
GLOG_LICENSE = BSD-3-Clause
|
|
GLOG_LICENSE_FILES = COPYING
|
|
|
|
ifeq ($(BR2_PACKAGE_GFLAGS),y)
|
|
GLOG_DEPENDENCIES = gflags
|
|
endif
|
|
|
|
# glog can optionally use atomic __sync built-ins. However, its
|
|
# configure script only checks for the availability of the 4 bytes
|
|
# version, but the code also uses the 1 byte version. While this works
|
|
# on most architectures, it does not on architectures that implement
|
|
# only the 4 bytes version, such as Microblaze. So if the architecture
|
|
# does not implement the 1 byte version, we hint the configure script
|
|
# that atomic built-ins should not be used.
|
|
ifeq ($(BR2_TOOLCHAIN_HAS_SYNC_1),)
|
|
GLOG_CONF_ENV += ac_cv___sync_val_compare_and_swap=no
|
|
endif
|
|
|
|
$(eval $(autotools-package))
|