Hi, On Fri, Aug 20, 2010 at 05:35:36PM +0200, Peter Stuge wrote: > Samuli Seppänen wrote: > > converting the OpenVPN build system (on Windows) to depend only on > > python, Visual Studio Professional and DDK. The original build > > system required bash and various other UNIX tools. > > James' mentioned argument for prefering Visual Studio, namely that > MinGW may not have all the most recent functions in .h files, is not > so good IMO. Since James also seems to prefer working outside Windows > I would rather try to make OpenVPN for Windows crosscompileable, both > driver and app.
The app is cross-compileable today - but to make that work requires that
all relevant Windows APIs are exported in mingw headers *and libraries*.
Windows APIs have the nasty habit of changing over time, 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...
> 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...
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
pgpJA0tfGiNHg.pgp
Description: PGP signature
