On Sun, Sep 20, 2009 at 6:25 PM, Martin Paljak <mar...@paljak.pri.ee> wrote: > > not sure if the changes we have so far break ABI. but if we break ABI, > > then I favor to merge libopensc, libpkcs15init and opensc-pcks11.so > > into one library / shared object. > > Hmm, that is an interesting idea. It would also have to include scconf > which currently is distributed separately, but then again is also used > by other software like pam_pkcs11 for example. > > Alon, what do you think of it (from the build system POV) and do you > think you have the interest and time to work on it?
First, I like the modulation. It is much simpler to maintain modulated piece of software. Second, it is a very bad idea to provide a PKCS#11 library with none PKCS#11 exports. opensc-pkcs11.so should export only PKCS#11 symbols, maybe one more to do some vendor specific stuff. There are vendors which does exactly this, hence all their tools use PKCS#11 interface. OpenSC utilities are not such, so I don't think it is wise to do so until they do. Merging between libopensc and libpkcs15init is making sense, but what the benefit will be? Anyway two options: 1. Make the libpkcs15init internal library (.a) it will not be distributed, but linked against executables. 2. Merge libopensc and libpkcs15init into a single library. Alon. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
