summaryrefslogtreecommitdiff
path: root/fontconfig/fontconfig-2.8.0.patch
AgeCommit message (Collapse)AuthorFilesLines
2012-08-16For kicks, enable cross-building for Android on MIPSTor Lillqvist1-2/+2
Change-Id: I6fa2b9a50c525fb2d8666a144409eb9a3ad2698a
2012-01-13Must use the "ascii" version of our expat build with fontconfigTor Lillqvist1-1/+1
Sigh, spent one day, more or less, tracking down a weird fontconfig problem, where all the diagnostic it offered was "unknown encoding" when reading the fonts.conf file. It turned out that I was being screwed by our fun two versions of the expat_xmlparse library: One where XML_Char is char and one where it is short. The intuitively "more normally" named libexpat_xmlparse is the latter, but fontconfig works only with the former as it implicitly expects XML_Char to be char.
2012-01-05Don't use soname, Android doesn't support thatTor Lillqvist1-0/+9
2011-12-11Download and build FreeType and fontconfig for AndroidTor Lillqvist1-0/+49
It will probably be simplest to just use FreeType on Android, too. (Android uses it itself, but doesn't provide its API publicly.) Probably fontconfig, too, although there shouldn't be much configuration per se that a LibreOffice-baed app would have to do at run-time; it will have to bundle all fonts it is going to use anyway, I think, so all font information is known a priori. But maybe in the future there will be user-installable system fonts on Android, or something.