Commit graph

8 commits

Author SHA1 Message Date
Bjoern Michaelsen
b1c3e8ae28 make gbuild the default assumption of build.pl
this removes dmake completely out of the build for migrated modules
build.pl now assumes modules to be gbuild, unless there is a
prj/dmake file

Change-Id: I674a036b182ee13c5ec093e83cb3d38133112d3b
2012-04-29 03:50:46 +02:00
Tor Lillqvist
0d1c24e5f6 Build freetype and fontconfig statically for Android 2012-04-20 00:57:24 +03:00
Tor Lillqvist
a5aa747d59 Use -g in CFLAGS when debugging requested 2012-04-04 22:29:41 +03:00
Norbert Thiebaud
27bd5ff1fd keep the module name consistent in build.lst 2012-01-30 18:44:25 -06:00
Tor Lillqvist
201ade8770 Must use the "ascii" version of our expat build with fontconfig
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-13 01:31:44 +02:00
Tor Lillqvist
c8bab278bb Don't use soname, Android doesn't support that 2012-01-05 17:53:02 +02:00
Tor Lillqvist
5bd8284c9d Mark fontconfig as depending on expat 2011-12-16 08:42:21 +02:00
Tor Lillqvist
75aacd87bb Download and build FreeType and fontconfig for Android
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.
2011-12-11 00:14:47 +02:00