Bug 65 - BDF_PropertyRec' undeclared
Summary: BDF_PropertyRec' undeclared
Status: RESOLVED FIXED
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2_1
Hardware: All All
: high normal
Assignee: Keith Packard
QA Contact:
URL:
Whiteboard:
Keywords:
: 68 69 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-04-17 07:40 UTC by Morten Welinder
Modified: 2014-01-17 10:53 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Morten Welinder 2003-04-17 07:40:14 UTC
Something is up with the detection of BDF_PropertyRec availability.  I have

#define FREETYPE_MAJOR 2
#define FREETYPE_MINOR 1
#define FREETYPE_PATCH 3

which apparently isn't good enough.



fcfreetype.c: In function `FcFreeTypeQuery':
fcfreetype.c:783: `BDF_PropertyRec' undeclared (first use in this function)
fcfreetype.c:783: (Each undeclared identifier is reported only once
fcfreetype.c:783: for each function it appears in.)
fcfreetype.c:783: parse error before `prop'
fcfreetype.c:784: warning: implicit declaration of function `FT_Get_BDF_Property'
fcfreetype.c:784: `prop' undeclared (first use in this function)
fcfreetype.c:785: `BDF_PROPERTY_TYPE_ATOM' undeclared (first use in this function)
fcfreetype.c:791: parse error before `prop'
fcfreetype.c:793: `BDF_PROPERTY_TYPE_INTEGER' undeclared (first use in this
function)
fcfreetype.c:794: `BDF_PROPERTY_TYPE_CARDINAL' undeclared (first use in this
function)
fcfreetype.c:796: warning: `value' might be used uninitialized in this function
Comment 1 Keith Packard 2003-04-17 14:52:52 UTC
Yup.  Looks like the BDF property stuff didn't appear until FreeType 2.1.4.
Comment 2 Keith Packard 2003-04-18 10:39:25 UTC
*** Bug 68 has been marked as a duplicate of this bug. ***
Comment 3 Keith Packard 2003-04-18 12:19:40 UTC
*** Bug 69 has been marked as a duplicate of this bug. ***


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.