Mario is correct.
Basically we want to be able to compile and load this library in systems where
libfontconfig is not available (or system where the given symbol,
FcConfigAppFontAddFile, is not there - maybe system using old version of
libfontconfig).
If it works for you, it just means your
I'm running on Ubuntu desktop, and I can gladly report that it works
fine. I think I saw fp wasn't null, but I'll check later. Maybe my only
fix was ignoring a 'false'. According to
https://www.freebsd.org/cgi/man.cgi?query=fontconfig=3=0=XFree86+4.5.0
FcConfigAppFontAddFile returns a FcBool,
Since I don't see any code here that looks like it would run only on
an embedded environment then I wonder why Linux desktop users
are not reporting the same problem ?
Did your instrumentation check that both dlopen & dlsym succeeeded ?
-phil.
On 3/3/16, 7:43 AM, Maurice wrote:
Hmm I
Hmm I think I have to agree with you... you are right. Commenting
it in didn't give a compiler or linkage error, and it made it work. I'm
happy at the moment and tired of the debugging process, but I'll give it
more thought later.
Op 03-03-16 om 16:36 schreef Mario Torre:
On Thu, Mar 3,
On Thu, Mar 3, 2016 at 2:48 PM, Maurice wrote:
> At the moment the embedded environment I'm using is not able to use
> downloaded or external supplied fonts. I've traced through the system and
> found that it looks like it fails in pango.c FcConfigAppFontAddFile, at
> least
At the moment the embedded environment I'm using is not able to use
downloaded or external supplied fonts. I've traced through the system
and found that it looks like it fails in pango.c FcConfigAppFontAddFile,
at least OSPango.FcConfigAppFontAddFile returns false, thus propagating
a null all