Hi, On Fri, Aug 20, 2010 at 06:24:06PM +0200, Peter Stuge wrote: > Gert Doering wrote: > > The app is cross-compileable today - but to make that work requires that > > all relevant Windows APIs are exported in mingw headers *and libraries*. > > Sure. You emphasize libraries, but MinGW is not so much a library as > it is a wrapper for the standard runtime from MS. [..] > > so if mingw stops updating their libraries etc., OpenVPN would be > > sort of stuck to the old APIs - which might turn into a problem. > > Or might not. We don't know... > > What could happen is that OpenVPN wants to use a brand new API which > was introduced in e.g. Windows 7, and if MinGW doesn't yet support > this, then it can't be used.
Yes, this was what I understood James to be worried about. > First of all, I'm not sure that will happen, since we want OpenVPN to > be backwards compatible for older Windows systems too. It might be necessary if "the API that we currently use" stops working on Win8 or so... (and yes, that would require different #ifdef branches for "old windows" and "new windows" - nasty, but sometimes unavoidable) > But if it really is neccessary, then maybe that API can be added to > MinGW with very little effort, since MinGW is just a wrapper. Now that's good news. I had the assumption that they are basically providing "re-engineered" versions of the windows libraries etc. (as WINE does for the runtime environment). That would have been much more work. > > > libusb-win32 can already compile their driver using MinGW. > > > > To be able to cross-compile the driver would certainly be nice. > > Need to check how libusb-win32 does this... > > They've switched to depending on the WDK (supercedes the DDK) out of > preference and stopped supporting MinGW builds. Rev 212 from May is > the last that cross-compiles without problems. > > svn co -r 212 > https://libusb-win32.svn.sourceforge.net/svnroot/libusb-win32/trunk/libusb > libusb-win32 > cd libusb-win32/ > make host_prefix=i686-mingw32 libusb0.sys > > (You may need another prefix.) Will check this out - not that I have any realy understanding how windows device driver building really works, but I've done "build tap with WDK" (because you can't download DDK any longer), so maybe it's enough to put the pieces togehter. thanks, gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgpiZ6LsFKYM8.pgp
Description: PGP signature
