Bug 4549

Summary: Libxml2 support
Product: fontconfig Reporter: Mathias Hasselmann <mathias.hasselmann>
Component: libraryAssignee: Keith Packard <keithp>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high    
Version: 2.3   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Libxml2 support
Patch against fc-2_4_branch
Working version of the patch.
Patch using libxml2 as fallback for expat
Next iteration

Description Mathias Hasselmann 2005-09-22 02:21:37 UTC
This patch allows fontconfig to use libxml2 as SAX parser instead of Expat. When
using fontconfig in Glade-enabled applications, libxml2 is needed anyway, so
adding this choice drops an unneeded library dependency for this common scenario.
Comment 1 Mathias Hasselmann 2005-09-22 02:22:30 UTC
Created attachment 3361 [details] [review]
Libxml2 support
Comment 2 Mathias Hasselmann 2005-09-23 14:14:21 UTC
Created attachment 3387 [details] [review]
Patch against fc-2_4_branch

Patch against fc-2_4_branch as requested (even if the old patch applies
cleanly).
Comment 3 Mathias Hasselmann 2005-09-23 15:51:28 UTC
Created attachment 3388 [details] [review]
Working version of the patch.

Previous version just worked by accident. Shame on me.
Comment 4 Mathias Hasselmann 2005-09-25 10:29:53 UTC
Created attachment 3400 [details] [review]
Patch using libxml2 as fallback for expat

This version of the patch instructs configure to use libxml2 as fallback, if
expat cannot be found.
Comment 5 Mathias Hasselmann 2005-09-29 00:26:07 UTC
Created attachment 3424 [details] [review]
Next iteration 

Next iteration of the patch, more specificly »configure.in«:

- explicitly reset EXPAT_*, when expat is not found 
  to avoid linking against -lexpat
- explicitly call AC_SUBST for LIBXML2_*, because automake-1.4
  doesn't realize, that PKG_CHECK_MODULES performs this action
Comment 6 Patrick Lam 2006-02-22 02:34:17 UTC
I've committed this a while ago.

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.