Hi Folks, I am trying to build a very large application which is based on GOOP2 classes. We have about 250 classes which are all included in the lvproj as dynamic VIs. The project definition puts just the top-level VI plus 2 classes in the executable and then all other classes go to the support directory. The fact that this is GOOP2 is probably immaterial since these are just basically groups of VIs... nothing special... just lots and lots of them. Up until our previous code release the project built OK under LV 8.2.1. However our latest version (which only adds 4 classes and a few minor code changes) fails in 8.2.1 with a "Memory Full" error. In an attempt to move forward, I have built also in LV 8.5 which again builds OK up to the last source release but fails with the new version, this time with a "File not found" error. Also, when it does fail, LV typically crashed (both in 8.2.1 and 8.5) and when I restart LV it goes through the "investigate error" dialog. The errors logges are always the same... "DWarn: You filled the image table" with the error at: //labview/branches/Jupiter/dev/source/manager/image.cpp#45. This may be a red herring but it does happen consistently. My current suspicion is that there's a hard upper limit fo the number of VIs that can be declared as "Dynamic, always include". Is this possible? Any suggestions would be very welocome as this is a complete show-stopper for us.

LabVIEW

Application builder fails with "File Not Found"

Author

Ok... so that has worked on both LV versions. So there clearly is a max limit in the dynamic VIs listing since all the VIs which I have removed will have been re-included as dependencies.

I will take this up with my local NI representitive.

Message 11 of 11

(414 Views)

LabVIEW

Application builder fails with "File Not Found"

Re: Application builder fails with "File Not Found"