Your main VI, once compiled into an executable, is able to open and run VIs
as files or in LLBs.
Plug-ins VIs do not need any special process to be run by a built
executable.
The main thing to care about is to make sure that the path to plug-in VIs is
correct and that all needed VIs are present on the target machine and
located in a folder included in the search paths.
VIs are ALWAYS compiled to the current platform when saved on disk so they
can be run by the Run-Time Engine. However the Run-Time Engine can only run
VIs that have been compiled/saved under the same LabVIEW version and
platform e.g. the Windows RTE 6.0.2 can only run VIs saved under LabVIEW
6.0.x for Windows.
Jean-Pierre Drolet
Scientech R&D
"pk"
a écrit dans le message news:
5
06500000008000000D2220000-993342863000@exchange.ni.com...
> Hi all,
>
> So far I have done all my Labview programming using the full
> development version. All my programs are files of type *.vi and get
> compiled at run time. One of my programs uses the concept of plugins,
> i.e. the main VI reads a certain directory and opens a reference to
> VIs contained in that directory. I would like to know whether this
> plugin concept still works after converting the main VI to an
> executable. Would this necessitate to convert the plugin VIs to *.exe
> files or can a Labview executable main VI still use uncompiled
> *.vi-files as sub-VIs?
>
> Any help appreciated
>
> Paul
