Close: Load and Save Warning List - while building an Executable

[daveTW]

Hello All,

I'm facing following issue. While building an executable I get several dependency warnings, looking like the one below. The strange thing is, that the new dependency is inside the Exe, where it should be!

Prior to the build I forced a complete recompile by pressing Ctrl+Shift and clicking the Run- button, then saving everything. So, there should all dependencies be saved correctly into every single VI.

What is it I don't understand?

[Norbert_B]

Dave,

is it possible that your build script does not only build an EXE but also some "source distribution" packages? This is ususally the case when creating a build script for plug-in architectures where the individual plugins are placed OUTside the EXE.

Norbert

[daveTW]

Hello Norbert,

I admit, I wouldn't know how to build an executable and a distribution from one build script. To make my settings clear to you, i attach screenshots of relevant pages of the "Build Executable" dialog.

[daveTW]

OK, this is very poor quality, I try it with attached images.

[daveTW]

No 2

But I see, this is not better.

[Norbert_B]

Hm, it seems to be a "clean" build script.

What bothers me is in your very first screenshot, the "affected source" is a VI which is located OUTSIDE of the EXE file (Load Single SE-Pref.vi). That means that if you acknowledge that dialog and save the VI, it will store an incorrect path to that subVI (Read Key(Boolean).vi). That's why i asked about plugins.

Do you have the affected caller open during the build process? If yes, it the "application instance" of this VI the project "KGA Basis Ansteuerung" or is it something else (e.g. Main Application Instance)?

You can see the active application instance for a VI on the bottom left as it moves the horizontal scrollbar to the side.

Norbert

[daveTW]

Hello Norbert,

thank you for your advices. Since the build process was only paused by the Message- Windows, but not aborted, I just clicked them away. After all I deleted the Build entry in my project and created a new one from scratch, and - voilà, everything was fine again.

I made no Backup of my project file, so we won't find out the actual reason for the error messages by looking into the .lvproj - XML text. But for now it's fixed just by creating a new build script.