Jean-Michel Pouré - GOOZE wrote: > > > I would like to advance on the Windows part of OpenSC 0.12svn. > > Go for it! That would be great! > > How about OpenSSL? I found this link on the OpenSSL website: > http://www.slproweb.com/products/Win32OpenSSL.html
Ok - see if you can reuse some part of their installer. I think you should indeed replace it, not use it as a whole. > What extra packages should be installed except OpenSC? Dunno. Start simple.. > I have little knowledge in Windows compilers and development > environments. But I will give a try. > > Could you point out some documentation and/or GUI explaining how to > cross compile? No GUI, don't know much documentation either. Start testing. Test simple stuff first. Get a cross-compiler toolchain. On Gentoo it's trivial: emerge crossdev crossdev -t i686-w64-mingw32 crossdev -t x86_64-w64-mingw32 And you'll have a 32-bit and a 64-bit cross-toolchain for Windows. Then, for any autotools package, you build it using: ./configure --host=x86_64-w64-mingw32 Make sure to also set a prefix - you do *not* want these binaries mixed with your regular system. > I am not sure that we can cross-compile, as some > libraries like OpenSSL may be installed separately. Assume that they are not there and build and include all dependencines. Don't install anything to system folders is what I would start out with. Maybe something will need to be there, but start testing without. Jean-Michel Pouré - GOOZE wrote: > I plan to use Cygwin. Any comments? That's a bad idea. Cygwin is absolutely not Windows. Cygwin must be considered a distinct system, a POSIX environment that happens to run on top of Windows. Use MinGW. //Peter _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
