Joerg Hampel

Any chance there will be an official release of VIPM 2022 for Mac, too?

Hey, JKI, what's the status for this one?

Hey Jim, what's the situation in regard to the VIPM API? Currently, it shows as "not OS compatible":

It would be great if that fix made it back into the official release. If at all possible, we'd prefer to keep using the API from our LabVIEW-based tools.

Jim, you privately shared an unpublished version of VIPM (2020.0.3.80) with us back then, which we've been bundling with our tools ever since.

The one and only @Darren suggested the following (and my colleague Alexander @AlexElb executed on it brilliantly) for fixing that broken lv_icon.lvlibp: NI provides the source code for the icon editor on the NI forums. You can grab the version that matches your LabVIEW version and re-build the PPL with that issue fixed. Here's where you can get Icon Editor source files: https://forums.ni.com/t5/Enhanced-Icon-Editor/bd-p/grp-1168 For the sake of google-ability, here are the error messages and paths in plain text: The following source VIs or Libraries are missing. Click OK to show the callers of these VIs or Libraries. Please correct this problem before rebuilding. The build will now be aborted Load.vi --- e:\builds\penguin\labview\branches\2016\dev\dist\vi.lib\xml\Load.vi The following source VIs or Libraries are the callers of missing files (specified in the previous dialog). Please correct this problem before rebuilding. The build will now be aborted. NI_XML.lvlib. --- C:\Program Files (x86)\National Instruments\LabVIEW 2016\resource\plugins\lv_icon.lvlibp\1abvi3w\vi.lib\xml\NI_XML.lvlib

Done and dusted.

For added fun, I found an exact duplicate of the "Escape HTTP URL.vi" inside the JKI REST Client API: "Escape URL String.vi"! I created an issue in the REST Client's GitHub repo: https://github.com/JKISoftware/JKI-HTTP-REST-Client/issues/22 (I'd have loved to create a merge request but I don't have LabVIEW 2013 available, 2016 is the oldest version still in use at HSE).

Actually, this "Escape HTTP URL.vi" from vi.lib/wsapi is being used in JKI's REST Client 😉

LabVIEW Professional Development System Version 2022 Q3 (64-bit) 22.3f0

It seems that the webservices library is missing from my vi.lib: As the error message hints at, the whole /wsapi/ folder is missing. I'm not sure about this one. Is there a way to fix this? Edit: The NI System Configuration API (nisyscfg) and vi.lib/Platform/fileVersionInfo.llb:FileVersionInfo.vi also seem to be missing...

The next problem is OpenG - or, rather, the user.lib: So the next command to be executed is: sudo chgrp -R staff /Applications/National\ Instruments/LabVIEW\ 2022\ 64-bit/user.lib/ Now, all the necessary OpenG packages for my project can be installed. (still more to come...)

I'm using macOS Monterey version 12.2 (21D49) on an Intel MacBook Pro. --------------- The KB entry indeed helped resolve the issues with file permissions. Applying .vipc files also works! The one thing I'm stuck at now is installing DQMH 6.1. The process errors out with the following information: The 2nd error message already shows the problem - the KB entry misses a folder that also needs the staff group to be set: /resource/plugins/PopupMenus. So I added the following command: sudo chgrp –R staff /Applications/National\ Instruments/LabVIEW\ 2022\ 64-bit/resource/plugins/PopupMenus Now, the installation of DQMH succeeded! (more to come...)

Not sure if this is the right place to provide feedback - please move the post if not. Feedback for the Mac beta: The first three times I ran it, it crashed (the report mentions an error 8 at Delete in VIPM Splash.vi for the file VI Package Managerrunning.tmp while writing the "is running" temp file in the splash screen When VIPM opens, the status bar does show all sorts of packages it syncs/downloads from various places, but once it's done the package list seems outdated / inconsistent (see screenshot) Mostly, it crashes showing error 10 (duplicate path) while trying to create /Library After re-checking for package updates, VIPM tells me it could not access either the LabVIEW Tools Network (shouldn't that be called the NI Tools Network now?) nor the VI Package Network. Cmd - , does not open the settings window Applying a .vipc file does not work - but maybe that's due to all the other errors occurring before

Jim, that will be good enough for us Thank you! I've created an issue. Once we get around to implement and test this, I'll update this thread with our findings (if any).