Building an executable hangs Labview

[Rockyenco]

I'm trying to build an executable within LV2017 / 2018 32bit.

When i use a simple vi with just a switch and indicator, it works.

But i'm using the AD2 toolkit from Digilent, and i think this causes it.

It starts to initialize and build, but almost at the end it stops forever.

No error message.

I need to close Labview with Task Manager.

What can i do ....

[FireFist-Redhawk]

The first thing I would do is add NI_AppBuilder_Logging=True token to your LabVIEW.ini to get a detailed build log, then you can go into it after the build gets stuck to see where exactly it got stuck at. Not saying you'll glean any info from the log, but it's a troubleshooting start.

Also, see if you can generate a preview of the build. Whether you can or can't might be helpful info for troubleshooting as well.

Edit: One more thing that may help in troubleshooting is to make an absurdly simple VI that basically has nothing but a loop, a stop button, and a couple VIs from the toolkit in question, and try to build that into an executable.

[pincpanter]

Try to collect more info: does the Preview gives any hint? (not sure if this can help); also, generate the build log file (Category Advanced).

[altenbach]

Good advice so far....

---

@Rockyenco wrote:

It starts to initialize and build, but almost at the end it stops forever.

---

"Forever" cannot be proven unless you really wait forever, which is impossible :D.

Just curious. How long did you wait before giving up?

[billko]

I haven't really seen "forever", but I have seen some "absurdly long" build times!  😄

[Bob_Schor]

You have an external library (from Digilent, as I recall).  You'd like to think that when you build, the Linker will find and link "foreign" libraries and DLLs for you, but that may not always be the case.

You might give Digilent a call and tell them you are having trouble building an Executable while using their modules.  I recall a colleague with third-party LabVIEW compatible devices (things like the NI USB-6009) which had a similar "build" problem, but once we added the correct library to the "Always Included" part of the Build Spec, it went very well.

Bob Schor

[Rockyenco]

Hi.

I tried with a simple vi (Button + indicator) and that builds without an issue in only several seconds.

I can make a preview of the build. (see attached pictures)

The build starts, but got stuck almost at the end. 

" Had It Run for More Than 2 Hours... "

see attached files

---

[billko]

Okay, yes, something seems amiss!  Did you try what Bob suggested?

[Bob_Schor]

---

@billko wrote:

Okay, yes, something seems amiss!  Did you try what Bob suggested?

---

In particular, in the Digilent AD2 Zip file you included, the folder DigilentWF, which seems to contain all of the Digilent VIs needed by Digilent_Waveforms_Stimulus Response (MSI + DIO TOM).vi is missing.

It is extremely difficult for us to really help Forum users (such as yourself) who don't give us the "tools" we need to help you fix your LabVIEW Projects.  I generally suggest that you compress the Folder that contains your Project, which usually includes all of the sub-VIs that you are using, and attach the resulting .zip files.  However, if you are also using external third party routines (such as those contained in DigilentWF), and the problem involves those VIs, it is difficult to diagnose and help you "fix" the problem without your also including those files.

Try my suggestion.  In your Build Specification, include the routines found in DigilentWF in the "Always Included" section.

Bob Schor

[Rockyenco]

I tried Bob's suggestion by adding those external Vi's to the "Always included" section.

But still the same respons.
I already mentioned, but each time i have to close Labview with the task manager......