LabVIEW 2019 SP1 create installer: additional required installers list

[kosist90]

Dear LabVIEW community,

recently I've faced with the following issue, which I was able to replicate on a simple dummy project's code.

I have simple VI which calls 1 button dialog function. I am able to create executable with it. But when I create installer, it requires a lot of additional installers which I am missing on my PC.

I have set manually to include just components which are needed, but anyway - LabVIEW asks for installers which obviously are not needed in my case/have nothing to do with current application.

I know that LabVIEW stores installers in cache so it could use them during installer builds. But - why does it asks to locate installers which are not needed for the current build? Like, why there is needed NI Logos, NI Python Interface, VIPM Runtime Engine installers?

I was clearing my cache manually - but now it is not clear how to get back them using, let's say, NI Package Manager?

Overall it seems like a LabVIEW bug - because it asks for installers which are not needed by this particular installer specification build; and if one does not provide those installers - it is not possible to build installer at all.

[RavensFan]

You do have the box checked that says, "copy the select installers and all future installers"

So it sounds like LabVIEW is doing exactly what it says it is going to do.

[kosist90]

If I deselect that checkbox, then anyway it is not possible to build the installer. It drops the same window but at the end of the build.

When checkbox is selected, then window with the list of installers is shown right after I press "OK" button (kind of saving build specification).

When checkbox is deselected, then I can press "OK" button and save build specification, but when I press "Build" - it starts building installer, and then shows the window with installers list at the end. And if I close that window, then installer build fails.

[kosist90]

Additional point: if I deselect "future installers" in that window, then button "OK" is disabled - so it is not possible to make build at all.

I believe that solution could be to run LabVIEW repair or something like that, but it takes time and means that again all installers will be copied to cache. And, if I'll cleanup cache in the future then the same issue will appear.

Now I'd like to build such a simple installer, but in order to do that I need to have all those components which are not needed at the end. That is weird, and I guess it shouldn't act like that...

[billko]

If you're using any of the HTML VIs, I believe they do require the cURL library (no, that's not a caps lock artifact).  IMO, LabVIEW is very good at selecting the installers it needs to build an application.  You probably have dependencies you didn't know you needed.  Some of them aren't even logical, but some drivers depend on other drivers to be loaded, for example.

[kosist90]

Thank you, billko, but obviously that is not the case - because as you could see, my VI has only "1 button dialog" function primitive. And I guess there is no way that it depends somehow on "VIPM Runtime Engine", or NI Logos for example.

It seems for me that for some reason - because the behavior is the same when I deselect option "Include and copy installers ...." - LabVIEW ignores settings of the build, and tries to get all the possible installers that it misses. Even if those installers are not needed for the current build.