• Show log

    Commit

  • Hash : f83ded01
    Author : Werner Lemberg
    Date : 2002-05-05T10:57:06

    FreeType 2 can now be built in an external directory with the
    configure script also.
    
    * builds/freetype.mk (INCLUDES): Add `OBJ_DIR'.
    
    * builds/unix/detect.mk (have_mk): New variable to test for
    external build.
    (unix-def.mk): Defined according to value of `have_mk'.
    * builds/unix/unix.mk (have_mk): New variable to test for
    external build.
    Select include paths for unix-def.mk and unix-cc.mk according
    to value of `have_mk'.
    * builds/unix/unix-def.in (OBJ_BUILD): New variable.
    (DISTCLEAN): Use it.
    * builds/unix/unix-cc.in (LIBTOOL): Define default value only
    if not yet defined.
    * builds/unix/install.mk (install): Use `OBJ_BUILD' for installing
    freetype-config.
    
    * configure: Don't depend on bash features.
    (ft2_dir, abs_curr_dir, abs_ft2_dir): New variables (code
    partially taken from Autoconf).
    Build a dummy Makefile if not building in source tree.
    
    * docs/INSTALL: Document it.
    

  • README

  •   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.1.0
      ==============
    
      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.1.0.tar.bz2
        ftp://ftp.freetype.org/pub/freetype2/ftdocs-2.1.0.tar.gz
        ftp://ftp.freetype.org/pub/freetype2/ftdoc210.zip
    
    
      Reports
      =======
    
      Please  report  bugs  by  e-mail to  `devel@freetype.org'.   Don't
      forget to send  a detailed explanation of the  problem -- there is
      nothing worse  than receiving a  terse message that only  says "it
      doesn't work".
    
    
    
      Enjoy!
    
    
        The FreeType Team