Go to file
2002-02-20 21:49:59 +00:00
builds * builds/unix/install.mk (check): New dummy target. 2002-02-20 00:55:59 +00:00
docs * README: Fix typo. 2002-02-09 17:59:12 +00:00
include * src/autohint/ahglyph.c (ah_outline_link_segments): Remove unused 2002-02-19 01:12:23 +00:00
objs renamed "obj" to "objs" 2001-03-20 15:04:30 +00:00
src * builds/freetype.mk (FT_CFLAGS): Use $(INCLUDE_FLAGS) first. 2002-02-19 16:30:15 +00:00
tests Formatting. 2001-12-05 01:22:05 +00:00
.cvsignore Formatting. 2000-10-31 19:42:53 +00:00
ChangeLog * builds/unix/install.mk (check): New dummy target. 2002-02-20 00:55:59 +00:00
configure fixed the "configure" script in the top-level directory.. 2002-01-29 18:13:54 +00:00
descrip.mms adding or updating files to the old build system to compile 2001-10-19 07:34:20 +00:00
install Formatting. 2002-01-09 21:01:18 +00:00
Jamfile Formatting. 2001-12-05 01:22:05 +00:00
Jamrules * builds/os2/*.mk: These files have been forgotten to update to 2001-04-06 07:05:50 +00:00
Makefile Added copyright messages to all Makefiles. 2000-10-17 03:38:43 +00:00
README adding "devel@freetype.org" address for bug reports 2002-02-20 21:49:59 +00:00
README.UNX updating documentation for 2.0.7 2002-01-31 17:42:05 +00:00

  Special note to Unix users
  ==========================

  Please   read  the  file   "README.UNX",  it   contains  important
  information  regarding  the   installation  of  FreeType  on  Unix
  systems, especially GNU based operating systems like GNU/Linux.


  FreeType 2.0.8
  ==============

  Please   read  the  docs/CHANGES   file,  it   contains  IMPORTANT
  INFORMATION.

  Read  the  files "docs/INSTALL"  or  "docs/BUILD" for installation
  instructions.

  Note  that the  FreeType 2  documentation  is now  available as  a
  separate package from our sites.  See:

    ftp://ftp.freetype.org/pub/freetype2/ftdocs-2.0.8.tar.bz2
    ftp://ftp.freetype.org/pub/freetype2/ftdocs-2.0.8.tar.gz
    ftp://ftp.freetype.org/pub/freetype2/ftdoc208.zip



  Reports
  =======

  Please report bugs by e-mail to 'devel@freetype.org'. Don't forget
  to join a detailed explanation of what's wrong, there is nothing
  worse than receiving a terse message that says "it doesn't work"
  for us :o)



  Enjoy!


    The FreeType Team