This is just the final cleaned up version of the configuration that worked, if you go over the commits history at the github or the builds on appveyor you will see that I have tried many different things
https://github.com/sasobadovinac/FreeCA ... yor_vs2015
https://ci.appveyor.com/project/sasobad ... ad/history
here are some test builds with FREECAD_LIBPACK_DIR as environment variable (on top of every build there is a link to the commit)
https://ci.appveyor.com/project/sasobad ... s/23648724
https://ci.appveyor.com/project/sasobad ... s/23648849
If you hoover the mouse over the log at appveyor you can see the time for every line
Yes, I think there are 2 cpus and we are using the msbuild /m switch to use all the available coresapeltauer wrote: ↑Sun Apr 07, 2019 3:11 pmAll plans have 60 minutes quota per build job. https://www.appveyor.com/docs/build-con ... d-pipeline)
Also how many cpu cores are available?
In the past I have been testing https://github.com/frerich/clcache to speed up the Win builds, it worked, but not quite as it should. However I have not tested it lately, so maybe things have improved. But IMO, the first next thing to try is to set it up on Travis (I am quite busy with other things lately but maybe I will find some time to try it).
An article on speeding up C and C++ builds https://www.viva64.com/en/b/0549/