Alon Bar-Lev wrote: > Hello All, > > It all started as result of OpenSSL incompatibility between an > application and OpenSC PKCS#11 provider. > > I quickly learned that OpenSC is built for Windows only using > Microsoft compiler. > > Requiring Microsoft compile for free software is somewhat strange... :)
Why? Using the vendor's compiler is common on many platforms, especially if your code is in the kernel, or is security related, like OpenSC and runs with operating system privileges. If its the cost of the compiler that is an issue, have you looked at the free Visual Studio Express? http://msdn2.microsoft.com/en-us/vstudio/products/bb933731.aspx For XP and Vista, it would also be wise for OpenSC to start using Manifests to make OpenSC more compatible, as it is security related code. http://msdn2.microsoft.com/en-us/library/ms235532.aspx > > Also, it required OpenSC developers to implement and maintain two > separate build systems, one for all other operating systems and one > specific for Microsoft. > > It took some effort, but at the end I have a test release that uses a > single autoconf/automake/libtool build system for all operating > systems. > > The problem is that I do not use OpenSC (yet) and I also do not use > Windows... :) I can confirm that it sane... It detects readers and > loads the provider... But I cannot do more than this. > > So if you are a Windows user, I need some help! > None Windows users are also appreciated, as the build system had gone > a major change. > > Windows binaries are available at [1], source tarball is available at [2]. > > In order to do this modification, I had to clean up the current OpenSC > build, this is available at the first revision of my trunk [3]. Other > revisions are grouped by the level of complexity. > > Major Changes: > 1. Cleanup current build system, (Andreas, I hope you will not be > completely mad). All optional components are disabled now by default, > use --enable-X to enable them if required. > 2. Make build system support mingw. > 3. pcsc driver is loaded dynamically. This method works the same on > Linux and Windows. It should be tested on other platforms. > 4. Initial cygwin support (not tested). > 5. No version and other resources for DLLs and EXEs, it may be added > in future if important. > > I believe the modified build system is much cleaner, and it is worth > the efforts to detect the issues I missed and fix them using this as > base. > > Any comments/recommendations will be appreciated. > > Best Regards, > Alon Bar-Lev. > > [1] http://alon.barlev.googlepages.com/opensc-trunk-mingw32-001.tar.bz2 > [2] http://alon.barlev.googlepages.com/opensc-0.11.4-svn.tar.gz > [3] http://www.opensc-project.org/opensc/browser/branches/alonbl/mingw > _______________________________________________ > opensc-devel mailing list > opensc-devel@lists.opensc-project.org > http://www.opensc-project.org/mailman/listinfo/opensc-devel > > -- Douglas E. Engert <[EMAIL PROTECTED]> Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
