Am Sonntag 24 Januar 2010 21:45:07 schrieb Alon Bar-Lev: > If it is imported from other place, why not just link against it?
what do you exactly propose? create a second noinst_ lib in common/ and link it in opensc/ the same way we include libcompat.a? fine with me. btw: what was the result of the library consolidation? we still need to export some internal functions from opensc for the tools/ applications. so we can reduce the libraries to two (libopensc and opensc-pkcs11.so), and limit each to a set of exported symbols, or create one library implementing both the internal interface for the tools/ and the pkcs#11 interface with a longer export list. these are the options I see. did I miss something? what do you prefer? for the implementation: we could simply make the libs we have so far "noinst_" libs, and then in pkcs15init/ directory create one huge lib with all parts (except pkcs#11), and link opensc-pkcs11 with that, or create the big lib in pkcs11/ directory (then containing all parts). in tool/ we will need to change the linking, so no "noinst" lib is referenced, but only the shared lib we want to install. haven't tested that, but it should work that way, I guess. Regards, Andreas _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
