View Single Post
  #2   Spotlight this post!  
Unread 21-01-2010, 20:33
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: 64-bit vs. 32-bit Absolute Pathing

Can you be more specific about where and what files?

LV stores references between files in two ways. If the file is inside of one of the special LIB locations, then the path is stored as LIB/blah/foo/bar.vi. If the VI is not in one of those locations, then it is stored relative to the caller.

So, if you move folders of VIs and maintain the relative path, say using a zip or such, the path above should not matter.

When the relative or LIB path doesn't actually point to your VI, LV starts searching using the search path. You can let it search, show it where they are, put the relative paths back, or update the search path to include some of your code directories.

In general, you do not need change where LV is installed, and in fact putting it in the Program Files on a 64 bit machine may be a bad idea if it isn't actually 64 bit. Not sure.

Does that help? If not, give more info.

Greg McKaskle
Reply With Quote