Hello,
On Jan 24, 2011, at 6:13 PM, Douglas E. Engert wrote: > I agree with you on this, but there has not been much support for building > on Windows and it has been hard to find Windows developers and getting Visual > Studio installed is not easy. Alon and I had this discussion a few years ago. > Alon has had the time and energy to get the mingw with cross compiling > working. > In addition to building opensc, the build script also builds openvpn, openssl, > zlib, libp11, libconv, libtool and pkcs11-helper. True, Alon has done a great job, cross-compiling on Linux is a nice feature, which developers (like me) like. Yet it is IMHO wrong in the long from from platform integration point of view to take cross-compiling as the baseline. > As you point out, there are licencing issues, and if at least the cardmod > driver could be built on Windows these might be addressed. But it will take > some > work. See the e-mail about Hudson. Further down the road should come automated platform integration (Tokend, CSP) testing, which would be a nice thing but is not yet here. Or even near, I'm afraid. > An other interesting approach which we have not looked is to do what Mozilla > does. It uses a mingw environment for make, and other commands but uses the > Microsoft compiler and loader from Visual Studio. If you have tried to build Mozilla 5+ years ago and now, you probably have also seen that there has been great progress. But building Mozilla has never been a simple task and the probable reason for mingw this is (still) deep Unix heritage and dependencies. I've said it before - for Windows (or also other platforms) it does not matter which tools are used to build or package up the software, as long as it tries to integrate with the system in agreed way and as closely following platform best practices as possible. If the protocol is the same, then different options can be tried, but the "thin and native" tools should be preferred if possible for master builds. The interesting decision points for Windows builds are: building dependencies (zlib, openssl, libltdl), static building and 64 bit binaries. And integrating all that with the platform with a smooth installer. -- @MartinPaljak.net +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
