To make it easier to test for none svn users, here are tarballs: http://alon.barlev.googlepages.com/libp11-0.2.3-svn.tar.gz http://alon.barlev.googlepages.com/engine_pkcs11-0.1.4-svn.tar.gz http://alon.barlev.googlepages.com/openct-0.6.14-svn.tar.gz
Alon. On 3/15/08, Alon Bar-Lev <[EMAIL PROTECTED]> wrote: > Hello, > > Need help in testing new build systems for libp11 [1], engine_pkcs11 > [2] and openct [3]. > > The build system is sync with latest work on OpenSC build system. Many > cleanups, and one step closer to complete mingw based Windows bundle. > > Changes: > 1. libp11 and engine_pkcs11 support mingw cross compile, binaries > available at [4], please notice that .dll extension should not be > specified when engine is loaded. > 2. Optional features disabled by default. > 3. API documentation are not generated at "make dist" but if user > specify --enable-api-doc. As a result user should have doxygen > installed. > 4. Many more cleanups. > > As usual..... I had no way to test Windows stuff... And I don't use > OpenCT... So I need people who use this stuff to check it out. > > Regards, > Alon Bar-Lev. > > [1] http://www.opensc-project.org/svn/libp11/branches/alonbl/mingw > [2] http://www.opensc-project.org/svn/engine_pkcs11/branches/alonbl/mingw > [3] http://www.opensc-project.org/svn/openct/branches/alonbl/build > [4] http://alon.barlev.googlepages.com/engine_pkcs11-mingw-bin.tar.bz2 > _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
