NI Package Manager (NIPM)
Register NIPM Feed from Gitlab Repo
Rahul,
You can also create nipkgs on the commandline (e.g. Powershell, CMD) with the nipkg pack command, if I recall correctly.
The documentation that would be relevant can be found here: https://www.ni.com/docs/en-US/bundle/package-manager-21.0-feature/page/control-file-attributes.html
and related links near that one.
You can assemble the necessary structure on disk using a template that you create manually and then use LabVIEW or commandline, depending on what suits your build system, to copy it and replace the necessary strings in the control file for your specific package.
Does that help?
Thanks Bill,
With that Build.vi it seems I can only build any existing Build Specification but not create a new one.
@cbutcher: Thanks for your response.
Yes, that's what I was looking for.
I tried it out and could create a new sample Package.
Only thing still missing here is the Destination path where the installed files will be located on the deployment system.
Maybe I need to dive deeper into this topic if it is possible to make this Destination path configurable.
If not then, I guess I can always move the files after installation from C:\Program Files (x86) to the desired location from LabVIEW.
Thanks,
Rahul Nirhale
Certified LabVIEW Developer
So, when I tried doing this, the list of options was only relative to one of these paths: https://www.ni.com/docs/en-US/bundle/package-manager-21.0-feature/page/installation-target-roots.htm...
So for generic installations, the only path I found useful (for my case) was BootVolume - this gives basically C:\, and from there you assemble a bunch of empty-ish directories until you reach wherever you actually want to put your files.
However, now I see that you can produce a "relative file package", which seems to allow specifying a different installation path. I haven't used these, it isn't immediately obvious to me if this is to allow the user to choose where to install or the developer...
@Raul2203 wrote:
Thanks Bill,
With that Build.vi it seems I can only build any existing Build Specification but not create a new one.
@cbutcher: Thanks for your response.
Yes, that's what I was looking for.
I tried it out and could create a new sample Package.
Only thing still missing here is the Destination path where the installed files will be located on the deployment system.
Maybe I need to dive deeper into this topic if it is possible to make this Destination path configurable.
If not then, I guess I can always move the files after installation from C:\Program Files (x86) to the desired location from LabVIEW
Yeah, we have all of the build configuration pre-defined for each product including the folder structure. All of the information is stored in the .lvproj file, which is just XML. So in theory, you can create tooling to create all the XML entries, but there is a lot of keys to build.
For the Destinations, you have to build off those defined starting points, but you can create any depth of folders (as long as it valid for the file system). Target Root Directories However you can target anywhere on the main boot drive of the system from Boot Volume.
