Re: [Openvpn-devel] Windows build was messed up!

2010-09-20 Thread Samuli Seppänen
Hi David and Alon, > My suggestion is that we first move those parts related to the Windows > TAP driver, Windows installer and easy-rsa into separate git trees. > Next, the Windows building scripts needs to be split up, so that there's > a separate building process for Windows TAP driver and the O

Re: [Openvpn-devel] Windows build was messed up!

2010-09-20 Thread Samuli Seppänen
Hi David and Alon, > My suggestion is that we first move those parts related to the Windows > TAP driver, Windows installer and easy-rsa into separate git trees. > Next, the Windows building scripts needs to be split up, so that there's > a separate building process for Windows TAP driver and the O

Re: [Openvpn-devel] Windows build was messed up!

2010-09-19 Thread David Sommerseth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/09/10 21:32, Alon Bar-Lev wrote: > Look at the date Since ~2007 we are discussing modular. > It is so needed... :) > Better later than ever... Indeed ... I promise you I'll start a discussion here on the ML and on the the weekly meetings som

Re: [Openvpn-devel] Windows build was messed up!

2010-09-19 Thread Alon Bar-Lev
Look at the date Since ~2007 we are discussing modular. It is so needed... :) Better later than ever... -- Forwarded message -- From: Alon Bar-Lev List-Post: openvpn-devel@lists.sourceforge.net Date: Wed, Dec 27, 2006 at 8:20 PM Subject: Re: [openvpn] cross compile To: James Y

Re: [Openvpn-devel] Windows build was messed up!

2010-09-19 Thread David Sommerseth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13/09/10 21:15, Alon Bar-Lev wrote: > On Mon, Sep 13, 2010 at 8:25 PM, Peter Stuge wrote: >> autotools is absolutely alien in Windows, and to be honest a bit of a >> hassle to set up if you're already a VS wizard. > > In OpenVPN upstream provides

Re: [Openvpn-devel] Windows build was messed up!

2010-09-18 Thread Alon Bar-Lev
Samuli, Please peek this up. Thanks. On Mon, Sep 13, 2010 at 6:21 PM, Alon Bar-Lev wrote: > Hello, > > Does anyone know why the socklet_t detection was added this way? > > I mean the TYPE_SOCKLEN_T m4 macro. > > First, it should be sufficient to just try to see if socklen_t is defined. > Next, on

Re: [Openvpn-devel] Windows build was messed up!

2010-09-13 Thread Alon Bar-Lev
On Mon, Sep 13, 2010 at 9:29 PM, Toby Thain wrote: >>> NMAKE is convenient for Windows builds as it will also happily run >>> under Linux/WINE, targeting both 32 and 64 bit Windows runtimes with >>> the 'freely downloadable' Express toolchain. It may even be possible >>> to combine autotools with

Re: [Openvpn-devel] Windows build was messed up!

2010-09-13 Thread Toby Thain
On 13-Sep-10, at 3:14 PM, Peter Stuge wrote: Toby Thain wrote: So we have stuff for VC6, VS2005, VS2008, DDK/WDK, MinGW and Cygwin. :) I consider diversity of working build environments a net benefit to the project. It's another useful axis of portability and helps rub off non-portable burr

Re: [Openvpn-devel] Windows build was messed up!

2010-09-13 Thread Toby Thain
On 13-Sep-10, at 3:10 PM, Alon Bar-Lev wrote: On Mon, Sep 13, 2010 at 8:59 PM, Toby Thain wrote: NMAKE is convenient for Windows builds as it will also happily run under Linux/WINE, targeting both 32 and 64 bit Windows runtimes with the 'freely downloadable' Express toolchain. It may even be

Re: [Openvpn-devel] Windows build was messed up!

2010-09-13 Thread Alon Bar-Lev
On Mon, Sep 13, 2010 at 8:25 PM, Peter Stuge wrote: > autotools is absolutely alien in Windows, and to be honest a bit of a > hassle to set up if you're already a VS wizard. In OpenVPN upstream provides binaries using mingw anyway. So there is no need to support any other environment for Windows.

Re: [Openvpn-devel] Windows build was messed up!

2010-09-13 Thread Peter Stuge
Toby Thain wrote: > > So we have stuff for VC6, VS2005, VS2008, DDK/WDK, MinGW and Cygwin. :) > > I consider diversity of working build environments a net benefit to > the project. It's another useful axis of portability and helps rub > off non-portable burrs. I see your point and I agree in part

Re: [Openvpn-devel] Windows build was messed up!

2010-09-13 Thread Alon Bar-Lev
On Mon, Sep 13, 2010 at 8:59 PM, Toby Thain wrote: > NMAKE is convenient for Windows builds as it will also happily run > under Linux/WINE, targeting both 32 and 64 bit Windows runtimes with > the 'freely downloadable' Express toolchain. It may even be possible > to combine autotools with the Micr

Re: [Openvpn-devel] Windows build was messed up!

2010-09-13 Thread Toby Thain
On 13-Sep-10, at 2:25 PM, Peter Stuge wrote: Alon Bar-Lev wrote: The whole build environment of openvpn is malformed, using two separate build systems for windows and posix, Only two? Oh that's nothing. We're having lots of fun with build systems in libusb-1.0, where each contributing Window

Re: [Openvpn-devel] Windows build was messed up!

2010-09-13 Thread Peter Stuge
Alon Bar-Lev wrote: > The whole build environment of openvpn is malformed, using two > separate build systems for windows and posix, Only two? Oh that's nothing. We're having lots of fun with build systems in libusb-1.0, where each contributing Windows developer actually requires a separate build