Bug 1062 - HAVE_FT_BITMAP_SIZE_Y_PPEM
Summary: HAVE_FT_BITMAP_SIZE_Y_PPEM
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/Xft (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 351
  Show dependency tree / graph
 
Reported: 2004-08-12 12:50 UTC by Owen Taylor
Modified: 2004-09-16 20:23 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:

Attachments
Proposed fix (775 bytes, patch)
2004-08-12 14:15 UTC, Owen Taylor 		no flags Details | Splinter Review
View All

Description Owen Taylor 2004-08-12 12:50:14 UTC 
I'm seeing a problem where the standalone Xft library works fine with
FreeType-2.1.9 but the same code build as part of the monolithic X
tree is unable to load PCF fonts.

I think the problem is that the Xft configure.ac contains a check
for HAVE_FT_BITMAP_SIZE_Y_PPEM. When built in the Xorg tree this
will never be set.

I don't really have a good idea how to solve this....  probably
easiest is to replace the configure check with a #if on
FREETYPE_MAJOR/FREETYPE_MINOR/FREETYPE_PATCH.
Comment 1 Owen Taylor 2004-08-12 14:15:01 UTC 
Created attachment 621 [details] [review]
Proposed fix

I've attached a proposed fix, not tested since I don't have a built
copy of the monolithic tree at the moment.
Comment 2 Mike A. Harris 2004-08-12 16:21:49 UTC 
Adding to release blocker bug.
Comment 3 Søren Sandmann Pedersen 2004-08-13 11:29:06 UTC 
Fri Aug 13 19:47:12 2004  Soeren Sandmann  <sandmann@redhat.com>

	* xftint.h: Make HAVE_FT_BITMAP_SIZE_Y_PPEM conditional on the
	FreeType version instead of proping it. This way it will work
	with the monolithic version too. #1062, Patch by Owen Taylor.
Comment 4 Martin Mokrejs 2004-09-17 13:23:40 UTC 
I don't see this fix applied to tree at
CVSROOT=:pserver:anoncvs@anoncvs.xfree86.org:/cvs

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.