LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Load warning summary issue on built application

I have a problem when I load up my built application and I can't figure out what's going on.  Here is a portion of the summary, which seems to say that certain paths were expected.  How can I configure my build to know what path to look for without throwing out this warning?

0 Kudos
Message 1 of 6
(2,872 Views)
I changed the destination to Application.exe instead of "support directory".  I was told Support Directory was the way to go.  That appears now to have been misinformation.  Good day.
0 Kudos
Message 2 of 6
(2,869 Views)

Hi Orion,

 

I would need some questions answered first prior to giving any suggestions:

 

1. Are you building an installer or an executable?

2. How many VIs do you have in your project?

3. What additional installers are you using in your project besides the LabVIEW Run-Time Engine?

 

Ipshita C.

 

National Instruments
Applications Engineer
0 Kudos
Message 3 of 6
(2,852 Views)

I am building an application without an installer.

The above picture shows pretty much all of the VIs in my project. 15 or so.

I already have the DSC run-time and the Labview Run time so I didn't think I needed anything else.

0 Kudos
Message 4 of 6
(2,849 Views)

H Orion HE,

 

What version of LabVIEW are you using (and therefore version of the Application Builder and DSC)?

What is your operatng system?

Is "Application.exe" the name of your executable (Target filename) and/or the name of a directory (Destination directory) you saved your executable to?

Are all of the VIs in question subVIs, or are they being programmatically called from your main VI using VI server?

When you run the executable on the development computer, are the same warnings given?

Did you hardcode any VI path names?  (If you put the executable in the same location on your second computer as the first, do the warnings appear?)

 

Kevin S.

Applications Engineer

National Instruments

0 Kudos
Message 5 of 6
(2,822 Views)
Thanks for the help and suggestions.  A Labview engineer helped me just hours before quitting time on thanksgiving eve.  My problem is resolved, it was mostly due to programmatically calling a library that the caller was already inside of.
0 Kudos
Message 6 of 6
(2,819 Views)