Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic VS2017 CE long compile times with new installation (Read 3089 times)
FrankP
Senior Member
****
Offline


Posts: 251
Joined: Oct 19th, 2011
VS2017 CE long compile times with new installation
Jul 2nd, 2018 at 11:21pm
Print Post  
I have a brand-new XPS-15 with new, default installations of VS2017 CE and Visual Micro.  The only VM setting I have changed is to set the 'Auto Open Serial' flag to TRUE.  I'm using the 'Visual Micro (no IDE)' selection in the 'configure IDE locations' field rather than installing a version of the Arduino IDE.

This new laptop is at least twice as fast as the Precision M6700 it replaces, but the compile times are at least twice as long.

BlinkTest takes well over 8 sec to compile, even with no changes (just pressing F7).  I have uploaded a ZIP file containing verbose outputs from two consecutive compiles with no code changes between compiles.

What am I doing wrong here?

TIA,

Frank

  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12192
Location: United Kingdom
Joined: Apr 10th, 2010
Re: VS2017 CE long compile times with new installation
Reply #1 - Jul 3rd, 2018 at 10:59am
Print Post  
This is normally caused by virus checkers or anti-malware software.

Try switching off "vMicro>Compiler>Shared Cache For Cores"

Otherwise you just need to exclude the temp build folders from your virus checker.
  
Back to top
IP Logged
 
FrankP
Senior Member
****
Offline


Posts: 251
Joined: Oct 19th, 2011
Re: VS2017 CE long compile times with new installation
Reply #2 - Jul 3rd, 2018 at 11:00pm
Print Post  
Tim,

Yep - you were right; my AV was also brand-new and not excluding anything by default.  When temporarily switched OFF, BlinkTest compile time was reduced to about 2 sec.   

I *think* that disabling 'Shared Cores Cache' further reduced it to less than 1 sec - hooray! Wink

Thanks again

Frank
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12192
Location: United Kingdom
Joined: Apr 10th, 2010
Re: VS2017 CE long compile times with new installation
Reply #3 - Jul 5th, 2018 at 10:43pm
Print Post  
Great. yes the shared cache  has to copy the core.a to the build folder each time which might take a second. However new projects and examples will compile in a couple of seconds as opposed to 20+. The shared cache also dramatically reduces disk usage because not shared has a copy of the compiled core for every project+board+configuration.
  
Back to top
IP Logged
 
FrankP
Senior Member
****
Offline


Posts: 251
Joined: Oct 19th, 2011
Re: VS2017 CE long compile times with new installation
Reply #4 - Jul 6th, 2018 at 12:06am
Print Post  
Tim@Visual Micro wrote on Jul 3rd, 2018 at 10:59am:
This is normally caused by virus checkers or anti-malware software.

Try switching off "vMicro>Compiler>Shared Cache For Cores"

Otherwise you just need to exclude the temp build folders from your virus checker.


Tim,

At present, I am temporarily disabling run-time scans entirely, as I'm not sure where the temp build folders are - can you tell me that?

TIA,

Frank

  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12192
Location: United Kingdom
Joined: Apr 10th, 2010
Re: VS2017 CE long compile times with new installation
Reply #5 - Jul 7th, 2018 at 11:39am
Print Post  
If revie the vMicro menu it will help you. Switch on verbose then you get to see all paths in the build output. There is also an option to always show the build folder in the the compiler output

In the build output look for a "Coping cached core" message when Cached Cores is enabled.
  
Back to top
IP Logged
 
FrankP
Senior Member
****
Offline


Posts: 251
Joined: Oct 19th, 2011
Re: VS2017 CE long compile times with new installation
Reply #6 - Jul 7th, 2018 at 8:03pm
Print Post  
Tim,

Ty - will do

Frank
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint