Amalia Grigore Posted November 23, 2022 Report Share Posted November 23, 2022 Dear JKI users, I'm trying to build a package out of a library using VIPM. My library uses functions from another already installed package, which introduces the "LabVIEWHTTPClient.lvlib" (located here on my machine "C:\Program Files (x86)\National Instruments\LabVIEW 2018\vi.lib\httpClient") as a dependency. I attached file "http functions.jpg" with the block diagram of the VI that introduces the dependency. As a result, I receive a build error (attached "missing file.jpg") saying SSL.vi (which is called by LabVIEWHTTPClient.lvlib as "caller.jpg" is confirming) is missing. And indeed it is, I have no such VI at the specified location, but neither do my colleagues who tried building the same package on their machines. They receive the same error. Does anyone have any idea why this happens and how it can be fixed? Thanks in advance, Amalia Quote Link to comment Share on other sites More sharing options...
Matt Satcher Posted February 20, 2023 Report Share Posted February 20, 2023 Hi Amalia, Did you find any fixes for this? I'm seeing the same issue. I dug into that LabVIEWHTTPClient.lvlib and found that NI_InternetTK_Core_VIs.lvlib:SSL.vi was listed as a friend of the library. But since the library is locked and password protected, there's no way to remove it. And that file just doesn't exist in the expected path. I tried creating an SSL.vi in that location, but then I just get errors about VI's not correctly linked to libraries. Quote Link to comment Share on other sites More sharing options...
Amalia Grigore Posted February 21, 2023 Author Report Share Posted February 21, 2023 Hi Matt, I accidentally discovered that if I had a project which has the LabVIEWHTTPClient.lvlib as a dependency opened in LabVIEW and then trying to build the package using VIPM (with that project opened in the background) it works fine without throwing the error. My guess is that having the project opened in LabVIEW loads the LabVIEWHTTPClient.lvlib and its components into memory and thus the missing VI issue is solved. Hope this workaround helps Quote Link to comment Share on other sites More sharing options...
Youssef Menjour Posted February 22, 2023 Report Share Posted February 22, 2023 (edited) I Edited February 22, 2023 by Youssef Menjour Quote Link to comment Share on other sites More sharing options...
Jordan Kuehn Posted April 26, 2023 Report Share Posted April 26, 2023 I can reproduce this behavior and the workaround. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.