libreoffice/core - main, development code repository

Age	Commit message (Collapse)	Author	Files	Lines
2012-04-29	make gbuild the default assumption of build.pl	Bjoern Michaelsen	1	-0/+0
	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-20	Build freetype and fontconfig statically for Android	Tor Lillqvist	2	-2/+4

2012-04-04	Use -g in CFLAGS when debugging requested	Tor Lillqvist	1	-0/+4

2012-01-30	keep the module name consistent in build.lst	Norbert Thiebaud	1	-3/+3

2012-01-13	Must use the "ascii" version of our expat build with fontconfig	Tor Lillqvist	1	-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-05	Don't use soname, Android doesn't support that	Tor Lillqvist	1	-0/+9

2011-12-16	Mark fontconfig as depending on expat	Tor Lillqvist	1	-1/+1

2011-12-11	Download and build FreeType and fontconfig for Android	Tor Lillqvist	4	-0/+117
	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.