I've found that the application builder will not find the dlls automatically if they are only added to the lvlib:
But they are found if part of a lvclass:
I'm using LabVIEW 2019
Hi Patrick,
Thanks for posting your results, it sometimes comes up when users want to package the DLLs but have to manually select them. The difficulty is that the 32-bit and 64-bit dependencies have the same filenames, so it's not trivial to just include all the DLLs. Maybe LabVIEW is smart enough to pick the ones appropriate for the target you're compiling for? Interesting there is such a difference between putting the DLLs as members of the class versus members of the library.
Cheers,
Martijn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Martijn,
I am building several applications that depend on ZMQ, but as discussed here
https://forums.ni.com/t5/LabVIEW/Include-all-dlls-of-a-project-into-executable/m-p/3763988/highlight/true?profile.language=en#M1060251
it
is not possible for LabVIEW to find the dlls if they are not inside a
class, library, or statically linked in a CLFN. Do you think you could add
the dlls to zeromq.lvlib? I am not sure if there are ramifications for
32/64 bit applications.
Also, thank you for the library; it is incredibly useful.
Thanks,
Patrick
I've found that the application builder will not find the dlls automatically if they are only added to the lvlib:
But they are found if part of a lvclass:
I'm using LabVIEW 2019
Last edit: Patrick Irvin 2021-09-17
Hi Patrick,
Thanks for posting your results, it sometimes comes up when users want to package the DLLs but have to manually select them. The difficulty is that the 32-bit and 64-bit dependencies have the same filenames, so it's not trivial to just include all the DLLs. Maybe LabVIEW is smart enough to pick the ones appropriate for the target you're compiling for? Interesting there is such a difference between putting the DLLs as members of the class versus members of the library.
Cheers,
Martijn
Thank you very much Patrick. This solved my issue.