Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
7 ratings:
 2.57 out of 5     Rate this Document

Managing the Resulting Files from a Build Containing LabVIEW Classes

Primary Software: LabVIEW Development Systems
Primary Software Version: N/A
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:
When building an executable using a LabVIEW 8.6.1 (or prior) class dependent architecture, one example includes the Report Generation Toolkit VIs in LabVIEW 8.6, there are multiple directories containing support VIs that are included. Is there a way to minimize the number of files that are created or consolidate the files to distribute?

Solution:
In LabVIEW 8.6 and earlier, the Application Builder saves VIs and library files in a flat list within the application and saves VIs with conflicting filenames outside the application in separate directories. The Application Builder no longer moves VIs with conflicting filenames outside of stand-alone applications, shared libraries, or Web services for build specifications you create in LabVIEW 2009. Because of this change, the following solution is only applicable to LabVIEW 8.6.1 and earlier. See LabVIEW 2009 Help: LabVIEW 2009 Features and Changes for more information.

When building applications or shared libraries that use LabVIEW classes, Application Builder will place the files that have name conflicts in folders outside of the application. This is due to the mechanism that is used to build applications in LabVIEW. However, in certain cases you may want all files to be within the application.

To minimize the number of files generated, you can follow this approach to create LLBs with .dll extensions which will mask the behavior from the end user.
  1. Move any LabVIEW Classes that are contained within the Dependencies section of the LabVIEW Project to the same level as the top level VI by right-clicking My Computer»Add»File then browse to C:\Program Files\National Instruments\LabVIEW x.x\vi.lib for the LabVIEW Class of interest.
  2. Configure the properties for the Application you are going to build by right-clicking Build Specifications and selecting New»Application (EXE).
  3. In the My Application Properties page, select the Destinations page.
  4. Create a new destination and set its type as LLB.
  5. Repeat Step 4 for each LabVIEW class that will be part of the application.
  6. In the Destination Path control, change the extension from .llb to .dll. The destination will still be an LLB but the resulting file will have the .dll extension.
  7. In the Source File Settings page, select each LabVIEW class in the Project Files section, and select the appropriate destination that was created from the Destination drop-down menu.
  8. You can verify the output in the Preview page.





Related Links:
LabVIEW 2009 Help: LabVIEW 2009 Features and Changes
KnowledgeBase 496CKS45: Error When Building an Executable Containing LabVIEW Classes

Attachments:
app_properties.PNG

Report Date: 08/21/2008
Last Updated: 08/20/2009
Document ID: 4OKDCDES

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit