Symbolic path: Difference between revisions
mNo edit summary |
changed all instances of "pseudopath" to "symbolic path" due to page rename. Added external link to "LabVIEW Help: Using Symbolic Paths" |
||
| Line 1: | Line 1: | ||
When files are located beneath certain special folders, callers that link to these files will link to them using a '' | When files are located beneath certain special folders, callers that link to these files will link to them using a ''symbolic path'', rather than an absolute or relative path. The ''symbolic path'' will be relative to the special folder. The following table lists these special folders and their ''symbolic path'': | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! | ! symbolic path | ||
! description | ! description | ||
! actual path | ! actual path | ||
| Line 28: | Line 28: | ||
|} | |} | ||
Note that some of these can have the actual path changed by changing the settings in '''Tools>>Options'''. The whole point of the | Note that some of these can have the actual path changed by changing the settings in '''Tools>>Options'''. The whole point of the symbolic path is to indicate "load from whatever location this path is currently defined to be." | ||
For example, if you have a VI located in the following location: | For example, if you have a VI located in the following location: | ||
| Line 34: | Line 34: | ||
<LabVIEW>\user.lib\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi | <LabVIEW>\user.lib\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi | ||
Callers will link to this VI using the following '' | Callers will link to this VI using the following ''symbolic path'': | ||
<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi | <userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi | ||
'' | ''symbolic path'' are not generally encountered. They are used mostly under the hood of LabVIEW, for example, when using the Application '''Linker:Read Info From File''' and '''Linker:Write Info To File''' methods. | ||
== When Using Modules (FPGA, RT, etc) == | == When Using Modules (FPGA, RT, etc) == | ||
A | A symbolic path may resolve to different actual files on disk depending upon which target the VI is loaded into. So a VI that is written to use <vilib>\a.vi may use <labview>\vi.lib\a.vi when loaded for the desktop target, but may use <labview>\vi.lib\fpga\a.vi when loaded for the FPGA target. | ||
== See Also == | |||
* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/using_symbolic_paths/ LabVIEW Help: Using Symbolic Paths] | |||
Revision as of 20:41, 7 May 2007
When files are located beneath certain special folders, callers that link to these files will link to them using a symbolic path, rather than an absolute or relative path. The symbolic path will be relative to the special folder. The following table lists these special folders and their symbolic path:
| symbolic path | description | actual path |
|---|---|---|
| <userlib> | User Libraries | <LabVIEW>\user.lib |
| <vilib> | NI Libraries and Addons | <LabVIEW>\vi.lib |
| <instrlib> | Instrument Drivers | <LabVIEW>\instr.lib |
| <help> | Help Files | <LabVIEW>\help |
| <menu> | Palette Menus | <LabVIEW>\menus |
Note that some of these can have the actual path changed by changing the settings in Tools>>Options. The whole point of the symbolic path is to indicate "load from whatever location this path is currently defined to be."
For example, if you have a VI located in the following location:
<LabVIEW>\user.lib\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
Callers will link to this VI using the following symbolic path:
<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
symbolic path are not generally encountered. They are used mostly under the hood of LabVIEW, for example, when using the Application Linker:Read Info From File and Linker:Write Info To File methods.
When Using Modules (FPGA, RT, etc)
A symbolic path may resolve to different actual files on disk depending upon which target the VI is loaded into. So a VI that is written to use <vilib>\a.vi may use <labview>\vi.lib\a.vi when loaded for the desktop target, but may use <labview>\vi.lib\fpga\a.vi when loaded for the FPGA target.