This document is part of the NI Package Management Portal.
Build a package that installs a 3rd party (non-NI) installer
Option 1: Create a File Package Using NI Package Builder
You can use the following steps to create a file package that places (i.e. installs) the non-NI installer files on the target computer… and uses a post-install step that runs the non-NI installer.
Completed NI Package Builder solution
Note: For NI Package Builder 19.5 or earlier, please use a destination folder like [Documents]\My Installer instead of [Temp].
Dialog to configure "Post All Install" behavior
Note: The 3rd party Git installer will install silently if you pass a "/SILENT" argument. Enabling the Wait to Complete checkbox cause the NIPM installation of this package to wait until the 3rd party installer completes before this package's installation completes.
Note: Use a Root folder that contains the 3rd party installer.
For NI Package Builder 19.5 and earlier, this folder should be something like [Documents]\My Installer instead of [Temp].
Dialog to configure "Pre Uninstall" behavior
Example code: Explore the files for this example NIPB solution, which is hosted on this GitHub page: 3rd party installer wrapper (Git client installer)
Option 2: Create a WinInst Package
If the non-NI installer (e.g. non-NI drivers) contains .msi files, you can follow these instructions to create a “WinInst” package:
Example code: Explore an example that wraps a Python 2.7 msi installer on the this GitHub page: 3rd party MSI installer wrapper (Python 2.7 MSI)
Option 3: Create a File Package By Manually Assembling the Package
If the non-NI installer does not have .msi files, then you could use the following documentation to create a file package instead that places (i.e. installs) the non-NI installer files on the target computer… and uses the instructions XML file to execute a post-install step that runs the non-NI installer.