Dependency not copied at build

[BrotherTom]

Hi everybody

I have a project which I want to build and the current focus is on two DLL which are called. Those DLL are contained in a lvlib located in the project dependencies.

Build specification:

In the source file settings I set the DLL's destination directory:

Now what happens is that one DLL is copied to the destination folder, the other one is not. Both DLLs are implicitly called by the program...

Anyone can hand out some advice?

Thank you!

[Sam_Sharp]

Is one of the DLLs located in System32? If so, I don't think it will get pulled into the build specification because it's a 'system' DLL so it's expected that it would be in the same place (System32) on the target computer.

[BrotherTom]

No, neither of them is located there. Both DLLs are located in the same user.lib path. The locations are identical.

[Sam_Sharp]

Are you specifying both by path? If you specify by name, LabVIEW won't automatically include it. If you specify by path, it will be automatically included. http://zone.ni.com/reference/en-XX/help/371361H-01/lvexcodeconcepts/locations_for_shared_libraries/

The obvious solution to this is to add the DLL to your project and then set them to 'always include' in the build specification, but it's weird that one is being included and the other isn't.

[Ben]

Speculating...

Are the VIs that cal into the DLLs located in the same folder and the DLLs they call AND marked as always include in the build?

Done with the speculating.

Ben