LabVIEW
Executable "Vi is not loadable"
The VIs probably have the option "separate compiled code" on. This means the VIs don't contain compiled code.
An exe needs compiled code.
Either turn that option off and try your luck (there are many more problems waiting for you, like missing (compiled) dependencies) OR compile the vilibs to ppls.
Search LabVIEW like a graph!
@Yorick_Noel wrote:
This option is off. I had this idea and AI tell me too to disactivate this option. So I did on the libs and mains VI of the lib (singleton, cloneable and app main)
Ok, but ALL dependencies, incl compiled code, need to be accessible to the executable.
This includes vilib VIs, subVIs etc.
The search path of the exe is completely different then the search path of the project.
You should be able to get the exe to run source. This used to be the way to make plug ins (15 years ago). It was never easy though. Most people switched to ppls (, that are also not easy 🙄).
You can make a source distribution. This should include all dependencies. Maybe not as a final solution, but maybe you can find missing dependencies that way.
.png){kind=link}
.png){kind=link}
wiebe@CARYA wrote:
The VIs probably have the option "separate compiled code" on. This means the VIs don't contain compiled code.
An exe needs compiled code.
Either turn that option off and try your luck (there are many more problems waiting for you, like missing (compiled) dependencies) OR compile the vilibs to ppls.
I think that flag only matters when you build an executable that calls an external VI because it can't use the RTE for that. Or something to that effect?
@billko wrote:
wiebe@CARYA wrote:
The VIs probably have the option "separate compiled code" on. This means the VIs don't contain compiled code.
An exe needs compiled code.
Either turn that option off and try your luck (there are many more problems waiting for you, like missing (compiled) dependencies) OR compile the vilibs to ppls.
I think that flag only matters when you build an executable that calls an external VI because it can't use the RTE for that. Or something to that effect?
Pretty much.
To execute a VI, it needs to be compiled.
If the compiled code in "external" (in the compile cache) it's not in the VI. The development system can (re)compile the VI, the RTE can't. IIRC there is a key that allows the exe to access the compile cache, but haven't tried it. This is a hacky way that might get an exe running, but only on a PC where the IDE compiled it.
Another issue is dependencies. VIs that are in the exe will be available to dynamically loaded VIs, but if the dynamic VI uses other subVIs that can't be found or loaded, it won't run.
@Yorick_Noel wrote:
Sorry for my late reply
My executable is now working since last night and I didn't understand why (totally normal, I'm fine).
I change this 3 things :
- I generate the build on a folder that is not synchronised on my network.
- I moved all my generic VIs to the project folder (used on various projects)
- I installed NI MAX (in anticipation of generating reports for support)
Wow, that is a crazy mindset. Your reaction should be PANIC because if you don't know why it started working suddenly, it will happen again.
@billko wrote:
@Yorick_Noel wrote:
Sorry for my late reply
My executable is now working since last night and I didn't understand why (totally normal, I'm fine).
I change this 3 things :
- I generate the build on a folder that is not synchronised on my network.
- I moved all my generic VIs to the project folder (used on various projects)
- I installed NI MAX (in anticipation of generating reports for support)
Wow, that is a crazy mindset. Your reaction should be PANIC because if you don't know why it started working suddenly, it will happen again.
Running VIs from an executable is a sure path to failure. We (the community, incl. me) have been doing it for decades, because there was no alternative.
It has always been unpredictable and never pleasant.
It might "work" now, but the moment you add a vilib VI that isn't in your executable, the load will fail. And I can tell you right now this won't happen until it's the most inconvenient time for it to happen.
