On Mar 3, 2010, at 12:08 , Andreas Jellinghaus wrote: > Am Mittwoch 03 März 2010 08:46:27 schrieb Martin Paljak: >> Tokend still requires access to libopensc headers, having it in a standard >> place (/Library/OpenSC/include) would ease the building of it, as it would >> not require any changes in xcode buildfiles before it can be built. Not >> sure if/how it could be automated and changed to pick up headers from a >> custom location. > > what happened to the idea of merging it into opensc? > the cm is also part of opensc source, and at least I don't mind > keeping these components in opensc source code, would even favor > it, as they are closely tied to opensc. Tokend source code comes with a burden of extra pieces required to build it (like the libtoken itself, which is very macosx tokend specific).
There's the option of adding the source to the same svn repository but there's no point in distributing it with the tarball. Building it requires extra preparations that is not available via ./configure/make/make install. Also, the licensing of the whole tokend thing is unclear as everything else that relates to apple. -- Martin Paljak http://martin.paljak.pri.ee +3725156495 _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
