Hi,
I installed SCB-0.7 from the homepage and updated the contained opensc
library to the current SVN by compiling opensc on my own using VC++ 8.
Everything went fine, until I tried to use opensc-pkcs11.dll from within
JAVA, which did not work.
After several hours banging my head against a wall, I recognized, that JAVA
was loading the old version of opensc.dll, which has been installed by the
SCB installer to C:\WINDOWS\System32
After deleting the opensc-dlls from C:\WINDOWS\System32, everything went
smooth, openssl and JAVA now use the new opensc version flawlessly.
So I have the following remarks/questions to the SCB installation:
1) Are there any good reasons to install the opensc dlls twice? (SCB install
directory and C:\WINDOWS\System32) Installing then only in the SCB install
directory should be IMHO sufficient, because all dlls on which the opensc
libs depeand are installed alongside in the same directory, so they are
resolved anyways.
2) The MSVC 7.1 compiler used to compile the binary distribution of SCB
creates dependencies on msvcr71.dll, which is *not* layer atop the more
frequently used msvcrt.dll originating from msvc6.
msvcrt.dll shipped together with Win2K/WinXP and used by a bunch of libraries
out there. Therefore, it would be more feasible to use either mingw (is this
fully supported by now?) or at least msvc8 to build the binary SCB
distribution. The build notes on the opensc WIKI lead the user to the Visual
Studio express download, which contains msvc8. The msvc8 CRT library,
msvcr80.dll corrects the redundant installation of multiple CRT dlls, by
*extending* the functionality of msvcrt.dll instead of replacing it.
Best regards,
Wolfgang
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
