The Application Directory primitive is giving unexpected output when running inside of a LabVIEW compiled shared library on Linux (so file). I haven't check for LabVIEW built shared library on Windows. Help says that when running in stand-alone app it should return the folder containing the app.When running in a built shared library, it behaves differently, as it returns the path of the so file + relative path of calling VI to the application.

It took some time but I got a response from R&D via (tech support).R&D's statement is : it's expected (but not well documented), that the paths differ between Windows and Linux. But that the behavior is not consistent for static/dynamic calls is not expected. We filed Bug # 2699859 for this. You can search for this number in the LabVIEW Release Notes of new versions to see if this bug was fixed.

LabVIEW

Application Directory primitive bug?

Solved!

Author

Hi Christina,

Is there a way to fix this issue on macOS Tahoe with LabVIEW 2025Q3?

Cheers

We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

Message 11 of 11

(53 Views)

LabVIEW

Application Directory primitive bug?

Re: Application Directory primitive bug?