path: root/src/3rdparty/freetype/docs/INSTALL.GNU
diff options
authorKonstantin Ritt <>2015-03-19 17:34:42 +0400
committerKonstantin Ritt <>2015-03-20 13:42:29 +0000
commit2eaf0cf8fd6e7c290497fedb08134a89e7b49b1d (patch)
tree0a4f7bf528e87d0b0a71ce7fccf702b87f4cdec1 /src/3rdparty/freetype/docs/INSTALL.GNU
parent77c518a50334d4dcf2476a4f39edc1e3990c7f0b (diff)
Update bundled FreeType to 2.5.5
Removed everything, imported with help of script, and then added a pre-generated builds/unix/ftconfig.h Task-number: QTBUG-44648 Change-Id: Iea948e41f7761f1580382b3763d04c7a61383382 Reviewed-by: Lars Knoll <>
Diffstat (limited to 'src/3rdparty/freetype/docs/INSTALL.GNU')
1 files changed, 0 insertions, 159 deletions
diff --git a/src/3rdparty/freetype/docs/INSTALL.GNU b/src/3rdparty/freetype/docs/INSTALL.GNU
deleted file mode 100644
index 72df50a4ea..0000000000
--- a/src/3rdparty/freetype/docs/INSTALL.GNU
+++ /dev/null
@@ -1,159 +0,0 @@
-This document contains instructions how to build the FreeType library
-on non-Unix systems with the help of GNU Make. Note that if you are
-running Cygwin or MSys in Windows, you should follow the instructions
-in the file INSTALL.UNIX instead.
- FreeType 2 includes a powerful and flexible build system that allows
- you to easily compile it on a great variety of platforms from the
- command line. To do so, just follow these simple instructions.
- 1. Install GNU Make
- -------------------
- Because GNU Make is the only Make tool supported to compile
- FreeType 2, you should install it on your machine.
- The FreeType 2 build system relies on many features special to GNU
- Make.
- Note that make++, a make tool written in Perl, supports enough
- features of GNU make to compile FreeType. See
- for more information; you need version 1.19 or newer, and you must
- pass option `--norc-substitution'.
- Make sure that you are invoking GNU Make from the command line, by
- typing something like:
- make -v
- to display its version number.
- 2. Invoke `make'
- ----------------
- Go to the root directory of FreeType 2, then simply invoke GNU
- Make from the command line. This will launch the FreeType 2 host
- platform detection routines. A summary will be displayed, for
- example, on Win32.
- ==============================================================
- FreeType build system -- automatic system detection
- The following settings are used:
- platform win32
- compiler gcc
- configuration directory .\builds\win32
- configuration rules .\builds\win32\
- If this does not correspond to your system or settings please
- remove the file '' from this directory then read the
- INSTALL file for help.
- Otherwise, simply type 'make' again to build the library
- or 'make refdoc' to build the API reference (the latter needs
- python).
- =============================================================
- If the detected settings correspond to your platform and compiler,
- skip to step 5. Note that if your platform is completely alien to
- the build system, the detected platform will be `ansi'.
- 3. Configure the build system for a different compiler
- ------------------------------------------------------
- If the build system correctly detected your platform, but you want
- to use a different compiler than the one specified in the summary
- (for most platforms, gcc is the default compiler), invoke GNU Make
- with
- make setup <compiler>
- Examples:
- to use Visual C++ on Win32, type: `make setup visualc'
- to use Borland C++ on Win32, type `make setup bcc32'
- to use Watcom C++ on Win32, type `make setup watcom'
- to use Intel C++ on Win32, type `make setup intelc'
- to use LCC-Win32 on Win32, type: `make setup lcc'
- to use Watcom C++ on OS/2, type `make setup watcom'
- to use VisualAge C++ on OS/2, type `make setup visualage'
- The <compiler> name to use is platform-dependent. The list of
- available compilers for your system is available in the file
- `builds/<system>/'.
- If you are satisfied by the new configuration summary, skip to
- step 5.
- 4. Configure the build system for an unknown platform/compiler
- --------------------------------------------------------------
- The auto-detection/setup phase of the build system copies a file
- to the current directory under the name `'.
- For example, on OS/2+gcc, it would simply copy
- `builds/os2/' to `./'.
- If for some reason your platform isn't correctly detected, copy
- manually the configuration sub-makefile to `./' and go to
- step 5.
- Note that this file is a sub-Makefile used to specify Make
- variables for compiler and linker invocation during the build.
- You can easily create your own version from one of the existing
- configuration files, then copy it to the current directory under
- the name `./'.
- 5. Build the library
- --------------------
- The auto-detection/setup phase should have copied a file in the
- current directory, called `./'. This file contains
- definitions of various Make variables used to invoke the compiler
- and linker during the build. [It has also generated a file called
- `ftmodule.h' in the objects directory (which is normally
- `<toplevel>/objs/'); please read the file `docs/CUSTOMIZE' for
- customization of FreeType.]
- To launch the build, simply invoke GNU Make again: The top
- Makefile will detect the configuration file and run the build with
- it.
- Final note
- The build system builds a statically linked library of the font
- engine in the `objs' directory. It does _not_ support the build
- of DLLs on Windows and OS/2. If you need these, you have to
- either use an IDE-specific project file, or follow the
- instructions in `INSTALL.ANY' to create your own Makefiles.
-Copyright 2003, 2004, 2005, 2006, 2008 by
-David Turner, Robert Wilhelm, and Werner Lemberg.
-This file is part of the FreeType project, and may only be used,
-modified, and distributed under the terms of the FreeType project
-license, LICENSE.TXT. By continuing to use, modify, or distribute
-this file you indicate that you have read the license and understand
-and accept it fully.
---- end of INSTALL.GNU ---