wiki:SettingUpGenericBuildsystem

Introduction

You can use the generic buildsystem from openvpn-build subproject to cross-compile OpenVPN using any toolchain to any target environment. The build host must have a *NIX-like environment, e.g. Linux, *BSD or Cygwin (on Windows).

Generic instructions

You need to install a bunch of tools before attempting a build:

  • mingw-w64, version 2.0.x.
  • gcc-*-arm-linux-gnueabi (if building Arm binaries)
  • Git
  • man2html (for windows-nsis builds)
  • dos2unix (for windows-nsis builds)
  • NSIS: if you need support for riducuously long PATHs, you need to build NSIS yourself.
  • osslsigncode version 1.4 or later (pkcs12 support needed). Earlier versions can be used with minor modifications to the codesign() method in the build scripts.

Converting certificates to PKCS12 format

If you have code-signing certificates generated with MS tools (.spc and .pvk files), you can convert them into standard (pkcs12) format using this script. If that fails, look at this old version of this page for manual instructions.

You can also create self-signed certificate for testing like this:

$ openssl req -newkey rsa:1024 -new -x509 -subj "/CN=test1" -out test.crt	
$ openssl pkcs12 -export -inkey privkey.pem -in test.crt -out test.p12	

Once you have the pkcs12 archive, you can give it and it's password as argument to the buildsystem(s). For details, look here:

Automated openvpn-build setup on Ubuntu

Please use this shell script. It has been tested and should work on 64-bit flavors of Ubuntu 12.04, 12.10 and 14.04. Please let us know if the script does not work for you. Manual setup instruction can be deduced from the script.

Setup on Windows

If you're building using Cygwin on Windows, it's best to configure Git not to translate LF to CR/LF. For this reason it's probably best to use Cygwin's Git. Also take a look at Cygwin's README to see which packages are required.

Last modified 5 months ago Last modified on 10/22/14 08:44:45

Attachments (3)

Download all attachments as: .zip