Hi everyone, Just to give an update, compilation on Alon's generic/ fails when it tries to compile openvpn with messages like:
In file included from base64.c:40:0: syshead.h:345:22: fatal error: ntddndis.h: No such file or directory etc. ntddndis.h can be found in several places i.e. /usr/include/w32api/ddk, but including that path manually results in duplicate definitions and the build brakes again. Besides, I'm not sure including the path manually is the right thing to do. Ref: also my message from the 9th of March, where I had a similar problem in a completely different build environment in different builder system. And this has occurred with 2.3alpha1, not before. Cheers, Athanasios On Thu, Mar 15, 2012 at 1:39 AM, Alon Bar-Lev <alon.bar...@gmail.com> wrote: > Next step is for you to create an installer :) > Use the windows-nsis scripts. > > On Thu, Mar 15, 2012 at 1:37 AM, Athanasios Douitsis <aduit...@gmail.com> > wrote: > > > > > > On Thu, Mar 15, 2012 at 1:19 AM, Alon Bar-Lev <alon.bar...@gmail.com> > wrote: > >> > >> On Thu, Mar 15, 2012 at 1:05 AM, Athanasios Douitsis < > aduit...@gmail.com> > >> wrote: > >> > I was just thinking loudly, definitely not asking for someone to write > >> > it > >> > and replace the existing build process(es). Having said that, I'd like > >> > to > >> > clarify that what I meant is this would not be an additional > dependency > >> > on > >> > top of others, since neither cygwin nor msvc would be needed anymore. > >> > Anyway, not important, just a thought. > >> > >> Visual studio build is for compatibility for people who insist of using > >> it. > >> > >> The "generic" build system is pure cross compile / native build system > >> for dependencies and openvpn. It compiles openvpn using a given > >> toolchain to any environment. > >> > >> For example, you can use it to compile at Linux for Linux on power pc > >> or to Linux on arm. > >> As a side effect you can also compile openvpn on Linux to windows using > >> mingw. > >> This exact same script without any modification can be used on Windows > >> in cygwin environment to cross compile to windows native. > >> > >> So at the larger picture the target is to maintain a single build > >> system for all environment... same dependencies, same utilities. > >> > >> Alon > > > > > > Thanks for taking the time to explain! I'll be happy to provide as much > > feedback as possible on the windows native case with cygwin. > > > > Best regards, > > -- > > Athanasios Douitsis > > > > > > > -- Athanasios Douitsis
