# Long compile times on Windows 10 status

5 messages
Open this post in threaded view
|

## Long compile times on Windows 10 status

 Hi folks, Although a dyed in the wool Linux user, I am experimenting with Windows 10. At 2.19.48 I am seeing the long compile times that have been mentioned, for every run. With 2.19.39 the compilation is normal and quite fast. [I picked this previous release at random, to simply get back somewhere before the current problem arose.] Running Windows 10 14393.321. What is the current status on this, and is there a workaround? Andrew  _______________________________________________ lilypond-user mailing list [hidden email] https://lists.gnu.org/mailman/listinfo/lilypond-user
Open this post in threaded view
|

## RE: Long compile times on Windows 10 status

 I’ve found that whenever I install a new font on my computer, I wind up in this state.   That being said, I can recover back to normal speeds by deleting the C:\Users\\.lilypond-fonts.cache-2 folder.  The first build after doing this will be slow (because it’s rebuilding the font cache), but after that, speeds are back to normal.   --Steven   From: lilypond-user [mailto:lilypond-user-bounces+panteck=[hidden email]] On Behalf Of Andrew Bernard Sent: Sunday, October 16, 2016 4:42 PM To: [hidden email] Subject: Long compile times on Windows 10 status   Hi folks,   Although a dyed in the wool Linux user, I am experimenting with Windows 10. At 2.19.48 I am seeing the long compile times that have been mentioned, for every run. With 2.19.39 the compilation is normal and quite fast. [I picked this previous release at random, to simply get back somewhere before the current problem arose.]   Running Windows 10 14393.321.   What is the current status on this, and is there a workaround?   Andrew     _______________________________________________ lilypond-user mailing list [hidden email] https://lists.gnu.org/mailman/listinfo/lilypond-user
Open this post in threaded view
|

## Re: Long compile times on Windows 10 status

 Hi Steven,I get the slow compile on every run. I believe this is a current development issue.AndrewOn 17 October 2016 at 10:45, Steven Weber wrote: I’ve found that whenever I install a new font on my computer, I wind up in this state.   That being said, I can recover back to normal speeds by deleting the C:\Users\\.lilypond-fonts.cache-2 folder.  The first build after doing this will be slow (because it’s rebuilding the font cache), but after that, speeds are back to normal.   _______________________________________________ lilypond-user mailing list [hidden email] https://lists.gnu.org/mailman/listinfo/lilypond-user