Sorry for the wasted bandwidth. I just realized that I hadn't seen the
dot in your command line. Running
fc-cache.exe .
does indeed produce a fonts.cache-1 file of considerable size.
Also, I realized that I had been hit by the old problem that some
mingw commands don't print any output since the buffer isn't flushed.
To see better what happens, you can use something like:
C:\WINDOWS\Fonts>fc-cache.exe --verbose . > log
C:\WINDOWS\Fonts>more log
fc-cache.exe: ".": caching, 823 fonts, 0 dirs
fc-cache.exe: succeeded
However, when I run LilyPond --verbose ... , it still spends quite some
time
at
..
Initializing FontConfig...
Rebuilding FontConfig cache C:\Documents and
Settings\mats/.fonts.cache-1. this
may take a while...
adding font directory: C:/Program
Files/LilyPond/usr/share/lilypond//current/fonts/otf/
adding font directory: C:/Program
Files/LilyPond/usr/share/lilypond//current/fonts/type1/Building font
database.
..
and the file C:\Documents and Settings\mats/.fonts.cache-1
is still empty, but that's maybe normal? It seems that the time spent
on producing the cache file in C:\WINDOWS\Fonts\ was negligible,
I cannot notice any difference in the time it takes to run LilyPond.