This topic contains 3 replies, has 2 voices, and was last updated by 
julesd 1 year, 2 months ago.
-
Posts
-
Why is the compile time with MSVC X64 so much slower than version 1.1.09 of Monkey 2?
What are you building?
I haven’t noticed any obvious slowdowns with v1.1.10 myself, and I rebuild mx2cc/modules a lot!
Ok, v1.1.10 is actually faster here for updating modules:
v1.1.09 – update modules, clean existing data checked (ie: rebuild all): 15m 4s
followed immediately by…
v1.1.09 – update modules, clean existing data not checked: 0m 21s
…and…
v1.1.10 – update modules, clean existing data checked (ie: rebuild all): 13m 15s
followed immediately by…
v1.1.10 – update modules, clean existing data not checked: 0m 14s
Both of these used mx2cc built with msvc x64. To do this, you need to change to appropriate scripts dir and updatemx2cc with bin/env_windows.txt set correctly.
I am not exactly sure why it’s faster though. Although I’m constantly making tweaks to mx2cc, c++ compiles still take up most of the time when updating modules. There’s a chance that some change I made could be producing code that is more c++ friendly – wanna see if I can do more of it!
Do you perhaps have space in your project path? There was in fact a bug in mx2cc that I found shortly before the v1.1.10 release that caused mx2cc unnecessarily rebuild output c files that had a space in their path. I thought I had fixed this but maybe not?
Ok uninstalled Everything Monkey 1.1.10, Visual Studio Community 2017.
and reinstalled, seems to be fine now.
You must be logged in to reply to this topic.