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

26 lines
696 B
Makefile
Raw Normal View History

libusb-compat: update HOMEPAGE
2017-09-30 09:44:12 +02:00
# $NetBSD: Makefile,v 1.6 2017/09/30 07:44:12 wiz 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
update 0.1.4 to 0.1.5 --------------------- Date: Mon May 20 17:34:02 2013 -0600 libusb-compat-0.1.5 Date: Mon May 20 17:33:43 2013 -0600 Add bootstrap.sh and do not set debug mode by default. Date: Mon May 20 17:32:43 2013 -0600 Replace the deprecated INCLUDES token with AM_CPPFLAGS in Makefile.am Date: Fri Aug 24 17:13:11 2012 -0400 libusb.pc.in: Add missing Requires.private: libusb-1.0 so that pkg-config adds the libusb 1.0 library and dependencies when static linking. Date: Thu Apr 4 10:53:42 2013 -0600 use atexit() to call libusb_exit() Fixes #130 Date: Thu Apr 4 10:53:01 2013 -0600 fix autoconf errors/warnings Fixes #161 Date: Sun May 13 19:50:38 2012 +0800 examples: Link only with ../libusb/libusb.la and not with -lusb Similar to libusb.git commit 93b0e09d53ed1d177631af9182378492481a790a http://git.libusb.org/?p=libusb.git;a=commitdiff;h=93b0e09d53ed1d177631af918 Previous _LDFLAGS included both the freshly built libusb in ../libusb and -lusb, where libtool would usually resolve the latter to an already-installed libusb library in the system. The extra reference to a second libusb library may cause failures to build examples on some platforms and is wrong. Fixes #135.
2014-11-24 13:53:19 +01:00
DISTNAME= libusb-compat-0.1.5
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
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=libusb/libusb-compat-0.1/}
EXTRACT_SUFX= .tar.bz2
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
USE_LIBTOOL= yes
USE_TOOLS+= pkg-config
GNU_CONFIGURE= yes
PKGCONFIG_OVERRIDE+= libusb.pc.in
use POSIX typedefs for u_int*_t on SunOS
2016-03-26 08:53:32 +01:00
CPPFLAGS.SunOS+= -Du_int8_t=uint8_t
CPPFLAGS.SunOS+= -Du_int16_t=uint16_t
CPPFLAGS.SunOS+= -Du_int32_t=uint32_t
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
CONFLICTS= libusb-[0-9]*
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