build exe is working but the program is not

[Susanne1709]

that's not possible. As you can see from the screenshot, the folder dependencies is not available in the Source Files folder. Don't know why... do you have an idea?

[Blokk]

changed to private msg.

[Susanne1709]

does nobody know why the dependencies are not shown to select as included?

[dan_u]

The dependencies are included automatically. You only have to explicitely include items which are called dynamically (using VI server). SubVIs are always included automatically.

[Susanne1709]

obviously is there something wrong because when I put the folder in the windows explorer in the same folder where the .exe is built, then the program is working. But the client shouldn't see this folder with loads of VIs, ctls etc.

So how I can get this folder IN the exe that the program is working fine?

[Yamaeda]

---

@Susanne1709 wrote:

obviously is there something wrong because when I put the folder in the windows explorer in the same folder where the .exe is built, then the program is working. But the client shouldn't see this folder with loads of VIs, ctls etc.

So how I can get this folder IN the exe that the program is working fine?

---

Set up a folder as Destination in the build and link a folder to it in the Source distribution settings.

/Y

[Susanne1709]

please see screens attached what i do. I have a destination folder for the build (this is working fine). Should I link the dependencies to "same as caller", "application.exe"... or what do you mean?

[Sam_Sharp]

I suggest you read the help for the application builder - it will explain all of the options and what they mean.

You can create additional destination folders in the destinations page and then they will appear under the 'destination' drop-down box on the source files page. You can then put the files that are missing into that new destination directory.

Like I said before - if you want all of the VIs to be contained inside the .exe then you will need to change how the VIs are referenced in your code. If you save your VI for LV2013 then I can have a look to see if that is the issue.

[Susanne1709]

thanks. I did it and it worked first fine. Then I get this error: the gpib interface is missing...

[Sam_Sharp]

Ignore the GPIB error...sometimes LabVIEW error codes are used for different reasons. I think the error is 'File not found'...and the path to the missing file is shown at the bottom of the screenshot.

Looks like you need to include that text file in your build specification as well.