LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How does path options work ?

Can someone direct me to documentation about use of the Tool->Options Path in LabView. Especially use of Library directory and VI search path, and how these are used when building an application (when and how are paths to libraries used by CLN's updated).

Thank you

frode
0 Kudos
Message 1 of 5
(3,127 Views)
I guess you have looked at the LV help files? If not, there is a page called Path Options page in the index. This tells you about all the options.

However, it doesn't say anything about how these are used when building an application, although i'm not convinced they are used. I thought they were merely for LV to find the files to run the main application environment.

If you can be specific about your problem, maybe i could help in a more direct way?

Kim
0 Kudos
Message 2 of 5
(3,127 Views)
A summary of my problem:
I have a sub folder with a shared library, and lot of VI's using this. When building an application, the application and the shared library get copied/created in the destination folder.
But, when starting the application it starts to search for the shared library. This produces an annoying dialog, and should be completely unecessary as LabView know where it has copied the file.

Any solution to this ?
0 Kudos
Message 3 of 5
(3,127 Views)
Before you create your application, if you 'Save with options', select 'Application distribution', and then tick 'Save entire hierarchy', etc. then you will not need to save the shared library separately as all the vi's will now be saved in just one library.

If you cant do this for some reason, you could try adding the destination directory to your VI search path, but i dont think it will save in the application.

Kim
0 Kudos
Message 4 of 5
(3,127 Views)
After some investigation it turned out to be a bug in LabView (Mac 6.0.2).
It have stored (internally) in some VI's the path to an older version of the shared library (with a different name). LabView tried for some reason to find this first, before it used the correct one that it displayed in the CLN Configure dialog.
I had to create the affected VI's from scratch to get rid of the "virus".
0 Kudos
Message 5 of 5
(3,127 Views)