59939244ad
sufficient to modify a single file, `modules.cfg', to control the
inclusion of modules and base extension files.
This change also fixes the creation of ftmodule.h; it now depends on
`modules.cfg' and thus is rebuilt only if necessary.
Finally, a version of `ftoption.h' in OBJ_DIR is preferred over the
default location.
* modules.cfg: New file.
* builds/freetype.mk: Don't include `modules.mk'.
Include all `rules.mk' files as specified in `modules.cfg'.
(FTOPTION_FLAG, FTOPTION_H): New variables.
(FT_CFLAGS): Add macro definition for FT_CONFIG_MODULES_H.
Add FTOPTION_FLAG.
($(FT_INIT_OBJ)): Don't use FT_MODULE_LIST.
(CONFIG_H): Add FTMODULE_H and FTOPTION_H.
(INCLUDES): Add DEVEL_DIR.
(INCLUDE_FLAGS, FTSYS_SRC, FTSYS_OBJ, FTDEBUG_SRC, FTDEBUG_OBJ,
OBJ_M, OBJ_S): Use `:=', not `='.
(remove_ftmodule_h): New phony target to delete `ftmodule.h'.
(distclean): Add remove_ftmodule_h.
* builds/modules.mk: (MODULE_LIST): Removed.
(make_module_list, clean_module_list): Replace targets
with...
(FTMODULE_H_INIT, FTMODULE_H_CREATE, FTMODULE_H_DONE): New
variables. Reason for the change is that it is not possible to have
a phony prerequisite which is run only if the target file must be
rebuilt (phony prerequisites act like subroutines and are *always*
executed). We only want to rebuild `ftmodule.h' if `module.cfg' is
changed.
Update all callers.
($FTMODULE_H)): Rule to create `ftmodule.h', depending on
`modules.cfg'.
* builds/toplevel.mk: Rewrite and simplify module handling.
(MODULES_CFG, FTMODULE_H): New variables.
Include MODULES_CFG.
(MODULES): New variable to include all `module.mk' and `rules.mk'
files. We no longer use make's `wildcard' function for this.
* Makefile (USE_MODULES): Remove. Update all users.
(OBJ_DIR): Define it here.
* src/*/module.mk: Change
make_module_list: foo
foo: ...
to
FTMODULE_H_COMMANDS += FOO
define FOO
...
endef
in all files. `FTMODULE_H_COMMANDS' is used in `FTMODULE_H_CREATE'.
* src/base/rules.mk (BASE_EXT_SRC): Use BASE_EXTENSIONS.
* builds/unix/detect.mk (setup): Always execute `configure' script.
(have_mk): Rename to...
(have_Makefile): This.
Don't use `strip' function.
* builds/unix/unix.mk: Include `install.mk' only if BUILD_PROJECT is
defined.
(have_mk): Don't use `strip' function.
Test for unix-def.mk in OBJ_DIR, not BUILD_DIR (and invert the test
accordingly).
* builds/unix/install.mk (install, uninstall): Handle `ftmodule.h'.
* builds/os2/os2-dev.mk, builds/unix/unix-dev.mk,
builds/win32/w32-bccd.mk, builds/win32/w32-dev.mk: Don't define
BUILD_DIR but DEVEL_DIR for development header files.
* builds/ansi/ansi-def.mk (TOP_DIR, OBJ_DIR),
builds/beos/beos-def.mk (TOP_DIR, OBJ_DIR), builds/unix/unix-def.in
(TOP_DIR, OBJ_DIR): Removed. Defined elsewhere.
* builds/dos/dos-def.mk (OBJ_DIR), builds/os2/os2-def.mk (OBJ_DIR),
builds/win32/win32-def.mk (OBJ_DIR): Removed. Defined elsewhere.
* builds/unix/unixddef.mk: Don't define BUILD_DIR but DEVEL_DIR for
development header files.
Don't define PLATFORM.
* configure: Copy `modules.cfg' to builddir if builddir != srcdir.
Update snippet taken from autoconf's m4sh.m4 to current CVS version.
Be more verbose.
* include/freetype/config/ftmodule.h: Add comments -- this file is
no longer used if FreeType is built with GNU make.
* docs/CHANGES, docs/CUSTOMIZE, docs/INSTALL, docs/INSTALL.ANY,
docs/INSTALL.GNU, docs/INSTALL.UNX: Document new build mechanism.
Other minor updates.
* modules.txt: Removed. Contents included in `modules.cfg'.
* include/freetype/internal/ftmemory.h (FT_QAlloc_Debug,
FT_Free_Debug) [FT_STRICT_ALIASING]: Fix typos.
* src/base/ftdbgmem.c (FT_Alloc_Debug, FT_Realloc_Debug,
FT_QAlloc_Debug, FT_QRealloc_Debug, FT_Free_Debug)
[FT_STRICT_ALIASING]: Implement.
160 lines
5.8 KiB
Gnuplot
160 lines
5.8 KiB
Gnuplot
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.UNX 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.
|
|
|
|
NEARLY ALL OTHER MAKE TOOLS FAIL, INCLUDING `BSD MAKE', SO REALLY
|
|
INSTALL A RECENT VERSION OF GNU MAKE ON YOUR SYSTEM!
|
|
|
|
Note that make++, a make tool written in Perl, supports enough
|
|
features of GNU make to compile FreeType. See
|
|
|
|
http://makepp.sourceforge.net
|
|
|
|
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.
|
|
|
|
VERSION 3.78.1 OR NEWER IS NEEDED!
|
|
|
|
|
|
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\w32-gcc.mk
|
|
|
|
If this does not correspond to your system or settings please
|
|
remove the file 'config.mk' 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 defaut 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>/detect.mk'.
|
|
|
|
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 `config.mk'.
|
|
|
|
For example, on OS/2+gcc, it would simply copy
|
|
`builds/os2/os2-gcc.mk' to `./config.mk'.
|
|
|
|
If for some reason your platform isn't correctly detected, copy
|
|
manually the configuration sub-makefile to `./config.mk' 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 `./config.mk'.
|
|
|
|
|
|
5. Build the library
|
|
--------------------
|
|
|
|
The auto-detection/setup phase should have copied a file in the
|
|
current directory, called `./config.mk'. 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 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 ---
|