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

34 lines
1.0 KiB
Makefile
Raw Normal View History

Normalize separator size to 80 Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-06-06 01:53:30 +02:00
################################################################################
libffi: new package libffi is needed by the Python interpreter. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2011-01-08 15:15:24 +01:00
#
# libffi
#
Normalize separator size to 80 Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-06-06 01:53:30 +02:00
################################################################################
libffi: new package libffi is needed by the Python interpreter. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2011-01-08 15:15:24 +01:00
libffi: bump to 3.1 Status of the patches: - libffi-001-Fix-installation-location-of-libffi.patch, preserved. - libffi-002-Fix-use-of-compact-eh-frames-on-MIPS.patch, preserved - libffi-arc-01-Add-ARC-support.patch, removed, ARC support was merged upstream as of commit b082e15091961373c03d10ed0251f619ebb6ed76. - libffi-arc-02-Rebuild-for-ARC-additions.patch, removed, this patch was merged upstream as of commit 0f8690a84c874ec09a090c8c6adfb93c594acac6. - libffi-003-fix-typo.patch, added, reported on the upstream mailing list as being necessary, will be part of the next 3.1.1 release. - libffi-004-Add-missing-GNU-stack-markings-in-win32.S.patch, same status as patch 003. - libffi-005-Fix-paths-in-libffi.pc.in.patch, same status as patch 003. The 3.1 release adds support for a number of architectures: ARC support, ppc64le support, NIOS II support. See https://sourceware.org/ml/libffi-announce/2014/msg00000.html for details. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-06-28 23:52:19 +02:00
LIBFFI_VERSION = 3.1
libffi: bump version It makes more sense to use a released version for 2013.02 rather than a git snapshot. The build system now correctly installs libffi.pc, so we can drop the manual install. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-18 23:28:42 +01:00
LIBFFI_SITE = ftp://sourceware.org/pub/libffi/
libffi: add license info Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-13 02:05:44 +01:00
LIBFFI_LICENSE = MIT
LIBFFI_LICENSE_FILES = LICENSE
libffi: new package libffi is needed by the Python interpreter. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2011-01-08 15:15:24 +01:00
LIBFFI_INSTALL_STAGING = YES
libffi: switch to using a Git version, brings Microblaze and Xtensa support We already had backported patches for the Blackfin and AArch64 support, and now we would have needed to also backport the Xtensa support and the Microblaze support. This starts to get crazy. Let's switch to using a Git version from Github, until libffi finally releases a new stable version. In order to achieve this, we also need to: * autoreconf the package, so that a libffi.pc file gets generated * manually install the libffi.pc file, because it doesn't get installed by libffi Makefile, for some reason * remove the part of the target post install hook that was messing with libffi.pc, since it was modifying the one in STAGING_DIR (which is odd for a target post install hook), and the libffi.pc file is anyway not installed to the target anymore. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-04 13:52:09 +01:00
LIBFFI_AUTORECONF = YES
libffi: new package libffi is needed by the Python interpreter. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2011-01-08 15:15:24 +01:00
# Move the headers to the usual location, and adjust the .pc file
libffi: bump version It makes more sense to use a released version for 2013.02 rather than a git snapshot. The build system now correctly installs libffi.pc, so we can drop the manual install. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-18 23:28:42 +01:00
# accordingly.
libffi: new package libffi is needed by the Python interpreter. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2011-01-08 15:15:24 +01:00
define LIBFFI_MOVE_STAGING_HEADERS
libffi: minor corrections in post install hooks In order to be sure that we just deal with the includes related with the actual package described into libffi.mk it is better to explicitly specify the version of the libffi we deal with into the post install hook. As dev files are deprecated in target rootfs target post install hook was also deleted. Signed-off-by: Nicolas Ménégale <nicolas.menegale@openwide.fr> Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-08-28 11:48:59 +02:00
mv $(STAGING_DIR)/usr/lib/libffi-$(LIBFFI_VERSION)/include/*.h $(STAGING_DIR)/usr/include/
libffi: bump version It makes more sense to use a released version for 2013.02 rather than a git snapshot. The build system now correctly installs libffi.pc, so we can drop the manual install. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-18 23:28:42 +01:00
$(SED) '/^includedir.*/d' -e '/^Cflags:.*/d' \
$(STAGING_DIR)/usr/lib/pkgconfig/libffi.pc
libffi: new package libffi is needed by the Python interpreter. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2011-01-08 15:15:24 +01:00
rm -rf $(TARGET_DIR)/usr/lib/libffi-*
endef
LIBFFI_POST_INSTALL_STAGING_HOOKS += LIBFFI_MOVE_STAGING_HEADERS
libffi: remove some header files installed in /usr/lib in the target For some reason, libffi installs some header files in /usr/lib/libffi-<version>/include, which is a non-standard location and therefore they do not get removed automatically by the target-finalize logic. This commit adds a post-install hook in libffi.mk to get rid of these unneeded headers on the target. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-06-28 23:52:20 +02:00
# Remove headers that are not at the usual location from the target
define LIBFFI_REMOVE_TARGET_HEADERS
$(RM) -rf $(TARGET_DIR)/usr/lib/libffi-$(LIBFFI_VERSION)
endef
LIBFFI_POST_INSTALL_TARGET_HOOKS += LIBFFI_REMOVE_TARGET_HEADERS
libffi: switch to using a Git version, brings Microblaze and Xtensa support We already had backported patches for the Blackfin and AArch64 support, and now we would have needed to also backport the Xtensa support and the Microblaze support. This starts to get crazy. Let's switch to using a Git version from Github, until libffi finally releases a new stable version. In order to achieve this, we also need to: * autoreconf the package, so that a libffi.pc file gets generated * manually install the libffi.pc file, because it doesn't get installed by libffi Makefile, for some reason * remove the part of the target post install hook that was messing with libffi.pc, since it was modifying the one in STAGING_DIR (which is odd for a target post install hook), and the libffi.pc file is anyway not installed to the target anymore. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-04 13:52:09 +01:00
all packages: rename XXXTARGETS to xxx-package Also remove the redundant $(call ...). This is a purely mechanical change, performed with find package linux toolchain boot -name \*.mk | \ xargs sed -i -e 's/$(eval $(call GENTARGETS))/$(eval $(generic-package))/' \ -e 's/$(eval $(call AUTOTARGETS))/$(eval $(autotools-package))/' \ -e 's/$(eval $(call CMAKETARGETS))/$(eval $(cmake-package))/' Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-03 00:07:32 +02:00
$(eval $(autotools-package))
all packages: use new host-xxx-package macros This is a purely mechanical change, performed with find package linux toolchain boot -name \*.mk | \ xargs sed -i -e 's/$(eval $(call GENTARGETS,host))/$(eval $(host-generic-package))/' \ -e 's/$(eval $(call AUTOTARGETS,host))/$(eval $(host-autotools-package))/' \ -e 's/$(eval $(call CMAKETARGETS,host))/$(eval $(host-cmake-package))/' Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-03 00:06:54 +02:00
$(eval $(host-autotools-package))
Reference in New Issue Copy Permalink