Re: [Openvpn-devel] [build] Windows build test

That does it - it works now, thanks!!! ... Russell On Sat, 02/25/2012 12:58 PM, Alon Bar-Lev wrote: > Never mind. > I guess that mingw is configured as multilib somehow. > I forced all to use /lib. > Can you please try again? > > On Sat, Feb 25, 2012 at 7:28 PM, Alon Bar-Lev wrote:

Re: [Openvpn-devel] [build] Windows build test

Never mind. I guess that mingw is configured as multilib somehow. I forced all to use /lib. Can you please try again? On Sat, Feb 25, 2012 at 7:28 PM, Alon Bar-Lev wrote: > Can you send me list: > $ find image-win32/openvpn/lib > $ find image-win32/openvpn/lib64 > > > On Sat, Feb 25, 2012 at 4:22

Re: [Openvpn-devel] [build] Windows build test

Can you send me list: $ find image-win32/openvpn/lib $ find image-win32/openvpn/lib64 On Sat, Feb 25, 2012 at 4:22 PM, Russell Morris wrote: > Hi, > > OK, I have done some digging - and I know what the issue is! Not sure how to > fix it though ... :-). > > Inside the image-win64 directory, and t

Re: [Openvpn-devel] [build] Windows build test

Hi, OK, I have done some digging - and I know what the issue is! Not sure how to fix it though ... :-). Inside the image-win64 directory, and then inside openvpn - running the build script results in two directories, lib and lib64 (for image-win32 there is only the lib directory). The librarie

Re: [Openvpn-devel] [build] Windows build test

