PathToUNIXPathString.vi

[aartjan]

Aahh! It's happening again: I want to make a build using built-in zip functions and Labview refuses, stating it is missing PathToUNIXPathString.vi in library C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Platform\CFURL.llb

Sure, the directory doesn't even contain this llb. 

I think built-in protected VI's should not have this kind of problem. Anyone have the proper solution to this? (Aside from simply replacing by OpenG)

Using LV8.6 on XP

[smercurio_fc]

As far as I know, that VI only exists for a Mac. Yet you say you're running under XP. Well, that's certainly confusing.

[aartjan]

Nothing confusing if you ask me. I really don't care which llb's support the labview functions. They should all work. The function uzip.vi is protected nowadays, but I am pretty sure it has some dysfunctional conditional disable structure

I have this issue a long time ago. Guess I should post it in the monthly bug report instead.

[Jim_Kring]

What's probably happening is that there is a Conditional Disable structure that has a call to this VI in the Mac frame of the CD structure (since the zip functions probably require Darwin paths).  This VI (PathToUNIXPathString.vi) is missing on Windows, which is causing the builder to barf when trying to read the linker info of zip functions.

Message Edited by Jim Kring on 09-30-2008 11:11 PM

[slrtrn]

Hello, Do you have any solution for missing PathToUNIXPathString.vi in XP when I build application. I am using LV 8.5 Thank you

[Jim_Kring]

---

slrtrn wrote:
Hello, Do you have any solution for missing PathToUNIXPathString.vi in XP when I build application. I am using LV 8.5 Thank you

---

The solution that I use is to copy the Mac VIs to Windows, but strip out all the code, so that the VIs are not broken.

Actually, I keep all of these VIs in a VI Package (ni_lib_mac_osx_placeholders-1.0-1.ogp) that I install with VIPM -- this package only installs on Windows and Linux, and places non-functional stubs in the place of VIs that are only present on LabVIEW for Mac.

Message Edited by Jim Kring on 03-28-2009 01:39 PM

[rolfk]

---

Jim Kring wrote:

---

slrtrn wrote:
Hello, Do you have any solution for missing PathToUNIXPathString.vi in XP when I build application. I am using LV 8.5 Thank you

---

The solution that I use is to copy the Mac VIs to Windows, but strip out all the code, so that the VIs are not broken.

Actually, I keep all of these VIs in a VI Package (ni_lib_mac_osx_placeholders-1.0-1.ogp) that I install with VIPM -- this package only installs on Windows and Linux, and places non-functional stubs in the place of VIs that are only present on LabVIEW for Mac.

Message Edited by Jim Kring on 03-28-2009 01:39 PM

---

Or in this specific case use the OpenG functions. I can't guarantee that they work in all situations without any problems, but am willing to work on any issue that is found in a reasonable timeframe, and last but not least the Vis and even the C source code are Open source and not password protectet

Rolf Kalbermatter