[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[FT2 bug contest :-)]
From: |
David Turner |
Subject: |
[FT2 bug contest :-)] |
Date: |
Mon, 30 Oct 2000 16:27:26 +0100 |
Hello,
I'm posting the instructions to test the infamous "cache" bug,
since it seems lots of people have already proposed their help.
the following should work equally well on Unix and Windows.
You _need_ GNU make.
1. Get the current "freetype2" and "ft2demos" modules from
the CVS server. CVS password is "anonymous"; On Unix:
export CVSROOT=:pserver:address@hidden:/cvsroot
cvs login
cvs co freetype2 ft2demos
2. Compile the library in "developer mode" (no optimisations, debugging
and static build only to avoid libtool):
cd freetype2
make setup devel
make
3. Edit the file "ft2demos/src/ftcommon.i" with your favorite editor.
Line 32 reads as:
#undef USE_SBITS_CACHE
change it to:
#define USE_SBITS_CACHE
4. Compile the demo programs:
cd ../ft2demos
make
5. Run "bin/ftview". For example, on Unix:
bin/ftview 12 /usr/X11R6/lib/X11/fonts/Type1/*.pf?
on Windows:
bin\ftview 12 c:/windows/fonts/*.ttf
6. the program may crash immediately, dump many error messages to the
standard output. In some cases, it even displays correctly the first
font, but crashes when jumping to the next one with the "n" key.
7. To test it with Purify or any other tool, you'll probably need to
recompile it or re-link it. You'll need to edit the file
"ft2demos/Makefile"
be sure to add your own definition of "CC" or "LINK" in the Makefile,
but _after_ line 52, which reads:
include $(CONFIG_MK)
8. Recompile/Relink; then re-run the program. And let us know of any
interesting output you may find. By the way, the X11 memory leaks
are not related to this bug and are a fairly minor annoyance.. !!
Voila, the seeds are in place, let's wait for the harvest :-)
And thanks in advance to anybody involved..
- Cheers,
- David
- [FT2 bug contest :-)],
David Turner <=