NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
038d17044a
kumquat-buildroot/package/lz4/lz4.mk

64 lines
1.7 KiB
Makefile
Raw Normal View History

lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
################################################################################
#
# lz4
#
################################################################################
package/lz4: bump version to 1.9.3 Signed-off-by: Norbert Lange <nolange79@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-11-27 11:29:47 +01:00
LZ4_VERSION = 1.9.3
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
LZ4_SITE = $(call github,lz4,lz4,v$(LZ4_VERSION))
lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
LZ4_INSTALL_STAGING = YES
boot, package: use SPDX short identifier for BSD-2c We want to use SPDX identifier for license string as much as possible. SPDX short identifier for BSD-2c is BSD-2-Clause. This change is done using following command. find . -name "*.mk" | xargs sed -ri '/LICENSE( )?[\+:]?=/s/BSD-2c/BSD-2-Clause/g' Signed-off-by: Rahul Bedarkar <rahulbedarkar89@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-30 15:43:39 +02:00
LZ4_LICENSE = BSD-2-Clause (library), GPL-2.0+ (programs)
lz4: fix legal info It moved, and programs are GPLv2+. Fixes: http://autobuild.buildroot.net/results/70a/70a526b265bb16a6be9f25c5044c65070706171c/ Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-03-02 22:44:42 +01:00
LZ4_LICENSE_FILES = lib/LICENSE programs/COPYING
lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
package/lz4: annotate CVE-2014-4715 CVE-2014-4715 is misclassified (by our CVE tracker) as affecting version 1.9.2, while in fact this issue has been fixed since lz4-r130: https://github.com/lz4/lz4/commit/140e6e72ddb6fc5f7cd28ce0c8ec3812ef4a9c08 See https://github.com/lz4/lz4/issues/818 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-03-28 10:51:38 +01:00
# CVE-2014-4715 is misclassified (by our CVE tracker) as affecting version
# 1.9.2, while in fact this issue has been fixed since lz4-r130:
# https://github.com/lz4/lz4/commit/140e6e72ddb6fc5f7cd28ce0c8ec3812ef4a9c08
# See https://github.com/lz4/lz4/issues/818
LZ4_IGNORE_CVES += CVE-2014-4715
Rename BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS Since a while, the semantic of BR2_PREFER_STATIC_LIB has been changed from "prefer static libraries when possible" to "use only static libraries". The former semantic didn't make much sense, since the user had absolutely no control/idea of which package would use static libraries, and which packages would not. Therefore, for quite some time, we have been starting to enforce that BR2_PREFER_STATIC_LIB should really build everything with static libraries. As a consequence, this patch renames BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS, and adjust the Config.in option accordingly. This also helps preparing the addition of other options to select shared, shared+static or just static. Note that we have verified that this commit can be reproduced by simply doing a global rename of BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS plus adding BR2_PREFER_STATIC_LIB to Config.in.legacy. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2014-12-03 22:41:29 +01:00
ifeq ($(BR2_STATIC_LIBS),y)
lz4: improve static only build support The current method of supporting static only build, removal of all lines that match the SHARED regex from lib/Makefile, is crude and fragile. Instead, patch lib/Makefile to allow disable of shared libraries. Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-20 06:52:46 +02:00
LZ4_MAKE_OPTS += BUILD_SHARED=no
lz4: disable static library on shared only Don't build the static library when BR2_SHARED_LIBS=y, to reduce build time. Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-24 13:14:43 +02:00
else ifeq ($(BR2_SHARED_LIBS),y)
LZ4_MAKE_OPTS += BUILD_STATIC=no
lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
endif
define HOST_LZ4_BUILD_CMDS
lz4: don't build library and tools in parallel Since commit e93fec6673e (lz4: bump to version 1.8.1.2) we use two make targets, 'lib' and 'lz4'. Both targets depend on the static library. When these targets run in parallel the two make instances that build the static library race against each other. Split these targets to ensure build order. Should fix: http://autobuild.buildroot.net/results/a8d/a8d956ff420f6a265c5c00b33646dbbc24ce2d48/ Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-21 22:58:52 +02:00
$(HOST_MAKE_ENV) $(HOST_CONFIGURE_OPTS) $(MAKE) -C $(@D) lib
$(HOST_MAKE_ENV) $(HOST_CONFIGURE_OPTS) $(MAKE) -C $(@D) lz4
lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
endef
define HOST_LZ4_INSTALL_CMDS
generic packages: use $(HOST_DIR) instead of $(HOST_DIR)/usr as prefix Remove the redundant usr/ component of the HOST_DIR paths. Since a previous commit added a symlink from $(HOST_DIR)/usr to $(HOST_DIR), everything keeps on working. This is a mechanical change with git grep -l '\$(HOST_DIR)/usr' | xargs sed -i 's%\(prefix\|PREFIX\)=\("\?\)\$(HOST_DIR)/usr%\1=\2$(HOST_DIR)%g' Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-05 13:14:18 +02:00
$(HOST_MAKE_ENV) $(HOST_CONFIGURE_OPTS) $(MAKE) PREFIX=$(HOST_DIR) \
package/lz4: only use PREFIX for host installation As noted by Peter Korsgaard, using DESTDIR=$(HOST_DIR) and PREFIX=/usr for the host installation is useless and actually incorrect (the pkg-config file contains incorrect paths). Instead, using PREFIX=$(HOST_DIR)/usr is simpler, and actually correct. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-29 23:17:06 +01:00
install -C $(@D)
lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
endef
package/lz4: simplify build/install logic No functional change. Rather than tracking both build targets and sub directory to run 'make install' from, use a make loop for the staging/target install logic, similar to how we are doing it to for the build step and directly use the Makefile in the sub directory rather than the helper lib/lz4 targets in the top level Makefile. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-07-27 18:20:07 +02:00
LZ4_DIRS = lib
package/lz4: make program installation optional Often lz4 is used as a library, and not as a standalone program. Excluding lz4 binary will save some space in this case. Indeed, the lz4 program is always statically linked against its library, which makes it duplicate the whole library size: $ ls -l usr/lib/liblz4.so.1.9.2 usr/bin/lz4 -rwxr-xr-x 1 thomas thomas 226724 27 juil. 16:33 usr/bin/lz4 -rwxr-xr-x 1 thomas thomas 156996 27 juil. 16:33 usr/lib/liblz4.so.1.9.2 Since lz4 is now primarily a library, it's moved to the "Libraries" section. Of course, installation of programs defaults to "yes" to preserve backward compatibility. Signed-off-by: Ed Spiridonov <edo.rus@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-05-23 19:34:25 +02:00
ifeq ($(BR2_PACKAGE_LZ4_PROGS),y)
package/lz4: simplify build/install logic No functional change. Rather than tracking both build targets and sub directory to run 'make install' from, use a make loop for the staging/target install logic, similar to how we are doing it to for the build step and directly use the Makefile in the sub directory rather than the helper lib/lz4 targets in the top level Makefile. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-07-27 18:20:07 +02:00
LZ4_DIRS += programs
package/lz4: make program installation optional Often lz4 is used as a library, and not as a standalone program. Excluding lz4 binary will save some space in this case. Indeed, the lz4 program is always statically linked against its library, which makes it duplicate the whole library size: $ ls -l usr/lib/liblz4.so.1.9.2 usr/bin/lz4 -rwxr-xr-x 1 thomas thomas 226724 27 juil. 16:33 usr/bin/lz4 -rwxr-xr-x 1 thomas thomas 156996 27 juil. 16:33 usr/lib/liblz4.so.1.9.2 Since lz4 is now primarily a library, it's moved to the "Libraries" section. Of course, installation of programs defaults to "yes" to preserve backward compatibility. Signed-off-by: Ed Spiridonov <edo.rus@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-05-23 19:34:25 +02:00
endif
lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
define LZ4_BUILD_CMDS
package/lz4: simplify build/install logic No functional change. Rather than tracking both build targets and sub directory to run 'make install' from, use a make loop for the staging/target install logic, similar to how we are doing it to for the build step and directly use the Makefile in the sub directory rather than the helper lib/lz4 targets in the top level Makefile. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-07-27 18:20:07 +02:00
$(foreach dir,$(LZ4_DIRS),\
package/lz4: make program installation optional Often lz4 is used as a library, and not as a standalone program. Excluding lz4 binary will save some space in this case. Indeed, the lz4 program is always statically linked against its library, which makes it duplicate the whole library size: $ ls -l usr/lib/liblz4.so.1.9.2 usr/bin/lz4 -rwxr-xr-x 1 thomas thomas 226724 27 juil. 16:33 usr/bin/lz4 -rwxr-xr-x 1 thomas thomas 156996 27 juil. 16:33 usr/lib/liblz4.so.1.9.2 Since lz4 is now primarily a library, it's moved to the "Libraries" section. Of course, installation of programs defaults to "yes" to preserve backward compatibility. Signed-off-by: Ed Spiridonov <edo.rus@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-05-23 19:34:25 +02:00
$(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) $(LZ4_MAKE_OPTS) \
package/lz4: simplify build/install logic No functional change. Rather than tracking both build targets and sub directory to run 'make install' from, use a make loop for the staging/target install logic, similar to how we are doing it to for the build step and directly use the Makefile in the sub directory rather than the helper lib/lz4 targets in the top level Makefile. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-07-27 18:20:07 +02:00
-C $(@D)/$(dir)
package/lz4: make program installation optional Often lz4 is used as a library, and not as a standalone program. Excluding lz4 binary will save some space in this case. Indeed, the lz4 program is always statically linked against its library, which makes it duplicate the whole library size: $ ls -l usr/lib/liblz4.so.1.9.2 usr/bin/lz4 -rwxr-xr-x 1 thomas thomas 226724 27 juil. 16:33 usr/bin/lz4 -rwxr-xr-x 1 thomas thomas 156996 27 juil. 16:33 usr/lib/liblz4.so.1.9.2 Since lz4 is now primarily a library, it's moved to the "Libraries" section. Of course, installation of programs defaults to "yes" to preserve backward compatibility. Signed-off-by: Ed Spiridonov <edo.rus@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-05-23 19:34:25 +02:00
)
lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
endef
define LZ4_INSTALL_STAGING_CMDS
package/lz4: simplify build/install logic No functional change. Rather than tracking both build targets and sub directory to run 'make install' from, use a make loop for the staging/target install logic, similar to how we are doing it to for the build step and directly use the Makefile in the sub directory rather than the helper lib/lz4 targets in the top level Makefile. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-07-27 18:20:07 +02:00
$(foreach dir,$(LZ4_DIRS),\
$(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) DESTDIR=$(STAGING_DIR) \
PREFIX=/usr $(LZ4_MAKE_OPTS) -C $(@D)/$(dir) install
)
lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
endef
define LZ4_INSTALL_TARGET_CMDS
package/lz4: simplify build/install logic No functional change. Rather than tracking both build targets and sub directory to run 'make install' from, use a make loop for the staging/target install logic, similar to how we are doing it to for the build step and directly use the Makefile in the sub directory rather than the helper lib/lz4 targets in the top level Makefile. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-07-27 18:20:07 +02:00
$(foreach dir,$(LZ4_DIRS),\
$(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) DESTDIR=$(TARGET_DIR) \
PREFIX=/usr $(LZ4_MAKE_OPTS) -C $(@D)/$(dir) install
)
lz4: new package Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-15 23:31:34 +02:00
endef
$(eval $(generic-package))
$(eval $(host-generic-package))
Reference in New Issue Copy Permalink