1
Installation on Woe32 (Microsoft Windows):
3
There are three ways to create binaries of this package for Woe32:
4
1) Native binaries, built using the mingw tool chain.
5
2) Native binaries, built using the MS Visual C/C++ tool chain.
6
3) Binaries for the Cygwin environment. For these, please see the normal
9
===============================================================================
10
1) Native binaries, built using the mingw tool chain.
12
I recommend to use the cygwin environment as the development environment
13
and mingw only as the target (runtime, deployment) environment.
14
For this, you need to install
16
- the mingw runtime package, also from the cygwin site.
18
Building for mingw is achieved through the following preparation,
19
configure, and build commands:
21
PATH=/usr/local/mingw/bin:$PATH
23
./configure --host=i586-pc-mingw32 --prefix=/usr/local/mingw \
24
CC="gcc-3 -mno-cygwin" \
25
CXX="g++-3 -mno-cygwin"
33
===============================================================================
34
2) Native binaries, built using the MS Visual C/C++ tool chain.
36
Note that binaries created with MSVC have a distribution constraint: They
37
depend on a closed-source library ('msvcr70.dll' for MSVC 7.0, 'msvcr90.dll'
38
for MSVC 9.0, and so on) which is not normally part of a Windows
40
You cannot distribute 'msvcr*.dll' with the binaries - this would be a
41
violation of the GPL and of the Microsoft EULA.
42
You can distribute the binaries without including 'msvcr*.dll', but this
43
will cause problems for users that don't have this library on their system.
44
Therefore it is not recommended; the mingw tool chain is preferred for
47
Requires MS Visual C/C++ 4.0 or newer. The "Express" edition which
48
contains just the tools and not the IDE is sufficient.
50
Requires also a cygwin or mingw environment (with 'bash', the common POSIX
51
commands, and 'make' ) as a build environment. Building with "nmake" is no
54
Make sure that the MSVC tools ("cl" etc.) are found in PATH.
55
In a typical MSVC 6.0 installation, this can be achieved by running
56
C:\Program Files\Microsoft Visual Studio\VC98\bin\vcvars32.bat
57
In a typical MSVC 7.0 installation, it can be achieved by running
58
C:\Program Files\Microsoft Visual Studio .NET\Common7\Tools\vsvars32.bat
59
In a typical MSVC 9.0 installation, it can be achieved by running
60
C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat
62
Then start a bash (from cygwin or mingw).
64
Building for mingw is achieved through the following preparation,
65
configure, and build commands:
67
PATH=/usr/local/msvc/bin:$PATH
70
win32_target=_WIN32_WINNT_WINXP # for MSVC 9.0
71
win32_target=_WIN32_WINNT_VISTA # possibly for MSVC >= 10.0
72
win32_target=_WIN32_WINNT_WIN7 # possibly for MSVC >= 10.0
74
./configure --host=i586-pc-mingw32 --prefix=/usr/local/msvc \
75
CC="`pwd`/build-aux/compile cl -nologo" \
77
CXX="`pwd`/build-aux/compile cl -nologo" \
79
CPPFLAGS="-D_WIN32_WINNT=$win32_target -I/usr/local/msvc/include" \
80
LDFLAGS="-L/usr/local/msvc/lib" \
82
NM="dumpbin -symbols" \
84
AR="`pwd`/build-aux/ar-lib lib" \
93
===============================================================================