Skip to content

Commit b6e910f

Browse files
committed
[README.win32] Update wording from Tor Lillqvist
1 parent fc12267 commit b6e910f

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

README.win32

+12-7
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,20 @@
11
Building Cairo on Windows
22
=========================
3-
There are two primary ways to build Cairo on Windows. You can use a
4-
UN*X-like setup, such as Cygwin, with the conventional configure
5-
script shipped with Cairo releases. In this configuration, you will
6-
build with GCC and end up with (for instance) a Cygwin-dependent
7-
library. In theory, this technique is no different than the ordinary
8-
build process for the Cairo library.
3+
There are two primary ways to build Cairo on Windows. You can use a
4+
UNIX emulation based setup, such as Cygwin or MSYS, with the
5+
conventional configure script shipped with Cairo releases. In this
6+
configuration, you will build with GCC and (implicitly) libtool. In
7+
the Cygwin case you end up with a DLL that depends on Cygwin and
8+
should be used only from Cygwin applications. In the MSYS case you end
9+
up with a "normal" Win32 DLL that can be used either from GCC- or
10+
Microsoft Visual C++-compiled code. In theory, this technique is no
11+
different than the ordinary build process for the Cairo library. In
12+
practise there are lots of small details that can go wrong.
913

1014
The second way is to use a GNU-compatible make, but build using
1115
Microsoft's Visual C++ compiler to produce native libraries. This is
12-
the setup this README is written for.
16+
the setup this README.win32 is written for. Also the DLL produced this
17+
way is usable either from GCC- or MSVC-compiled code.
1318

1419
Tools required
1520
==============

0 commit comments

Comments
 (0)