07-27-2020 01:05 PM
I can either create a "package" (requiring NIPM) or an "package installer" that does not require an "a priori" existence of NIPM). How do I create a lean package installer for my app (~10MB) that does not include the runtime (~300MB!), but still knows that my app depends on the runtime engine so NIPM can automatically download and install it as required dependency.
It seems if I add the runtime dependency, the package installer will include it, inflating the size. This is undesirable. Most of my users don't have any existing NI software except for some of my programs. Except for their first install, they already have the runtime and I don't want to drag along a 300MB boat anchor with every single program, but I also don't want to distribute it as package where they need to find, download, and install NIPM first!
Again: How Do I create a package installer that includes NIPM, knows all dependencies, but does not include the dependencies?
07-27-2020 01:55 PM
To do this in NI Package Builder, I think you would not list the runtime as a dependency to your package. (Not really helpful since you do need it.) I do not think they have added an option to exclude the run-time like you could with the Application Builder Installer. I would kudo that idea to have that as an option, particularly since NIPM 20.0+ is supposed to be able to get needed NI software without having to have the feed added.