kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/security/pakchois/Makefile

30 lines
784 B
Makefile
Raw Normal View History

all: migrate homepages from http to https pkglint -r --network --only "migrate" As a side-effect of migrating the homepages, pkglint also fixed a few indentations in unrelated lines. These and the new homepages have been checked manually.
2020-01-26 18:30:40 +01:00
# $NetBSD: Makefile,v 1.7 2020/01/26 17:32:06 rillig Exp $
Add pakchois-0.4. (upcoming new neon can use it) -- pakchois is just another PKCS#11 wrapper library. pakchois aims to provide a thin wrapper over the PKCS#11 interface. The goals are: 1) to offer a modern* object-oriented C interface wrapper for PKCS#11. 2) to not hide or abstract away any details of the PKCS#11 interface itself except where absolutely necessary. 3) to handle the details of loading DSOs 4) to allow the caller to avoid caring about where on the system PKCS#11 modules might be stored, or exactly how they are named. 5) to avoid any dependency on a particular cryptography toolkit. Existing PKCS#11 wrapper libraries solutions differ in at least one of the above goals. *: "modern" being a euphemism for not using process-global state, having a sane symbol namespace, etc.
2008-10-30 04:32:19 +01:00
#
DISTNAME= pakchois-0.4
recursive bump from gettext-lib shlib bump.
2011-04-22 15:41:54 +02:00
PKGREVISION= 1
Add pakchois-0.4. (upcoming new neon can use it) -- pakchois is just another PKCS#11 wrapper library. pakchois aims to provide a thin wrapper over the PKCS#11 interface. The goals are: 1) to offer a modern* object-oriented C interface wrapper for PKCS#11. 2) to not hide or abstract away any details of the PKCS#11 interface itself except where absolutely necessary. 3) to handle the details of loading DSOs 4) to allow the caller to avoid caring about where on the system PKCS#11 modules might be stored, or exactly how they are named. 5) to avoid any dependency on a particular cryptography toolkit. Existing PKCS#11 wrapper libraries solutions differ in at least one of the above goals. *: "modern" being a euphemism for not using process-global state, having a sane symbol namespace, etc.
2008-10-30 04:32:19 +01:00
CATEGORIES= security
MASTER_SITES= http://www.manyfish.co.uk/pakchois/
MAINTAINER= pkgsrc-users@NetBSD.org
all: migrate homepages from http to https pkglint -r --network --only "migrate" As a side-effect of migrating the homepages, pkglint also fixed a few indentations in unrelated lines. These and the new homepages have been checked manually.
2020-01-26 18:30:40 +01:00
HOMEPAGE= https://www.manyfish.co.uk/pakchois/
Be consistent in the way we quote the '#' character
2011-03-31 20:37:33 +02:00
COMMENT= PKCS\#11 wrapper library
Add pakchois-0.4. (upcoming new neon can use it) -- pakchois is just another PKCS#11 wrapper library. pakchois aims to provide a thin wrapper over the PKCS#11 interface. The goals are: 1) to offer a modern* object-oriented C interface wrapper for PKCS#11. 2) to not hide or abstract away any details of the PKCS#11 interface itself except where absolutely necessary. 3) to handle the details of loading DSOs 4) to allow the caller to avoid caring about where on the system PKCS#11 modules might be stored, or exactly how they are named. 5) to avoid any dependency on a particular cryptography toolkit. Existing PKCS#11 wrapper libraries solutions differ in at least one of the above goals. *: "modern" being a euphemism for not using process-global state, having a sane symbol namespace, etc.
2008-10-30 04:32:19 +01:00
GNU_CONFIGURE= yes
USE_LIBTOOL= yes
USE_TOOLS+= gmake pkg-config
PKGCONFIG_OVERRIDE+= pakchois.pc.in
PTHREAD_OPTS+= require
PKG_PTHREAD_FLAGS= ${PTHREAD_LDFLAGS} ${PTHREAD_LIBS}
BROKEN_GETTEXT_DETECTION= yes
security: align variable assignments pkglint -Wall -F --only aligned --only indent -r No manual corrections.
2019-11-04 22:12:51 +01:00
BUILDLINK_TRANSFORM+= opt:-ldl:${BUILDLINK_LDADD.dl:M*}
BUILDLINK_TRANSFORM+= opt:-lpthread:${PKG_PTHREAD_FLAGS:M*}
Add pakchois-0.4. (upcoming new neon can use it) -- pakchois is just another PKCS#11 wrapper library. pakchois aims to provide a thin wrapper over the PKCS#11 interface. The goals are: 1) to offer a modern* object-oriented C interface wrapper for PKCS#11. 2) to not hide or abstract away any details of the PKCS#11 interface itself except where absolutely necessary. 3) to handle the details of loading DSOs 4) to allow the caller to avoid caring about where on the system PKCS#11 modules might be stored, or exactly how they are named. 5) to avoid any dependency on a particular cryptography toolkit. Existing PKCS#11 wrapper libraries solutions differ in at least one of the above goals. *: "modern" being a euphemism for not using process-global state, having a sane symbol namespace, etc.
2008-10-30 04:32:19 +01:00
.include "../../devel/gettext-lib/buildlink3.mk"
.include "../../mk/dlopen.buildlink3.mk"
.include "../../mk/pthread.buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink