LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Executable won't automatically load one dependency

Solved!
Go to solution

DerrickB, 

 

My executable seemed to be pulling them to the correct place (except the vi that's the subject of this post), but it seems like Paul's saying that that vi was never stored inside my project so that's why it's causing errors. I'll fix that. 

But when I compact all my files to a zip file (i.e., if I need help again and want to upload my whole project), how do I get it to open to a know path on all systems? Is there a link or other resource you can direct me to so I can avoid confusion in the future? Or is there an easier way to upload? 

0 Kudos
Message 11 of 12
(422 Views)

@krogue wrote:

DerrickB, 

 

My executable seemed to be pulling them to the correct place (except the vi that's the subject of this post), but it seems like Paul's saying that that vi was never stored inside my project so that's why it's causing errors. I'll fix that. 

But when I compact all my files to a zip file (i.e., if I need help again and want to upload my whole project), how do I get it to open to a know path on all systems? Is there a link or other resource you can direct me to so I can avoid confusion in the future? Or is there an easier way to upload? 


You don't need to explicitly include the file in your buildspec.  The problem is just that the app builder gets confused when the destination is under <instrlib>.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 12 of 12
(418 Views)