04-28-2008
01:00 PM
- last edited on
04-09-2026
01:28 PM
by
Content Cleaner
I am having an issue with a shared variable in my application. This application is built into an installer to be installed on a machine without labview. After looking around I came across this link and think that it is close to what I need. The only difference is that the link refers to an executable, and the following step is what is throwing me off:
Since I am not using an executable, I do not have a "data folder" to point the invoke node towards. I am sure that other people must have run into this problem and am very interested to hear how it was solved.
Cheers!
Solved! Go to Solution.
04-28-2008
02:43 PM
- last edited on
05-28-2025
12:10 PM
by
Content Cleaner
As a follow up I found this link which may shed a little bit more light on the situation.
If you plan to distribute a stand-alone application that uses shared variables, do not include the .lvlib file in an LLB or in the executable. Use the Source File Settings page of the Application Properties dialog box to change the Destination of the .lvlib file to a destination outside the executable or LLB. You can deploy the shared variables in two ways:
If you plan to distribute a shared library that uses shared variables, do not include the .lvlib file in the shared library. Use the Source File Settings page of the Shared Library Properties dialog box to change the Destination of the .lvlib file to a destination outside the shared library.