Commit 6030a9f7554eceb2a0cfef011448d671edf54fa2
2014-03-01T14:01:12
* docs/INSTALL.CROSS: Revised and updated.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154
diff --git a/ChangeLog b/ChangeLog
index c32fdba..f2b68a2 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
2014-03-01 Werner Lemberg <wl@gnu.org>
+ * docs/INSTALL.CROSS: Revised and updated.
+
+2014-03-01 Werner Lemberg <wl@gnu.org>
+
Make `make clean' remove `freetype2.pc'.
This is a generated file at build time, not configure time.
diff --git a/docs/INSTALL.CROSS b/docs/INSTALL.CROSS
index 005d442..d372adc 100644
--- a/docs/INSTALL.CROSS
+++ b/docs/INSTALL.CROSS
@@ -1,26 +1,27 @@
This document contains instructions on how to cross-build the FreeType
library on Unix systems, for example, building binaries for Linux/MIPS
-on FreeBSD/i386. Before reading this document, please consult
-INSTALL.UNIX for required tools and the basic self-building procedure.
+on FreeBSD/i386. Before reading this document, please consult the
+file `INSTALL.UNIX' for required tools and the basic self-building
+procedure.
1. Required Tools
-----------------
For self-building the FreeType library on a Unix system, GNU Make
- 3.80 or newer is required. INSTALL.UNIX contains hints how to
+ 3.80 or newer is required. `INSTALL.UNIX' contains hints how to
check the installed `make'.
The GNU C compiler to cross-build the target system is required.
- At present, using non-GNU cross compiler is not tested. The cross
+ Currently, using a non-GNU cross compiler is untested. The cross
compiler is expected to be installed with a system prefix. For
example, if your building system is FreeBSD/i386 and the target
- system is Linux/MIPS, the cross compiler should be installed with
+ system is Linux/MIPS, the cross compiler should be installed with
the name `mips-ip22-linuxelf-gcc'.
A C compiler for a self-build is required also, to build a tool
- that is executed during the building procedure. Non-GNU self
- compilers are acceptable, but such a setup is not tested yet.
+ (`apinames') that is executed during the build procedure. Non-GNU
+ self compilers are acceptable, but such a setup is untested.
2. Configuration
@@ -28,10 +29,10 @@ INSTALL.UNIX for required tools and the basic self-building procedure.
2.1. Building and target system
- To configure for cross-build, the options `--host=<system>' and
- `--build=<system>' must be passed to configure. For example, if
- your building system is FreeBSD/i386 and the target system is
- Linux/MIPS, say
+ To configure a cross-build, the options `--host=<system>' and
+ `--build=<system>' must be passed to the `configure' script.
+ For example, if your build system is FreeBSD/i386 and the target
+ system is Linux/MIPS, say
./configure \
--build=i386-unknown-freebsd \
@@ -58,22 +59,63 @@ INSTALL.UNIX for required tools and the basic self-building procedure.
2.2. The prefix to install FreeType2
Setting `--prefix=<prefix>' properly is important. The prefix
- to install FreeType2 is written into the freetype-config script
- and freetype2.pc configuration file.
+ to install FreeType2 is written into the `freetype-config'
+ script and `freetype2.pc' configuration file.
If the built FreeType 2 library is used as a part of the
cross-building system, the prefix is expected to be different
- from the self-building system. For example, configuration with
- `--prefix=/usr/local' installs binaries into the system wide
- `/usr/local' directory which then can't be executed. This
- causes confusion in configuration of all applications which use
- FreeType2. Instead, use a prefix to install the cross-build
- into a separate system tree, for example,
- `--prefix=/usr/local/mips-ip22-linux/'.
-
- On the other hand, if the built FreeType2 is used as a part of
- the target system, the prefix to install should reflect the file
- system structure of the target system.
+ from the self-building system. For example, a configuration
+ with `--prefix=/usr/local' installs binaries into the
+ system-wide `/usr/local' directory, which then can't be executed
+ due to the incorrect architecture. This causes confusion in
+ configuration of all applications that use FreeType2. Instead,
+ use a prefix to install the cross-build into a separate system
+ tree, for example, `--prefix=/usr/local/mips-ip22-linux/'.
+
+ On the other hand, if the built FreeType 2 library is used as a
+ part of the target system, the prefix to install should reflect
+ the file system structure of the target system.
+
+
+ 2.3. Library dependencies
+
+ FreeType normally depends on external libraries like `libpng' or
+ `libharfbuzz'. The easiest case is to deactivate all such
+ dependencies using the `--without-XXX' configuration options.
+ However, if you want to use those libraries, you should ensure
+ that they are available both on the target system and as
+ (cross-compiled) libraries on the build system.
+
+ FreeType uses `pkg-config' to find most of the libraries; the
+ other libraries it links to are expected in the standard system
+ directories. Since the default pkg-config's meta-information
+ files (like `harfbuzz.pc') of the build platform don't work, use
+ one of the two possible solutions below.
+
+ o Use pkg-config's meta-information files that are adjusted to
+ cross-compile and cross-link with the target platform's
+ libraries. Make sure those files are found before the build
+ system's default files. Example:
+
+ ./configure \
+ --build=i386-unknown-freebsd \
+ --host=mips-ip22-linuxelf \
+ PKG_CONFIG_LIBDIR="/usr/local/mips-ip22-linux/lib/pkgconfig" \
+ [other options]
+
+ See the manpage of `pkg-config' for more details.
+
+ o Set variables like LIBPNG_LIBS as additional options to the
+ `configure' script, overriding the values `pkg-config' would
+ provide. `configure --help' shows the available environment
+ variables. Example:
+
+ ./configure \
+ --build=i386-unknown-freebsd \
+ --host=mips-ip22-linuxelf \
+ LIBPNG_CFLAGS="-I/usr/local/mips-ip22-linux/include" \
+ LIBPNG_LIBS="-L/usr/local/mips-ip22-linux/lib -lpng12" \
+ [other options]
3. Building command
@@ -121,7 +163,7 @@ INSTALL.UNIX for required tools and the basic self-building procedure.
----------------------------------------------------------------------
-Copyright 2006, 2008, 2012 by suzuki toshiya
+Copyright 2006, 2008, 2012, 2014 by suzuki toshiya
David Turner, Robert Wilhelm, and Werner Lemberg.