61 2008-05-06 12:06:48 +0000 [Performance] Generate fontconfig cache when building image 2012-08-13 21:13:02 +0000 1 1 7 Build System, Metadata & Runtime Meta-yocto meta-yocto 0.9 All Multiple VERIFIED WONTFIX (P1)(Scheduled) Medium normal 1.3 M3 1 ross laurentiu.palcu elizabeth.flanagan jessica.zhang laurentiu.serban matthijs.van.de.water poky.bs.watcher poky.watcher richard.purdie ross.burton sgw shane.wang song.liu --- --- --- oldest_to_newest 3517 0 ross 2008-05-06 12:06:48 +0000 We should generate a fontconfig cache in the rootfs when the image is generated, to avoid it happening randomly on first boot. 11855 1 elizabeth.flanagan 2011-02-17 23:26:11 +0000 postponed to 1.1 23742 2 ross.burton 2012-08-02 14:23:23 +0000 As discussed on a call, the cache is architecture-dependent so it has to be run on the target, or in a qemu. I'm not convinced that the cache generation is sufficiently slow to make the overhead of qemu worth it. I suspect consolidating the multiple cache generation operations into a single operation would be a better win. (that's entirely without data, just a hunch) 23909 3 ross.burton 2012-08-09 09:21:34 +0000 So as the fontconfig cache is architecture dependent, so either - build it on the target - build it on the host in qemu I'm not convinced that the overhead of qemu is worth the effort. We used to build the locales this way because low-memory devices didn't have enough memory to the work. I'll close this as WONTFIX, and open another bug about moving the font cache generation to a trigger. 23991 4 laurentiu.serban 2012-08-13 21:13:02 +0000 Setting this to verified due to Ross latest comment