Building Executable - how long should it take?

[michelleann]

Hi there,  I'm trying to build an executable in LabVIEW NXG but it's taking quite a while and LabVIEW's CPU usage has been pretty close to 0% throughout.  How can I be sure this is working?

My program has 10 sub VIs ranging from 25-60 KB, 1 sub VI at 163 KB and the main VI at 153 KB.  Building was taking nearly 3.5 hours before I cancelled it.  Is over 3.5 hours a reasonable amount of time for this size of program, or is something else probably wrong?  I have seen mention of hierarchy or 'levels' of VIs - maybe that has something to do with it but I'm not sure exactly what it means. 

Any help is greatly appreciated.  Thank you!

[Kyle97330]

I can't speak for NXG but regular LabVIEW generally takes just a few minutes at most unless your program is truly massive.

When people talk about VI hierarchy, they mean that your subVIs have other subVIs in them, which have more subVIs in them, and so on.  So the actual size of your program is determined by the total number of subVIs and their contents, not just the main VI and the subVIs you personally created.

The only way your project of 12 VIs could be large enough to take over 3.5 hours would be if one of your VIs referenced another VI that loaded tens of thousands of subVIs.  I suspect there's something wrong with your program or with NXG.  Probably NXG, as it's new and all the edge-case bugs haven't been worked out yet.

Is your project confidential or is it something you could post?

[mregione]

Hi michelleann,

Thanks for trying out building executables! I agree with Kyle's response above; 3.5 hours is much longer than any build time I've seen and your observation that NXG is not utilizing much CPU suggests that you probably encountered a bug. If you could share your project and source with us, we can take a look and see if we can suggest a workaround that allows you to successfully build. Sharing will also help us to fix the issue in a future version of NXG.

By the way, can you also share what version of NXG you are using?

Thanks,

M.Regione

LabVIEW R&D

[michelleann]

Thank you both for your responses!!

I ended up simply restarting LabVIEW and the executable built successfully in exactly 1 second.  I've found that this has often worked in NXG - when it starts acting strangely, simply restart LabVIEW and things are magically fixed.  So - feel a little dumb for not trying this out before I posted but at least it's a simple solution!! 

Thanks again 🙂

[michelleann]

Oh, and I'm using NXG 2.1.1

[mregione]

Exactly one second sounds much more in-line with my expectations 🙂 

I'm glad to hear you got your application working through restarting NXG. Even still, I know these type of intermittent issues are quite frustrating to hit during development. We'll continue striving to reproduce this build inconsistency so that it can be addressed in a future release; if you happen to hit it again and are willing to post or direct-message me your project I would really appreciate it.

Happy coding!

Michael.R

LabVIEW R&D