| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ie9ae6c2087dd6757ca22eabe2073e1f03a5489c8
|
|
|
|
|
|
|
| |
Change-Id: I2e779831e47cb1243ae7319b73b9fa553cf97034
Reviewed-on: https://gerrit.libreoffice.org/852
Reviewed-by: Michael Meeks <michael.meeks@suse.com>
Tested-by: Michael Meeks <michael.meeks@suse.com>
|
|
|
|
|
|
|
| |
We need to be able to link both into one binary in the
disable-dynloading case.
Change-Id: I499e204dfef2af488d4a350cb3a5bcfc03ca887f
|
|
|
|
| |
Change-Id: I6fa2b9a50c525fb2d8666a144409eb9a3ad2698a
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
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.
|