View Single Post
  #5   Spotlight this post!  
Unread 04-03-2009, 19:31
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Time to build cRIO LabVIEW code

I don't know where the other posts are, but this has come up a number of times. There is a setting in the LV project which should help your build time. The problem is that for some projects it will slow them down and others speed up. On the whole, I've discovered that I'm not very happy with the app building. As mentioned, it copies and saves all files and doesn't do a good job of reusing intermediate files. It has quite of bit of overhead and I haven't been able to find the usual low hanging fruit or hot spot.

The setting to toggle is in the build spec properties. Make sure to right click all the way to the bottom on your FRC build spec. Open Properties. Click to the Additional Exclusions tab. The options to disconnect poly-vis and typedefs seem to have little effect on build time, and are for tweaking the size of the EXE versus taking along the full lib for plug-in support. Similarly, there is a setting to take along only the library elements you use or the full library.

The default for FRC is to take the entire library. This seems to be the fastest option until you start including certain VIs, especially those from the DSP libraries, then the build often balloons to around 20 minutes. At that point it is far better to flip the checkbox and take only the VIs you are using. When not using analysis, this seems to be slower than the original setting. There may also be a combinatorial effect between the lib setting and the polyVI setting. Do not check the subBox under the lib to modify the library.

Greg McKaskle
Reply With Quote