And also full output of the build script... . 2>&1 | gzip > /tmp/build.log On Sat, Feb 25, 2012 at 11:14 AM, Alon Bar-Lev wrote: > I need the tmp/openvpn*/config.log > > On Sat, Feb 25, 2012 at 7:12 AM, Russell Morris wrote: >> Hi, >> >> I used the command line you provided below (actually,

Re: [Openvpn-devel] [build] Windows build test

I need the tmp/openvpn*/config.log On Sat, Feb 25, 2012 at 7:12 AM, Russell Morris wrote: > Hi, > > I used the command line you provided below (actually, copied and pasted it > to the command line). The one having issues is: IMAGEROOT=`pwd`/image-win64 > CHOST=x86_64-w64-mingw32 CBUILD=x86_64-pc-

Re: [Openvpn-devel] [build] Windows build test

Hi, I used the command line you provided below (actually, copied and pasted it to the command line). The one having issues is: IMAGEROOT=`pwd`/image-win64 CHOST=x86_64-w64-mingw32 CBUILD=x86_64-pc-linux-gnu ./build Thanks! ... Russell On Fri, 02/24/2012 06:11 PM, Alon Bar-Lev wrote: > How e

Re: [Openvpn-devel] [build] Windows build test

How exactly did you try to build? Please send command-line. The mingw32 suffix is historic, it is kept for compatibility as old autotools(config.guess) packages expects for mingw32 as a platform, in the old days there was no (forced) standard for specifying the arch. On Sat, Feb 25, 2012 at 2:04

Re: [Openvpn-devel] [build] Windows build test

> 2012/2/24 Samuli Seppänen : >> Actually, I cloned the "openvpn-build" Git repository and copied the >> directories from there on top OpenVPN sources (yours and official). That >> said, I tried the tarball, too: >> >> >> >> I

Re: [Openvpn-devel] [build] Windows build test

2012/2/24 Samuli Seppänen : > Actually, I cloned the "openvpn-build" Git repository and copied the > directories from there on top OpenVPN sources (yours and official). That > said, I tried the tarball, too: > > > > I documente

Re: [Openvpn-devel] [build] Windows build test

> 2012/2/24 Samuli Seppänen : >> Hi Alon, >> >> I tried building OpenVPN using the "Visual Studio Complete Batch" method: >> >> $ cd msvc >> $ build >> >> All went fine until OpenVPN build itself. The error message is here: >> >> > Oh... you used the tarball and I fo

Re: [Openvpn-devel] [build] Windows build test

> Hello people who actually use Windows! > > I will appreciate if you test my new windows build environment for OpenVPN. > > > Visual Studio Complete Batch > > install perl > >> cd msvc >> build > Visual Studio IDE > > After you have the dependencies of Complete Batch or your own. > Create msvc-en

Re: [Openvpn-devel] [build] Windows build test

On Wed, Feb 22, 2012 at 12:36 PM, Heiko Hund wrote: > On Wednesday 22 February 2012 10:32:23 Alon Bar-Lev wrote: >> On Wed, Feb 22, 2012 at 12:27 PM, Heiko Hund wrote: >> > I was cross compiling for Windows previously doing something very >> > standard >> > like `./configure --host=i686-w64-mingw

Re: [Openvpn-devel] [build] Windows build test

On Wednesday 22 February 2012 10:32:23 Alon Bar-Lev wrote: > On Wed, Feb 22, 2012 at 12:27 PM, Heiko Hund wrote: > > I was cross compiling for Windows previously doing something very > > standard > > like `./configure --host=i686-w64-mingw32 ...` followed by `make`. What > > the rationale behind m

Re: [Openvpn-devel] [build] Windows build test

BTW: cross compile support was added by me to OpenVPN long time ago. It is just that I've done the minimum required changes back-then. I needed this for OpenSC users, to be able to compile OpenSC and OpenVPN with the same version of OpenSSL. On Wed, Feb 22, 2012 at 12:32 PM, Alon Bar-Lev wrote: >

Re: [Openvpn-devel] [build] Windows build test

On Wed, Feb 22, 2012 at 12:27 PM, Heiko Hund wrote: > I was cross compiling for Windows previously doing something very standard > like `./configure --host=i686-w64-mingw32 ...` followed by `make`. What the > rationale behind moving away from this way? This is exactly what this build is doing. Ju

Re: [Openvpn-devel] [build] Windows build test

On Wednesday 22 February 2012 00:12:25 Alon Bar-Lev wrote: > BEST METHOD - Compile on Linux > > This is a generic method, it can cross compile OpenVPN using any > toolchain to any environment. > For Windows, make sure you have mingw-w64 toolchain. > We are using nsis so we can also package files a

Re: [Openvpn-devel] [build] Windows build test

2012/2/22 Samuli Seppänen : > I used this method to cross-compile for Windows (32-bit and 64-bit) on > Ubuntu 11.10 amd64. I replaced the "bin" directory of an existing > openvpn-2.3-alpha1 installation with the results on a 32-bit WinXP box > and it seemed work ok. Thank you for testing! > > Any

Re: [Openvpn-devel] [build] Windows build test

Hi, On Wed, Feb 22, 2012 at 10:57:43AM +0200, Alon Bar-Lev wrote: > > On Wed, Feb 22, 2012 at 10:04:51AM +0200, Samuli Seppänen wrote: > >> > While you at it, please try to explain me why we need Visual Studio > >> > build... :) [..] > > We have Visual Studio because James was afraid that mingw w

Re: [Openvpn-devel] [build] Windows build test

>> . >> Build is here[1] >> >> BEST METHOD - Compile on Linux >> >> This is a generic method, it can cross compile OpenVPN using any >> toolchain to any environment. >> For Windows, make sure you have mingw-w64 toolchain. >> We are using nsis so we can also package files at Linux. >> >> $ cd gener

Re: [Openvpn-devel] [build] Windows build test

2012/2/22 Gert Doering : > Hi, > > On Wed, Feb 22, 2012 at 10:04:51AM +0200, Samuli Seppänen wrote: >> > While you at it, please try to explain me why we need Visual Studio >> > build... :) >> I guess for building the TAP-driver. > > No, that one builds fine with the msys build environment and the

Re: [Openvpn-devel] [build] Windows build test

Hi, On Wed, Feb 22, 2012 at 10:04:51AM +0200, Samuli Seppänen wrote: > > While you at it, please try to explain me why we need Visual Studio > > build... :) > I guess for building the TAP-driver. No, that one builds fine with the msys build environment and the windows ddk. We have Visual Studi

Re: [Openvpn-devel] [build] Windows build test

Hi Alon, > Hello people who actually use Windows! > > I will appreciate if you test my new windows build environment for OpenVPN. I'll test this today. > You have many options, I guess all are needed. > > While you at it, please try to explain me why we need Visual Studio build... > :) I guess fo

[Openvpn-devel] [build] Windows build test

Hello people who actually use Windows! I will appreciate if you test my new windows build environment for OpenVPN. You have many options, I guess all are needed. While you at it, please try to explain me why we need Visual Studio build... :) . Build is here[1] BEST METHOD - Compile on Linux T