include directories with files when building Installer

[nyc_(is_out_of_here)]

---

@mikeporter wrote:
Yes, there needs to be at least one file. It can even be a text file.

Mike...

---

I ended up putting in a text file called empty.txt  🙂

[nyc_(is_out_of_here)]

Now, I am getting another error.

We use a 3rd party driver called labSSH.

When I build the executable, the labSSH.dll is placed in the data subdirectory under the executable.

Yet, when I start up the executable, I get the error message that the DLL cannot be found.

What do I have to do to make the executable aware that the DLL is the data subdirectory?

[chembo]

I use also 3rd party DLLs. You can copy it to the 'system32' if this is possible in your case. Or it may help if you add the location of the DLL to the 'path' environment variable.

[altenbach]

It should find it.

Do you do anthing unusual, e.g. calling the dll by using the "specify path on diagram" option?

(In this case you need to strip the path correctly relative to the executable, of course).

 

[nyc_(is_out_of_here)]

The DLL is installed in C:\Program Files\National Instruments\LabVIEW 2013\resource

The wrapper VIs that call the DLL are installed in C:\Program Files\National Instruments\LabVIEW 2013\vi.lib\Labwerx\labSSH

The wrapper VIs are in labSSH.lvlib

I keep trying to have the DLL installed in the same directory as the executable, which is what I see the previous programmer did.

But the Application Builder is not cooperating.

It keeps placing the DLL in the data directory.

[altenbach]

Why would you install VIs into vi.lib? Does that even exist on computers that only have the runtime engine installed?

[nyc_(is_out_of_here)]

---

@altenbach wrote:

Why would you install VIs into vi.lib? Does that even exist on computers that only have the runtime engine installed?

---

The source VIs are in the vi.lib

I was explaining what they are.

The Application Builder keeps placing the DLL into the data subdirectory under the executable.

I can't figure out how to make the Application Builder place the DLL in the same directory as the executable.

Any ideas?  This is all that I need to do and the program runs.

[altenbach]

Sorry, I have never tried to place them elsehwere. It should definitely find it if it is in the data folder. Something else must be wrong...

[nyc_(is_out_of_here)]

In the installer, I placed the DLL into the same directory as the executable.

Not pretty. But it works.

I have an email to LabWerx who sells labSSH.

[chembo]

You can create a destination in the builder which points to your application folder, i.e. if the application is in c:\app1, then you can create destination which points to this folder.

Then add the dll in the always included files and set the source file location for the dll to the already created destination.