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. > Windows APIs have the nasty habit of changing over time, I know this. I also do win32 development. With MinGW. > 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. First of all, I'm not sure that will happen, since we want OpenVPN to be backwards compatible for older Windows systems too. 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. > > 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.) //Peter
pgpeXM8YX8UgX.pgp
Description: PGP signature
