kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/libusb-compat/Makefile

26 lines
655 B
Makefile
Raw Normal View History

libusb-compat: Add DIST_SUBDIR to avoid checksum error pkgsrc changes: --------------- * Use release archive from Github to avoid the dependency on autotools and to remove conflict with the tag archive potentially present in ${DISTDIR} which has the same name but a different checksum. * Reorder variables to be compliant with pkgsrc policy described in doc/Makefile-example.
2020-10-13 08:10:35 +02:00
# $NetBSD: Makefile,v 1.11 2020/10/13 06:10:35 triaxx Exp $
Initial import of libusb-compat-0.1.4. Notes: depends on libusbx (we need a switch between the two) Conflicts with libusb (we need a switch between the two) libusb-compat-0.1 is a replacement for libusb-0.1. However, instead of being an actual implementation, libusb-0.1 is more of a compatibility layer (or wrapper) which just converts libusb-0.1 calls into their libusb-1.0 equivalents. It aims to look, feel and behave exactly like libusb-0.1. As it is a replacement, you cannot install it alongside libusb-0.1 on the same system. As the compatibility layer implements the exact same ABI and API, no modifications to existing libusb-0.1-based applications are needed. You do not even have to recompile them. This compatibility layer is a drop-in replacement.
2012-05-30 17:42:04 +02:00
(devel/libusb-compat) Using github raw files. (not src distribution)
2020-10-10 14:32:24 +02:00
VERSION= 0.1.7
DISTNAME= libusb-compat-${VERSION}
Initial import of libusb-compat-0.1.4. Notes: depends on libusbx (we need a switch between the two) Conflicts with libusb (we need a switch between the two) libusb-compat-0.1 is a replacement for libusb-0.1. However, instead of being an actual implementation, libusb-0.1 is more of a compatibility layer (or wrapper) which just converts libusb-0.1 calls into their libusb-1.0 equivalents. It aims to look, feel and behave exactly like libusb-0.1. As it is a replacement, you cannot install it alongside libusb-0.1 on the same system. As the compatibility layer implements the exact same ABI and API, no modifications to existing libusb-0.1-based applications are needed. You do not even have to recompile them. This compatibility layer is a drop-in replacement.
2012-05-30 17:42:04 +02:00
CATEGORIES= devel
Update devel/libusb-compat to version 0.1.6-rc2 (as 0.1.6rc2 here) From the ChangeLog: tag the 0.1.6-rc1 release Add -no-undefined to LDFLAGS Add some missing definitions Use C99 standard fixed width integer types in usb.h Prevent libusb-1.0 library symbol clash Add a library destructor to handle cleaning up libusb. Revert "Link with -znodelete to disallow unloading" Revert "use atexit() to call libusb_exit()" Link with -znodelete to disallow unloading Also changes the master site to GitHub. Tested on NetBSD/amd64. TODO: offer as an alternative to devel/libusb.
2017-12-16 23:53:15 +01:00
MASTER_SITES= ${MASTER_SITE_GITHUB:=libusb/}
libusb-compat: Use GITHUG_RELEASE instead of GITHUB_TAG pkgsrc changes: --------------- * Switch to release tarball to remove the dependency on autotools.
2020-10-08 13:54:44 +02:00
GITHUB_PROJECT= libusb-compat-0.1
(devel/libusb-compat) Using github raw files. (not src distribution)
2020-10-10 14:32:24 +02:00
GITHUB_RELEASE= v${VERSION}
Initial import of libusb-compat-0.1.4. Notes: depends on libusbx (we need a switch between the two) Conflicts with libusb (we need a switch between the two) libusb-compat-0.1 is a replacement for libusb-0.1. However, instead of being an actual implementation, libusb-0.1 is more of a compatibility layer (or wrapper) which just converts libusb-0.1 calls into their libusb-1.0 equivalents. It aims to look, feel and behave exactly like libusb-0.1. As it is a replacement, you cannot install it alongside libusb-0.1 on the same system. As the compatibility layer implements the exact same ABI and API, no modifications to existing libusb-0.1-based applications are needed. You do not even have to recompile them. This compatibility layer is a drop-in replacement.
2012-05-30 17:42:04 +02:00
MAINTAINER= pkgsrc-users@NetBSD.org
libusb-compat: update HOMEPAGE
2017-09-30 09:44:12 +02:00
HOMEPAGE= https://github.com/libusb/libusb/wiki
Initial import of libusb-compat-0.1.4. Notes: depends on libusbx (we need a switch between the two) Conflicts with libusb (we need a switch between the two) libusb-compat-0.1 is a replacement for libusb-0.1. However, instead of being an actual implementation, libusb-0.1 is more of a compatibility layer (or wrapper) which just converts libusb-0.1 calls into their libusb-1.0 equivalents. It aims to look, feel and behave exactly like libusb-0.1. As it is a replacement, you cannot install it alongside libusb-0.1 on the same system. As the compatibility layer implements the exact same ABI and API, no modifications to existing libusb-0.1-based applications are needed. You do not even have to recompile them. This compatibility layer is a drop-in replacement.
2012-05-30 17:42:04 +02:00
COMMENT= USB access library version 0 compatibility layer on top of version 1
LICENSE= gnu-lgpl-v2.1
libusb-compat: Add DIST_SUBDIR to avoid checksum error pkgsrc changes: --------------- * Use release archive from Github to avoid the dependency on autotools and to remove conflict with the tag archive potentially present in ${DISTDIR} which has the same name but a different checksum. * Reorder variables to be compliant with pkgsrc policy described in doc/Makefile-example.
2020-10-13 08:10:35 +02:00
CONFLICTS= libusb-[0-9]*
Initial import of libusb-compat-0.1.4. Notes: depends on libusbx (we need a switch between the two) Conflicts with libusb (we need a switch between the two) libusb-compat-0.1 is a replacement for libusb-0.1. However, instead of being an actual implementation, libusb-0.1 is more of a compatibility layer (or wrapper) which just converts libusb-0.1 calls into their libusb-1.0 equivalents. It aims to look, feel and behave exactly like libusb-0.1. As it is a replacement, you cannot install it alongside libusb-0.1 on the same system. As the compatibility layer implements the exact same ABI and API, no modifications to existing libusb-0.1-based applications are needed. You do not even have to recompile them. This compatibility layer is a drop-in replacement.
2012-05-30 17:42:04 +02:00
libusb-compat: Add DIST_SUBDIR to avoid checksum error pkgsrc changes: --------------- * Use release archive from Github to avoid the dependency on autotools and to remove conflict with the tag archive potentially present in ${DISTDIR} which has the same name but a different checksum. * Reorder variables to be compliant with pkgsrc policy described in doc/Makefile-example.
2020-10-13 08:10:35 +02:00
DIST_SUBDIR= ${PKGNAME_NOREV}
USE_LIBTOOL= yes
USE_TOOLS+= gsed pkg-config
GNU_CONFIGURE= yes
(devel/libusb-compat) Using github raw files. (not src distribution)
2020-10-10 14:32:24 +02:00
libusb-compat: Add DIST_SUBDIR to avoid checksum error pkgsrc changes: --------------- * Use release archive from Github to avoid the dependency on autotools and to remove conflict with the tag archive potentially present in ${DISTDIR} which has the same name but a different checksum. * Reorder variables to be compliant with pkgsrc policy described in doc/Makefile-example.
2020-10-13 08:10:35 +02:00
PKGCONFIG_OVERRIDE+= libusb.pc.in
Initial import of libusb-compat-0.1.4. Notes: depends on libusbx (we need a switch between the two) Conflicts with libusb (we need a switch between the two) libusb-compat-0.1 is a replacement for libusb-0.1. However, instead of being an actual implementation, libusb-0.1 is more of a compatibility layer (or wrapper) which just converts libusb-0.1 calls into their libusb-1.0 equivalents. It aims to look, feel and behave exactly like libusb-0.1. As it is a replacement, you cannot install it alongside libusb-0.1 on the same system. As the compatibility layer implements the exact same ABI and API, no modifications to existing libusb-0.1-based applications are needed. You do not even have to recompile them. This compatibility layer is a drop-in replacement.
2012-05-30 17:42:04 +02:00
Depend on libusb1. Requested by upstream maintainer, Peter Stuge. Bump PKGREVISION.
2012-05-31 13:58:12 +02:00
.include "../../devel/libusb1/buildlink3.mk"
Initial import of libusb-compat-0.1.4. Notes: depends on libusbx (we need a switch between the two) Conflicts with libusb (we need a switch between the two) libusb-compat-0.1 is a replacement for libusb-0.1. However, instead of being an actual implementation, libusb-0.1 is more of a compatibility layer (or wrapper) which just converts libusb-0.1 calls into their libusb-1.0 equivalents. It aims to look, feel and behave exactly like libusb-0.1. As it is a replacement, you cannot install it alongside libusb-0.1 on the same system. As the compatibility layer implements the exact same ABI and API, no modifications to existing libusb-0.1-based applications are needed. You do not even have to recompile them. This compatibility layer is a drop-in replacement.
2012-05-30 17:42:04 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink