> 2012/4/17 Samuli Seppänen <sam...@openvpn.net>: >>> 2012/4/13 Samuli Seppänen <sam...@openvpn.net>: >>>> Hi all, >>>> >>>> I also ran some build tests with the "generic" buildsystem[1], OpenVPN >>>> Git "master"[2] and an Ubuntu 11.10 amd64 workstation. As the Git >>>> "master" does not yet seem to include the "generic" buildsystem, >>> I don't understand what you mean... please explain what is "include"...? >> Hi, >> >> It means I could not find "build" or "build.vars" from official >> openvpn.git. Are those not needed for cross-compilation? >> > There is some confusion.... :) > > We have two separate projects: > > openvpn - standard open source project, autotool based build system, > like any other project its build system only builds it-self. > > openvpn-build - a separate project to build openvpn in various of > configurations. This project is divided into the following components: I thought this might be the case, was not sure where the line was drawn.
> - generic - a generic build using cross compiler, included the > complete dependencies. > > - msvc - a MSVC build using Microsoft specific msbuild system, I hope > this will die eventually. Amen to that :). > - windows-nsis - the windows installer generator, it uses the generic > component to build using mingw cross compiler, then package the output > using nsis. > > The separation between these project is healthy as a change in openssl > version due to security issue at windows installer should not modify > openvpn version, same for a change in windows installer, or tap > version or any other change that is not directly related to openvpn > code base. > > It also allows a separate maintainer to maintain these various of > build environments. > > Does it answer your question? > > Alon Yes, thanks! -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
