That is helpful in more ways than one. The virus checker is concerned anytime disk activity is taking place, so this also points in the direction of overly disk bound activity.
The LV build used to be so simple. LV VIs are already compiled and the .o is bound inside of them. The files were aggregated into a primitive zip called an LLB, that was attached as data to the end of a tiny EXE wrapper that knew how to load the LV runtime engine, and we were off to the races. If you wanted it smaller, the other parts of the VI were stripped of diagram and some panel info.
With libaries, lots of things changed while I wasn't looking, so let me investigate. I'd like it to take less than a minute. I don't see why the build should be slower than the download.
By the way, noticed in my other post that I had a typo
Quote:
|
day jog kept getting in the way
|
Hah, day job is what was getting in the way, I haven't jogged in years.
Greg McKaskle