App builder includes library dll

[Malcolm Bebb]

I am trying to build an exe app in LV6i. I am having problems with a couple of dlls, one of which is ours and one an NIDAQ library dll, lvdaq.dll.

App builder includes them as support files, and wants to put them in the data directory.  I want them in a common area, because other apps will use them.

If I leave them in place, the build fails (presumably because of a source/destinationclash). 

If I move the source location, App builder won't find them unless I save with them. I can't edit the app builder field to point it where I want. 

If I save with the "source" location, I can edit the destination location to what I want and the build succeeds, but the program can't find the dlls and won't start cleanly. I have to manually point to them on startup. 

Am I doing something stupid? (my head is spinning) I'm quite happy for App Builder just to ignore them and to install them manually on the target machine. 

It works fine when run in the development environment (base) from the vis. 

Malcolm

[rolfk · Accepted solution]

---

Malcolm Bebb wrote:

I am trying to build an exe app in LV6i. I am having problems with a couple of dlls, one of which is ours and one an NIDAQ library dll, lvdaq.dll.

App builder includes them as support files, and wants to put them in the data directory.  I want them in a common area, because other apps will use them.

If I leave them in place, the build fails (presumably because of a source/destinationclash). 

If I move the source location, App builder won't find them unless I save with them. I can't edit the app builder field to point it where I want. 

If I save with the "source" location, I can edit the destination location to what I want and the build succeeds, but the program can't find the dlls and won't start cleanly. I have to manually point to them on startup. 

Am I doing something stupid? (my head is spinning) I'm quite happy for App Builder just to ignore them and to install them manually on the target machine. 

It works fine when run in the development environment (base) from the vis. 

Malcolm

---

If you want app builder to ignore them you best copy them into the Windows or System path and delete any other copies on your development machine. DLLs located in one of these locations will be ignore by app builder as being provided by the system.

Of course in order to start your application on another system you have to make sure those DLLs are installed. They can either go into the aformentioned Windows or System directory or if you put them somewhere else you have to make sure to add that directory to the PATH environment variable. LabVIEW will simply ask Windows for the DLL and if it is not either in the Windows or System directory (or the current application directory) or in a directory in the PATH variable Windows will not be able to find it.

I would however not mess with lvdaq.dll. It's required by LabVIEW to access DAQ hardware and will access the system installed NI-DAQ drivers.

Rolf Kalbermatter

Message Edited by rolfk on 05-08-2009 01:30 PM

[Malcolm Bebb]

Thanks - putting them in \system32 has sorted it out. I set the installer to put copies in the system directory on the target system while leaving the originals in place on the development system.

This meets my needs well enough to be a liveable solution.  (There are some buttons in the App Builder window which seem as though they should do this function, but apparently they don't)

But anyway, I'm going again. 

Thanks again,

Malcolm