Vi outside executable won't run - Labview 8.0

Question

Hello.
I have a main program including a set of vi:s. I then have modules that hook into the program using vi:s in the main program.
I call the module from the main program with a open vi reference + invoke node.
#1 Main <- #2 module
And it works great. I then build my main program to a executable and
when I launch the executable (main) there is a popup searching for vi:s
and then it dissapears. The module is not executed.
I logged the error output on the open vi reference in the main program and it states: "Error 1003, could not find subvi:s".
In application.ini i have:
[application]
viSearchPath="/path/path/application/*"
Even if i remove the viSearchPath line the main vi looks for the sub
vis, but Im not sure if its actually looking for the vi:s in my
executable. Is there a way to check that the application is actually
using the application.ini file? Am I doing something wrong? This is
possible right? =)
I'm running Labview 8.2, Linux version.
Any help is more then appreciated.

Answer 1

"Fox_Mccloud" <[email protected]> wrote in message news:[email protected]...
Hello.
I have a main program including a set of vi:s. I then have modules that hook into the program using vi:s in the main program.
I call the module from the main program with a open vi reference + invoke node.
#1 Main &lt;- #2 module
And it works great. I then build my main program to a executable and
when I launch the executable (main) there is a popup searching for vi:s
and then it dissapears. The module is not executed.
I logged the error output on the open vi reference in the main program and it states: "Error 1003, could not find subvi:s".
In application.ini i have:
[application]
viSearchPath="/path/path/application/*"
Even if i remove the viSearchPath line the main vi looks for the sub
vis, but Im not sure if its actually looking for the vi:s in my
executable. Is there a way to check that the application is actually
using the application.ini file? Am I doing something wrong? This is
possible right? =)
I'm running Labview 8.2, Linux version.
Any help is more then appreciated.
Well, it's clear that the exe cannot find some subvi's used by the subvi. Some vi lib vi's are not included in the runtime (e.g. some of the picture control stuff). To be sure, you can save the sub vi as development llb, and include vi library vi's. That should include everything it needs.
Under windows, you can start a VI with the executable. When the exe is running, you can use the command prompt to start a vi in the exe (e.g. c:\test.exe "c:\vi with missing subvis.vi"). This does almost the same as starting a vi dyamically, from the exe. A big difference is that you get a list with all the vi's that are missing in a dialog. Don't know if this works with Linux, but usually this work better...
Another thing is when you use type defs. The exe, by default disconnects the type defs. The vi that is started doesn't. That will conflict. So untag the "disconnect from type defs and polymorphic vis" tag in the app builder (if it's in the linux builder).
Regards,
Wiebe.