Re: Pregenerate fontconfig cache
Guillermo Rodriguez Garcia <[email protected]>
| Newsgroups | gmane.comp.fonts.fontconfig |
|---|---|
| Message-ID | <CABDcavZ77Ny4j9Bd7ZUg0vJxQzLhMNTdkpvoiNxb82BN2CO-Mg@mail.gmail.com> |
Hello, Thank you for the info. Is there any way to tell fontconfig not to check the mtime of font directories? Since I have full control over fonts installed in the device, and I would be pregenerating the cache file, I would be happy to tell fontconfig to just use the cache file without any further checks. Other than that, is there a recommended procedure for this? (pregenerating cache files) Thank you, Guillermo 2016-08-17 4:21 GMT+02:00 Akira TAGOH <[email protected]>: > Fontconnfig is checking the mtime of the directories fonts installed > to detect the changes. that message means the mtime of > /usr/share/fonts/X11 is different where the caches originally > generated. > > On Tue, Aug 16, 2016 at 9:13 PM, Guillermo Rodriguez Garcia > <[email protected]> wrote: >> Hi all, >> >> I have an embedded system where the list of fonts is known in advance >> and cannot change. I want to pregenerate the fontconfig cache files >> for an embedded system in order to avoid long startup times on first >> boot. >> >> I already learned that the cache files are architecture specific so >> they need to be generated either on the target hardware or using qemu >> or similar. What I am doing right now is: >> >> - Install fonts on target system >> - Generate cache files (fc-cache -f) >> - Get generated cache files and add them to the build system >> - Generate a rootfs image containing the original font files and the >> cache files. This is the rootfs image that will be installed on the >> target devices. >> >> However when I install this rootfs image to the target system, on >> first boot the pregenerated cache files are ignored, and the cache >> files are regenerated again from scratch. >> >> Setting FC_DEBUG=16 I see this: >> >> $ fc-list >> FC_DEBUG=16 >> FcCacheTimeValid dir "/usr/share/fonts/X11" cache checksum 1167623491 >> dir checksum 1167628683 >> >> Why are the checksums different? Is there a way to avoid this? >> >> Thank you, >> >> Guillermo Rodriguez Garcia >> [email protected] >> _______________________________________________ >> Fontconfig mailing list >> [email protected] >> https://lists.freedesktop.org/mailman/listinfo/fontconfig > > > > -- > Akira TAGOH -- Guillermo Rodriguez Garcia [email protected] _______________________________________________ Fontconfig mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/fontconfig