Unexpected folders after build

[MimiKLM]

Hi,

I've just performed a build operations. The source code contains LV Report generation toolkit VIs. Instead of expected one exe file I received six subbfolders with Report generation toolkit VIs. 

How can I build one exe only?

K.

[dan_u]

Probably you created a "Source Distribution" build specification instead of an "Application (EXE)" build specification.

Try creating a new build specification for an application.

[MimiKLM]

I made Application (EXE) build specification.

[Wart]

On the advanced tab of the build instructions try unchecking the Use LabVIEW 8.x file layout.  I'm not 100% certain, but I think that'll force everything into the EXE.

[MimiKLM]

There is no option like that.

I'm using LV8.6

[Matthew_Kelton · Accepted solution]

What version of LabVIEW are you using?  Prior to 8.x, LabVIEW didn't support classes, lvlib, etc. so every VI name had to be unique.  When NI introduced classes and lvlib, LabVIEW now had the ability to open VIs with the same name as long as they existed in different classes or lvlibs.

The problem was that they didn't really address this in the EXE build, so the workaround was to create a directory structure mimicking the lvlib or class and the EXE would call the code in the subdirectories.

In LV2009, NI fixed this by creating virtual folders inside the EXE, so you could get back to having all the code inside one EXE.  The flag Wart mentions will cause LV2009 and later to build the EXE the way LV 8.x built it.

So, if you are using LV8.x, you don't really have any choice.  They are ways to mask it a little bit.  I did the method here.  It at least makes it look a little bit better on disk.