Commit a00ff98a503cb246c6b321d4150352455281d86e
2001-05-30T07:53:37
formatting, minor fixes
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
diff --git a/ChangeLog b/ChangeLog
index 2e5fc9c..d869c76 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,16 @@
+2001-05-29 Werner Lemberg <wl@gnu.org>
+
+ * INSTALL: Minor fixes.
+
+
+ * Version 2.0.3 released.
+ =========================
+
+
+2001-05-29 David Turner <david@freetype.org>
+
+ * INSTALL, docs/CHANGES: Updated.
+
2001-05-25 David Turner <david@freetype.org>
Moved several documents from the top-level to the "docs" directory.
diff --git a/INSTALL b/INSTALL
index e35eda8..467df10 100644
--- a/INSTALL
+++ b/INSTALL
@@ -5,43 +5,46 @@ directory. This is only a quick starter.
I. From the command line
------------------------
- There are two ways to quickly build FreeType 2 from the command line.
+ There are two ways to quickly build FreeType 2 from the command
+ line.
- The first, and favorite one, is to use the "Jam" build tool. Jam is
- a highly portable replacement for Make whose control files do not
+ The first, and favorite one, is to use the "Jam" build tool. Jam is
+ a highly portable replacement for Make whose control files do not
depend on the current platform or compiler toolset.
- For more information, please see: http://www.freetype.org/jam/index.html
+ For more information, please see:
+
+ http://www.freetype.org/jam/index.html
The second one is to use "GNU Make" (and NO OTHER MAKE TOOL).
- 1. Building FT2 with "Jam":
- ===========================
+ 1. Building FT2 with "Jam"
+ --------------------------
- once you've got *our version* of the Jam tool installed on your
- system, simply go to the top-level FT2 directory, then type:
+ Once you've got *our version* of the Jam tool installed on your
+ system, simply go to the top-level FT2 directory, then type
"jam"
- on the command line. This will build the library and place it
- in the "objs" directory.
+ on the command line. This will build the library and place it in
+ the "objs" directory.
- By default, a static library is built. On Unix systems, it's possible
- to build a shared library through the "libtool" script. You'll need
- to have libtool installed on your system, then re-define a few
- environment variables before invoking Jam, as in:
+ By default, a static library is built. On Unix systems, it is
+ possible to build a shared library through the "libtool" script.
+ You need to have libtool installed on your system, then re-define
+ a few environment variables before invoking Jam, as in
export CC="libtool --mode=compile"
export LINK="libtool --mode=link"
jam
- In later releases of FT2, building shared libraries with Jam should
- become automatic..
+ In later releases of FT2, building shared libraries with Jam
+ should become automatic.
- 2. Building FT2 with "GNU Make":
- ================================
+ 2. Building FT2 with "GNU Make"
+ -------------------------------
You need to have GNU Make (version 3.78.1 or newer) installed on
your system to compile the library from the command line. This will
@@ -121,7 +124,8 @@ II. In your own environment (IDE)
src/autohint/autohint.c -- auto hinting module
src/cache/ftcache.c -- cache sub-system (in beta)
- src/sfnt/sfnt.c -- SFNT files support (TrueType & OpenType)
+ src/sfnt/sfnt.c -- SFNT files support
+ (TrueType & OpenType)
src/cff/cff.c -- CFF/OpenType font driver
src/psnames/psnames.c -- Postscript glyph names support
src/psaux/psaux.c -- Postscript Type 1 parsing
@@ -139,6 +143,6 @@ II. In your own environment (IDE)
etc.
-For more information, please consult "docs/BUILD" !!
+For more information, please consult "docs/BUILD".
--- end of INSTALL --