Symbolic path: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
When files are located beneath certain special folders, callers that link to these files will link to them using a ''pseudopath', rather than an absolute or relative path. The ''pseudopath' will be relative to the special folder. The following table lists these special folders and their ''pseudopath': | When files are located beneath certain special folders, callers that link to these files will link to them using a ''pseudopath'', rather than an absolute or relative path. The ''pseudopath'' will be relative to the special folder. The following table lists these special folders and their ''pseudopath'': | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 36: | Line 36: | ||
<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi | <userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi | ||
'pseudopath'' 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. | ''pseudopath'' 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 pseudopath 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. | A pseudopath 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. | ||
Revision as of 20:38, 7 May 2007
When files are located beneath certain special folders, callers that link to these files will link to them using a pseudopath, rather than an absolute or relative path. The pseudopath will be relative to the special folder. The following table lists these special folders and their pseudopath:
| pseudopath | 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 |
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 pseudopath:
<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
pseudopath 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 pseudopath 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.