Tim@Visual Micro wrote on May 30
th, 2018 at 12:37pm:
What is" tools>options>visual micro>compiler optimization" set to?
Both default to True, are they both set to True?
Thanks
No. 'Library Modified' was set to FALSE, although I have no idea how/why.
I set it back to TRUE and recompiled several times; the first time took about 16 sec, and the next three all took about 10 sec. These times are significantly longer than with this option set to FALSE (10/7 resp).
Set it back to FALSE. The first compile took WAY longer (27 sec, with most of that time spent in the 'Linking' section. Next compile was 24 sec, then 23 sec, then 22 sec - RATS!!
Set it back to TRUE. Now almost all the time (9.2 sec on the first compile) was spent on 'Linking'. 2nd compile was 9.7 sec, almost all spent either on 'Compiling Libraries' or 'Linking'. The actual code compile is insignificant (less than 1 sec)
Set it back to FALSE just for completeness. First compile about 24 sec, 2nd one 22, 3rd one 23 sec.
Back to TRUE: 1st = 9.8, 2nd 9.9, 3rd 9.9 sec
I did notice that with the option set to TRUE, the time to compile the code was reduced to almost nothing. In fact I have to watch closely to see the 'compiling code' string display between 'Compiling Libraries' and 'Linking'. This is a change from before, where the code section compile took a second or so, and the library/linking sections took significantly less, for a total of around 7.8 sec on average.
So, it appears that messing with the 'Library Modified' option had the net effect of costing me about 2 sec/compile, without any positive effect
I left it set for TRUE, as now the previous FALSE option is WAY too expensive in terms of time.
Frank
PS: When I opened VS2017 this morning, I got a notification about a new version of Visual Micro, so I checked the release notes for 1804 - 1806 (I'm using 1803).
1805.14: Support local project source code override
1805.25: When Deep Search for Libraries is enabled
Would either of these affect my issue?
Frank