When building and/or installing packages, errors can occur due to file path lengths that exceed the limits of Windows (255 or 260 characters for Windows 7 and Windows 10, respectively).
Right now, there is no ideal solution (other than keeping your paths short, as described in the Work-Arounds section below), due to the fact that LabVIEW currently does not include support for enabling LongPaths in the Windows Registry, as shown in the docs below:
The length of the file name and file path that can be recognized by LabVIEW is the same as the length that is specified by Windows. For Windows 10, you can specify a file path or file name up to 260 characters, while for Windows 7, the maximum length is 265 characters. Please refer to your Windows version regarding the length limit.
Disclaimer: LabVIEW does not support long path names on Windows. Although Windows includes support to enable LongPaths in the Registry Editor, each individual application must have this support included in the code.
The best work-arounds involve keeping your file names short. This can be done in the following ways:
- Edit the package file name so that it's shorter -- the default value for the package file name is calculated from the organization name and display name of the package.
- Put your VI Package source in a folder with a short pathname (before you do a build) -- for example "C:\MyProj\"
- Adjust the Temp Folder used by VIPM for package builds (to make it shorter):
In VIPM's configuration file:
C:\Program Files\JKI\VI Package Manager\VI Package Manager.ini
find the "VI Package Manager" section:
[VI Package Manager]
and add the following key:
Note that this might fix the problem of building the package, but won't solve any problems associated with installing the package's files, if the install location path names are too long.
See also: NI Knowledgebase Article: What is LabVIEW File Path Control/Constant Length Limit?
Article is closed for comments.