projects
/
wiki
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
7e98de3
)
Mention that other distributions can use different names for the mingw32 architecture.
author
Guus Sliepen
<guus@tinc-vpn.org>
Wed, 16 Dec 2009 21:13:39 +0000
(22:13 +0100)
committer
Guus Sliepen
<guus@tinc-vpn.org>
Wed, 16 Dec 2009 21:13:39 +0000
(22:13 +0100)
examples/cross-compiling-windows-binary.mdwn
patch
|
blob
|
history
diff --git
a/examples/cross-compiling-windows-binary.mdwn
b/examples/cross-compiling-windows-binary.mdwn
index
2e850c1
..
3a2eb56
100644
(file)
--- a/
examples/cross-compiling-windows-binary.mdwn
+++ b/
examples/cross-compiling-windows-binary.mdwn
@@
-24,6
+24,13
@@
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 mingw32 wine git-core
> 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
+directory however, for example `/usr/i686-pc-mingw32/`. Check in which directory
+it is installed, and replace all occurences of `i586-mingw32msvc` in this
+example with the correct name from your distribution.
+
### Setting up the build directory and getting the sources
We will create a directory called `mingw/` in the home directory. We use
### Setting up the build directory and getting the sources
We will create a directory called `mingw/` in the home directory. We use