User Tools

Site Tools


kb:labview:tools:vipm

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
kb:labview:tools:vipm [2023/08/19 07:11] alexander.elbertkb:labview:tools:vipm [2025/01/15 17:20] (current) – ↷ Links adapted because of a move operation 117.99.213.102
Line 1: Line 1:
 ====== VI Package Manager ====== ====== VI Package Manager ======
  
-//VI Package Manager (VIPM) is a community and tool that helps you find, download, share, & manage LabVIEW Add-ons.// +//VI Package Manager (VIPM) is a community and tool that helps you find, download, create, share, & manage LabVIEW Add-ons.//  
 + 
 +<WRAP center round tip 100%> 
 +HSE Internal: [[organization:internal-kb:sw-dev:vips|How to create a new package]] 
 +</WRAP> 
  
 ===== Resources ===== ===== Resources =====
  
   * https://vipm.io   * https://vipm.io
-  * https://www.vipm.io/desktop/versions/+  * https://vipm.io/desktop/versions/
   * https://forums.vipm.io   * https://forums.vipm.io
  
 +---- 
  
 ===== FAQ ===== ===== FAQ =====
Line 21: Line 27:
  
 You can define VIs to be called during install/uninstall, so-called custom actions. I've tried to copy zip files to ''C:\ProgramData\Hampel Software Engineering\PPLs'' instead of installing them into vi.lib and it turned out, that the Post-Install Custom Action is executed before the files were extracted! You can define VIs to be called during install/uninstall, so-called custom actions. I've tried to copy zip files to ''C:\ProgramData\Hampel Software Engineering\PPLs'' instead of installing them into vi.lib and it turned out, that the Post-Install Custom Action is executed before the files were extracted!
 +
 +=== Connecting to LabVIEW ===
 +
 +VIPM connects to LabVIEW via the VI-Server TCP port (default: 3363). If experiencing problems, make sure to adhere to the settings as described on [[https://support.vipm.io/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW|this KB page]].
 +
 +{{:kb:labview:tools:vipm-lv-viserver.png?600|}}
 +
 +
 +=== internal_deps ===
 +
 +When VIP Builder thinks he needs to add dependencies, a folder in vi.lib next to the installation folder will be created like this:
 +
 +{{:kb:labview:tools:pasted:20240815-094406.png}}
 +
 +I was able to solve it, be opening the .vipb file and refreshing the dependency list.
 +
 +Looking at the .vipb with notepad++ showed changes in this entries, but I couldn't follow the logic.
 +
 +   <Advanced_Settings>
 +     <Package_Dependencies>
 +       <External_Dependencies>...</External_Dependencies>
 +       ...
 +       <Direct_Dependencies>...</Direct_Dependencies>
 +     </Package_Dependencies>
 +
 +
 +---- 
  
 ===== Linux ===== ===== Linux =====
 +
 +==== Download ====
 +
 +  * [[https://www.vipm.io/desktop/|Latest Official Release]]
 +  * [[https://forums.vipm.io/topic/7513-vipm-2023-q3-release-candidate-for-linux/#comment-14353|VIPM 2023 Q3 Release Candidate for Linux]]
 + 
 +
  
 ==== Installation ==== ==== Installation ====
  
-Download the VIPM release for Linux: https://www.vipm.io/desktop/+[[https://support.vipm.io/hc/en-us/articles/8746083021460-Error-11-Too-many-files-open-on-VIPM-for-Linux|To prevent the too many files open issue]] 
 + 
 +    $ sudo nano /etc/sysctl.conf 
 +    $ fs.file-max = 2000000 
 +    $ sudo sysctl -p 
 + 
 +Restart your system or re-login.
  
 Create two folders Create two folders
Line 32: Line 78:
     $ sudo mkdir /etc/JKI     $ sudo mkdir /etc/JKI
  
-Change the owner of the folders to your current user, to gain write access+Change the owner of the folders to your current user, to gain write access (not needed, if sudo is used later)
     $ sudo chown $USER -R /usr/local/JKI/VIPM     $ sudo chown $USER -R /usr/local/JKI/VIPM
     $ sudo chown $USER /etc/JKI     $ sudo chown $USER /etc/JKI
kb/labview/tools/vipm.1692429116.txt.gz · Last modified: 2023/08/19 07:11 by alexander.elbert