distribution. Therefore, this howto deals with cross-compiling tinc with MinGW
under Linux on a Debian distribution.
+The result is a 32-bit executable. If you want to create a 64-bit executable,
+have a look at the [[64-bit cross-compilation example|examples/cross-compiling-64-bit-windows-binary]].
+
### Overview
The idea is simple:
There are only a few packages that need to be installed as root to get started:
-> sudo apt-get install mingw32 wine git-core
-> sudo apt-get build-dep tinc
+ sudo apt-get install mingw-w64 wine git-core quilt
+ sudo apt-get build-dep tinc
Other Linux distributions may also have MinGW packages, use their respective
package management tools to install them. Debian installs the cross-compiler
-in `/usr/i586-mingw32msvc/`. Other distributions might install it in another
+in `/usr/i686-w64-mingw32/`. Other distributions might install it in another
directory however, for example `/usr/i686-pc-mingw32/`. Check in which directory
-it is installed, and replace all occurences of `i586-mingw32msvc` in this
+it is installed, and replace all occurences of `i686-w64-mingw32` in this
example with the correct name from your distribution.
### Setting up the build directory and getting the sources
apt-get to get the required libraries necessary for tinc, and use `git` to get
the latest development version of tinc.
-> mkdir $HOME/mingw
-> cd $HOME/mingw
-> apt-get source openssl liblzo2-dev zlib1g-dev
-> git clone git://tinc-vpn.org/tinc
+ mkdir $HOME/mingw
+ cd $HOME/mingw
+ apt-get source openssl liblzo2-dev zlib1g-dev
+ git clone https://tinc-vpn.org/git/tinc
### Making cross-compilation easy
up the necessary environment variables so configure scripts and Makefiles will
use the MinGW version of GCC and binutils:
-> mkdir $HOME/bin
-> cat >$HOME/bin/mingw << EOF
-> #!/bin/sh
-> export CC=i586-mingw32msvc-gcc
-> export CXX=i586-mingw32msvc-g++
-> export CPP=i586-mingw32msvc-cpp
-> export RANLIB=i586-mingw32msvc-ranlib
-> export PATH="/usr/i586-mingw32msvc/bin:$PATH"
-> exec "$@"
-> EOF
+ mkdir $HOME/bin
+ cat >$HOME/bin/mingw << 'EOF'
+ #!/bin/sh
+ PREFIX=i686-w64-mingw32
+ export CC=$PREFIX-gcc
+ export CXX=$PREFIX-g++
+ export CPP=$PREFIX-cpp
+ export RANLIB=$PREFIX-ranlib
+ export PATH="/usr/$PREFIX/bin:$PATH"
+ exec "$@"
+ EOF
+ chmod u+x $HOME/bin/mingw
If `$HOME/bin` is not already part of your `$PATH`, you need to add it:
-> export PATH="$HOME/bin:$PATH"
+ export PATH="$HOME/bin:$PATH"
We use this script to call `./configure` and `make` with the right environment
variables, but only when the `./configure` script doesn't support cross-compilation itself.
Cross-compiling LZO is easy:
-> cd $HOME/mingw/lzo2-2.03
-> ./configure --host=i586-mingw32msvc
-> make
-> DESTDIR=$HOME/mingw make install
+ cd $HOME/mingw/lzo2-2.08
+ ./configure --host=i686-w64-mingw32
+ make
+ DESTDIR=$HOME/mingw make install
### Compiling Zlib
Cross-compiling Zlib is also easy, but a plain `make` failed to compile the
tests, so we only build the static library here:
-> cd $HOME/mingw/zlib-1.2.3.3.dfsg
-> mingw ./configure
-> mingw make libz.a
-> DESTDIR=$HOME/mingw mingw make install
+ cd $HOME/mingw/zlib-1.2.8.dfsg
+ mingw ./configure
+ mingw make libz.a
+ DESTDIR=$HOME/mingw mingw make install
-### Compiling OpenSSL
+### Compiling LibreSSL
-OpenSSL is always a bit hard to compile, because they have their own
-`Configure` script that needs some tweaking. There is also a small bug in
-e_os2.h that breaks compilation with recent versions of GCC. First download
-this [[openssl-cross-compilation.diff]] to your home directory, then patch
-OpenSSL, and then compile as usual. Do not use the `-j` option when compiling
-OpenSSL, it will break.
+Tinc can use either OpenSSL or LibreSSL. The latter is recommended.
-> cd $HOME/mingw/openssl-0.9.8k
-> patch < $HOME/openssl-cross-compilation.diff
-> mingw ./Configure --openssldir=$HOME/mingw/usr/local mingw
-> mingw make
-> mingw make install
+ cd $HOME/mingw/libressl-2.3.3
+ CC=i686-w64-mingw32-gcc ./configure --host=i686-w64-mingw32
+ make
+ DESTDIR=$HOME/mingw make install
### Compiling tinc
`autoreconf` first. If you want to cross-compile tinc from a released tarball,
this is not necessary.
-> cd $HOME/mingw/tinc
-> autoreconf -fsi
-> ./configure --host=i586-mingw32msvc --with-openssl=$HOME/mingw/usr/local
-> make
+ cd $HOME/mingw/tinc
+ autoreconf -fsi
+ ./configure --host=i686-w64-mingw32 --with-zlib=$HOME/mingw/usr/local
+ make
### Testing tinc
Since Wine was installed, you can execute the resulting binary even on Linux.
-You cannot do much however, since tinc requires a TAP-Win32 device, which is
-not available in Wine. Still, the following command should work:
+Wine does not provide a TAP-Win32 device, but you can use the `DeviceType = dummy` option to test it without.
+The following command should work in any case:
-> $HOME/mingw/tinc/src/tincd.exe --help
+ $HOME/mingw/tinc/src/tincd.exe --help
projects / wiki / blobdiff