Search the Community
Showing results for tags 'fixed'.
Found 4 results
Update from JKI: This issue is planned to been fixed in VIPM 2018. So I can successfully build packages with VIMs in them. But I found that if I need to make a package, that depends on a package, which contains a VIM, the build will fail. First install the hooovahh_array_vims-188.8.131.52 package. Then try to build the File IO package, which at the moment only contains one VI. If it is like my setup the build will fail with this error. If I remove the VIM dependency by replacing it with the OpenG one the build is successful. Build Fail VIM Dependency.zip
Hopefully someone here can point me in the right direction. Installing VIPM 2017: LabVIEW 2015 SP1 failed since 2017 is installed. Says X already has newer version in 2017 so fails on error but the installer eventually, after several of these, says installation successful. I disagree. Running vipm results in errors like this... [root@shawn-michaels VIPM]# ./vipm Can't load library /usr/local/lib/liblvrt.so.15.0 libXinerama.so.1: cannot open shared object file: No such file or directory So then I create softlink to resolve the apparent issue but them I run into 32 vs 64 bit like this... Can't load library /usr/local/lib/liblvrt.so.15.0 libXinerama.so.1: wrong ELF class: ELFCLASS64 and I've tried softlinks to both 32 and 64 bit object files. I am running CentOS7.4 64 bit bit I do have 32 bit glibc and such installed. Thank you for your help! Kindest Regards, Brian
The OpenG Array Library 184.108.40.206 is not listed in VIPM from the JKI Package Network. I even tried refreshing, but it did not find the required library. Other observations: 1. I am able to see an older version 220.127.116.11 of that library in VIPM 2. I checked the website and was able to find the latest version But I want to understand why my VIPM is not listing it
Hi, VIPM 2014 build 1963. When building a package with licensing and adding palette to the library, this search box comes up during the build: The search doesn't find anything, and we just have to close the search box. The package seems to work ok though - what does this mean? Also, when we enable deactivation in the build spec. we aren't able to deactivate (only supported in LV 2014 and onwards). When attempting to deactivate LabVIEW tells us that the deactivation failed with the following message "Function call contains invalid arguments". NI has confirmed this and can get deactivation to work when using the TPLAT API before building the package (and thus not handle the license binding within VIPB). Anything we can do to get deactivation to work from within VIPB? Cheers, Steen