|
1 | 1 | Building Cairo on Windows
|
2 | 2 | =========================
|
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. |
9 | 13 |
|
10 | 14 | The second way is to use a GNU-compatible make, but build using
|
11 | 15 | 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. |
13 | 18 |
|
14 | 19 | Tools required
|
15 | 20 | ==============
|
|
0 commit comments