Closed feliwir closed 2 years ago
Unity builds might help as well.
Unity builds might help as well.
They usually decrease incremental build time by a lot, which is not desirable in my opinion
I believe this merge broke the build for win64
D:\buildbot\wolfire-dev\overgrowth-build-win64\build\Source\Internal\datemodified.cpp(76): error C3861: 'ctime_s': identifier not found [D:\buildbot\wolfire-dev\overgrowth-build-win64\build\Build\OvergrowthWorker.vcxproj]```
@autious which VS version are you using? Our CI runner uses VS2022, which defaults to win64 and that one compiled succesfully
I believe it is vs2017
@autious is it fixed by including <time.h>
?
Run some clang compile time analysis and try to reduce some of the hotspots found (only the low hanging fruits). There are some other things i'll look out for and try to reduce. The are the principles i applied:
ninja
on anAMD Ryzen 7 1800X
If someone is interested in a good read about the tools i've used: https://aras-p.info/blog/2019/01/16/time-trace-timeline-flame-chart-profiler-for-Clang/ https://aras-p.info/blog/2019/09/28/Clang-Build-Analyzer/