Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
This Document is not yet Rated  Rate this Document


How Do I Prevent LabVIEW from Creating a Copy of a DLL When Building an Executable?

Primary Software: LabVIEW Development Systems>>LabVIEW Base Package
Primary Software Version: 8.2
Primary Software Fixed Version: N/A
Secondary Software: LabVIEW Toolkits>>Application Builder

Problem:
I use Call Library Function Node VI to access a dll from my LabVIEW code. If I create an executable from my VI, LabVIEW automatically copies the dll to the data subfolder of my executable’s folder. However, I do not need the extra dll copy.

Solution:
By default, LabVIEW copies external code called by the Call Library Function Node VI when creating an executable. LabVIEW assumes the application will be used on a different target, so it makes sure all supporting files are available. Starting with LabVIEW 8.2, it is possible to hardcode the path to an external dll on the block diagram. This prevents copying the specified dll during the executable generation process. There is no way to bypass the automatic dll copying in LabVIEW 8.0 and earlier. Steps to enable the Specify path on diagram option:
  1. Double click on the Call Library Function Node VI after you place it on the block diagram.
  2. A configuration dialog box pops up.
  3. Select the Function tab.
  4. Check the Specify path or path box.
The Call Library Function Node VI now has one more input – reference. Right-click on the reference input and create a control or a constant. Finally specify the path to the desired dll in the reference control/constant.

Related Links:
Product Manuals: LabVIEW 8.2 Help


Attachments:





Report Date: 01/27/2007
Last Updated: 01/27/2007
Document ID: 45Q2C6LA

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