Hello, This was supported once, then reverted (I don't know why). I agree it is better to have this on $(libdir)/pkcs11, but why not putting there the library itself?
Also please note that you need to use $(DESTDIR)$(libdir)/pkcs11 so that libdir will be available also to 64bit. So you need something like: At configure.in: pkcs11dir="\$(libdir)/pkcs11" AC_SUBST([pkcs11dir]) At Makefile.am: pkcs11_DATA=#This will create the directory install-data-hook: $(LN_S) ../opensc-pkcs11.so $(DESTDIR)$(pkcs11dir)/opensc-pkcs11.so But I think it is better to put the library there in the first place. Alon. On 11/8/07, Ludovic Rousseau <[EMAIL PROTECTED]> wrote: > Hello, > > I propose to support the scheme described at > http://wiki.cacert.org/wiki/Pkcs11TaskForce > > I propose the patch: > Index: src/pkcs11/Makefile.am > =================================================================== > --- src/pkcs11/Makefile.am (révision 3290) > +++ src/pkcs11/Makefile.am (copie de travail) > @@ -45,3 +45,8 @@ pkcs11-jar: jar-dir > cp opensc_pkcs11_install.js jar-dir > signtool -Z"opensc-pkcs11.jar" -i"opensc_pkcs11_install.js" \ > -k"testcert" jar-dir > + > +# see http://wiki.cacert.org/wiki/Pkcs11TaskForce > +install-exec-hook: > + mkdir -p $(DESTDIR)/$(prefix)/lib/pkcs11 > + cd $(DESTDIR)/$(prefix)/lib/pkcs11 ; ln -sf ../opensc-pkcs11.so > > > One problem of my patch is that opensc-pkcs11.so is named > opensc-pkcs11.dylib under Mac OS X. I will add support of Mac OS X if > the idea of using /usr/lib/pkcs11/ is accepted. > > Any comment or objection? > > bye > > -- > Dr. Ludovic Rousseau > _______________________________________________ > opensc-devel mailing list > opensc-devel@lists.opensc-project.org > http://www.opensc-project.org/mailman/listinfo/opensc-devel > _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
