Sign Up
EU Cyber Resilience Act (CRA) — First Deadline September 2026
If you sell LabVIEW-based software and systems in the EU, please be aware that new CRA regulations may require you to implement security vulnerability reporting starting September 11, 2026. The VIPM Team has prepared guides to help you understand how this applies to your software applications and published packages, since it's important you understand these regulatory requirements (click the Learn More link to read these guides). Thank you for your help in keeping security front-and-center within the LabVIEW community.
Learn more
VIPM › Posts › Libraries Missing from Lvlib

suggestion

Libraries Missing from Lvlib

Suggestion shared 3 years, 8 months ago by Matthew Fergusson
Related Packages: LIBSSH2 for LabVIEW
   

Details

We are trying to build a source distribution that includes this library - however we are running into issues due to the lvlib file "missing" the libraries it requires. Although they seem to still be present on disk.

This can be seen in "Support" folder for the the "Field_RND_Services_LIBSSH2_Toolkit.lvlib".

Thanks,

Matt

Comments

Christopher Field Hello Matt, Thank you for your interest and usage of the LIBSSH2 for LabVIEW toolkit developed and maintained by Field R&D Services. I am sorry to hear you are having trouble with the toolkit while trying to build a source distribution for your project. This toolkit is developed and maintained as an open source project with the source code repository hosted on GitHub (https://github.com/fieldrndservices/libssh2-labview) Please see the Issue tracker (https://github.com/fieldrndservices/libssh2-labview/issues) for the project, as someone else may have encountered similar trouble and may have a resolution for you. Specifically, your issue sounds similar to https://github.com/fieldrndservices/libssh2-labview/issues/54. The DLLs, dylibs, and Shared Objects (.so) in the Support folder need to be "always included" and/or explicitly added to the distribution as always included, or the workaround to add copies of the DLLs, dylibs, and SOs to an "in-project" destination may work for you as well. If this does not resolve your issue, could you please create a new one in the issue tracker? This would benefit everyone that uses the toolkit and would be greatly appreciated. Thank you, Chris
 •  Reply • 3 years

Please sign in to leave a comment.