Application Builder locking up LabVIEW

[LLindenbauer]

Dear all!

I frequently have to compile some rather voluminous projects where a single build takes about 1-2 hours. During this time, LabVIEW (LV16, 32 bit, Win10) becomes unresponsive to the point where even just moving the progress bar for the build takes about one minute (!) to register. Also, the build process seems to only use one CPU core.

I did a quick look through the forums and help files and found no mentions of this behaviour, so maybe I have configured something incorrectly?

Is it possible to have LabVIEW compile using a different thread so that one can continue coding in another project?

Is it possible to use more than one core when compiling?

[LLindenbauer]

Is this an unreasonable thing to ask? Did I miss something obvious in the documentation?

[Yamaeda · Accepted solution]

You're correct, the compilation only uses 1 core, and the system is quite unresponsive while doing it.

I remember from some earlier discussion that it's very hard to make compilation multithreaded due to dependencies, as mentioned in this thread: https://stackoverflow.com/questions/4430001/which-x86-c-compilers-are-multithreaded-by-itself

To reduce compile time you can make use of packed libraries. Assuming you have some libraries in your code, they can be precompiled to a lvlibp and subsequently only linked in the final build. As that's probably more mature code that don't change that often it should save you some time.