- Italian translation by Daniele Forsi (dforsi at gmail dot com)
[reactos.git] / reactos / dll / 3rdparty / freetype / docs / INSTALL.GNU
1 This document contains instructions how to build the FreeType library on
2 non-Unix systems with the help of GNU Make. Note that if you are
3 running Cygwin or MSys in Windows, you should follow the instructions in
4 the file INSTALL.UNX instead.
5
6
7 FreeType 2 includes a powerful and flexible build system that allows
8 you to easily compile it on a great variety of platforms from the
9 command line. To do so, just follow these simple instructions:
10
11 1. Install GNU Make
12 -------------------
13
14 Because GNU Make is the only Make tool supported to compile
15 FreeType 2, you should install it on your machine.
16
17 The FreeType 2 build system relies on many features special to GNU
18 Make -- trying to build the library with any other Make tool will
19 *fail*.
20
21 NEARLY ALL OTHER MAKE TOOLS WILL FAIL, INCLUDING "BSD MAKE", SO
22 REALLY INSTALL A RECENT VERSION OF GNU MAKE ON YOUR SYSTEM!
23
24 Note that make++, a make tool written in Perl, supports enough
25 features of GNU make to compile FreeType. See
26 http://makepp.sourceforge.net for more information; you need version
27 1.19 or newer, and you must pass option `--norc-substitution'.
28
29 Make sure that you are invoking GNU Make from the command line, by
30 typing something like:
31
32 make -v
33
34 to display its version number.
35
36 VERSION 3.78.1 OR NEWER IS NEEDED!
37
38
39 2. Invoke 'make'
40 ----------------
41
42 Go to the root directory of FreeType 2, then simply invoke GNU Make
43 from the command line. This will launch the FreeType 2 host
44 platform detection routines. A summary will be displayed, for
45 example, on Win32:
46
47
48 ==============================================================
49 FreeType build system -- automatic system detection
50
51 The following settings are used:
52
53 platform win32
54 compiler gcc
55 configuration directory ./builds/win32
56 configuration rules ./builds/win32/w32-gcc.mk
57
58 If this does not correspond to your system or settings please
59 remove the file 'config.mk' from this directory then read the
60 INSTALL file for help.
61
62 Otherwise, simply type 'make' again to build the library.
63 =============================================================
64
65
66 If the detected settings correspond to your platform and compiler,
67 skip to step 5. Note that if your platform is completely alien to
68 the build system, the detected platform will be 'ansi'.
69
70
71 3. Configure the build system for a different compiler
72 ------------------------------------------------------
73
74 If the build system correctly detected your platform, but you want
75 to use a different compiler than the one specified in the summary
76 (for most platforms, gcc is the defaut compiler), invoke GNU Make
77 with
78
79 make setup <compiler>
80
81 Examples:
82
83 to use Visual C++ on Win32, type: "make setup visualc"
84 to use Borland C++ on Win32, type "make setup bcc32"
85 to use Watcom C++ on Win32, type "make setup watcom"
86 to use Intel C++ on Win32, type "make setup intelc"
87 to use LCC-Win32 on Win32, type: "make setup lcc"
88 to use Watcom C++ on OS/2, type "make setup watcom"
89 to use VisualAge C++ on OS/2, type "make setup visualage"
90
91 The <compiler> name to use is platform-dependent. The list of
92 available compilers for your system is available in the file
93 `builds/<system>/detect.mk'
94
95 If you are satisfied by the new configuration summary, skip to
96 step 5.
97
98
99 4. Configure the build system for an unknown platform/compiler
100 --------------------------------------------------------------
101
102 The auto-detection/setup phase of the build system copies a file to
103 the current directory under the name `config.mk'.
104
105 For example, on OS/2+gcc, it would simply copy
106 `builds/os2/os2-gcc.mk' to `./config.mk'.
107
108 If for some reason your platform isn't correctly detected, copy
109 manually the configuration sub-makefile to `./config.mk' and go to
110 step 5.
111
112 Note that this file is a sub-Makefile used to specify Make variables
113 for compiler and linker invocation during the build. You can easily
114 create your own version from one of the existing configuration
115 files, then copy it to the current directory under the name
116 `./config.mk'.
117
118
119 5. Build the library
120 --------------------
121
122 The auto-detection/setup phase should have copied a file in the
123 current directory, called `./config.mk'. This file contains
124 definitions of various Make variables used to invoke the compiler
125 and linker during the build.
126
127 To launch the build, simply invoke GNU Make again: The top Makefile
128 will detect the configuration file and run the build with it.
129
130
131 Final note
132
133 The build system builds a statically linked library of the font
134 engine in the "objs" directory. It does _not_ support the build of
135 DLLs on Windows and OS/2. If you need these, you have to either use
136 a IDE-specific project file, or follow the instructions in
137 "INSTALL.ANY" to create your own Makefiles.
138
139 ------------------------------------------------------------------------
140
141 Copyright 2003, 2004 by
142 David Turner, Robert Wilhelm, and Werner Lemberg.
143
144 This file is part of the FreeType project, and may only be used,
145 modified, and distributed under the terms of the FreeType project
146 license, LICENSE.TXT. By continuing to use, modify, or distribute this
147 file you indicate that you have read the license and understand and
148 accept it fully.
149
150
151 --- end of INSTALL.GNU ---