From: Gee Chin Lin on
Hi:
 
I installed Labview 8.2 Pro Edition to a new Windows XP SP2 PC. I created a simple vi making use of C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\Analysis\6fits.llb\Linear Fit.vi. I then build the vi to an executable file. I ran it on a target system but was getting Missing subvi as shown in attachment files.
 
Initailly my target system has the following installed:
Labview 6.0
Labview RT 6.0
Labview RT 6.1
Labview RT 7.1
 
I then installed Labview RT 8.2.
I am currently evaluating converting all my project written for Labview 6.02 to Labview 8.2 and encountered the above problem. I also notice that the time taken to build an .exe file in Labview 8.2 take much longer time than Labview 6.02. My project took about 12 minutes to build in Labview 6.02 but 30 minutes in Labview 8.2.  Furthermore there is no individual control (remove/show panel, run when open) for the subvi in Labview 8.2.
 
Thank you.
 
Chin Lin


Missing Subvi.JPG:
http://forums.ni.com/attachments/ni/170/226748/1/Missing Subvi.JPG


Missing Subvi2.JPG:
http://forums.ni.com/attachments/ni/170/226748/2/Missing Subvi2.JPG
From: cphuong on
Hi Chin Lin,

Are you building your exe file from the Project Explorer?  I would
recommend using the Project Explorer when building exe files in LabVIEW 8.0 and
later.  The Project Explorer allows you to group all VI's and sub-VI's. 
In addition, this method allows you to see everything that is being included in
the exe file. 

When you build your exe file from the Project Explorer, take a look at the
Generate Preview Option (shown below) to ensure that all the necessary support
files have been included. 
<img src="http://forums.ni.com/attachments/ni/170/227022/1/GeneratePreview.JPG">


The options (remove/show panel, run when open) for sub-VI's
are located in that sub-VI under File �
VI Properties � Execution.

Please let me know if you have any more questions.&nbsp; Best of luck on your
application, and have a great day!!



Message Edited by cphuong on 01-30-2007 09:53 PM


GeneratePreview.JPG:
http://forums.ni.com/attachments/ni/170/227022/1/GeneratePreview.JPG
From: Gee Chin Lin on
Hi Ching P.:
&nbsp;
Thanks for your reply. I&nbsp;was using Project Exprorer. The missing subvis are actually from vi.lib. I also did&nbsp;expand the dependency folder and saw all the missing subvis in it. Aren't these VIs will become part of the .exe after build? Or will they become external dependency file? Do I need to manually include them in the Project Explorer? I then try to build the installer from the .exe file and with only the RunTime engine 8.2 included (selected from Additional installer option) and it works at the target PC. So I don't know what is the different between:
&nbsp;
build an .exe and run it on a PC with the RunTime engine 8.2 pre installed&nbsp;&nbsp;&nbsp;&nbsp; AND
build the installer with the RunTime engine 8.2 included and install and run it on a PC
&nbsp;
I also did try to build the installer wihtout the RunTime engine 8.2 included and install and run it on a PC with the RunTime engine 8.2 pre installed. But it did not work.
&nbsp;
For the 2nd part, I found the configuration option for the subvi as you mentioned below. But it is still different from 6.02 application builder where this option is available&nbsp;in the builder windows itself. It is under VI setting tab. I still find the 8.2 Project Explorer very slow when I try to navigate around with the available option exspecially when I click the properties of a builder specification and&nbsp;also when I click cancel and OK button afterward.
&nbsp;
Thank you.
&nbsp;
Chin Lin
From: cphuong on
Hi Chin Lin,

One other thing to try manually add the NI_AALPro.lvlib as a support file in
the Application Builder Wizard by first putting the library in the
project.&nbsp;

With regards to your other question about the speed of the application builder,
how large is your application?&nbsp; Also, how much available RAM do you
have?&nbsp; While the application builder runs, it stores a copy of each VI
that is part of the application in memory.&nbsp; If you have a very large
application or not enough RAM, this can slow your PC down.&nbsp;

How are you determining that it takes longer to build an application in LabVIEW
8.20?&nbsp; Are you trying to build an application that you once built in
LabVIEW 6?&nbsp; Is it the same exact application?&nbsp;

I wish you the best of luck on your application, and hope to hear from you
soon!!
From: Gee Chin Lin on
Hi Ching P.:
I tried adding the NI_AALPro.lvlib to the project as the support file but getting this error when building the .exe:"Polymorphic VIs cannot be used as Startup/Exported or Dynamic VIs for applications or shared libraries.C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\analysis\_algsub.llb\Trace.vi"
I added the NI_AALPro by doing:1. Right click on My Computer-&gt;Add File...2. Select the NI_AALPro.lvlib from NI folder.3. Under Build Specification, right click on my project -&gt;properties.4. Under the Source Files , select NI_AALPro.lvlib. Move it under Dynamic VIs and Support Files.5. Under the Source File Settings, select NI_AALPro.lvlib. Under Destination to apply, I selected &lt;my project name&gt;.exe.6. Build the .exe.
At step 5, I also tried selecting the Support Directory and failed also.I remember I read it some where which mentioned that for Polymorphic VIs, we can only include the instand of the VI but not the VI itself. But how to include just the instand of the VI?
My actual project .exe file size is about 40MB when compile under Labview 6.0.2. When using Labview 8.2, the size is about 27MB. The project that I build using Labview 6.0.2 &amp; Labview 8.2 are the same project but with slightly different due to ongoing modification. But they should not differ much on the building time. My system is a Dell Precision PWS380 Pentium 2.8GHz with 1GB RAM. I noticed that a few times that the build time took only about 14 minutes to complete which is close to using Labview 6.0.2 (13 minutes). But most of the time is slow (about 25 - 30 minutes). Need more time to verify on this.
Thank you.Chin Lin