LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

installer size LV 2010

Guys,

 

Installer file size has been a problem since LV 2009.

 

I see that in LV 2010 (when builing installers) there are a range of run-time installers to include/exclude. 

 

Does this mean the run-time engine is now modular and the size of installers can be reduced if your application doesn't use certain functions?  More info?

 

If so, is there a way of LV deciding for me which RT module components I do need for my app?

 

Cheers,

 

Battler.

Message 1 of 7
(3,248 Views)

I suppose what I'm getting at; by unchecking any selections here can I reduce installer size? 

 

How do i know which ones I can uncheck?

 

Clipboard01.jpg

0 Kudos
Message 2 of 7
(3,225 Views)

Read the description off each. For example, if you are not creating a ww\eb service, you don't need the ones related to that. If you are using any analysis functions, you would obviously want the math kernel.

0 Kudos
Message 3 of 7
(3,223 Views)

I can't be sure what I am using just based on the descriptions.  I am talking about an application containing many thousand VIs.

 

Is there a way I can find out?

 

Does it make a difference to the size?

 

What are the NI logos?

 

Is there a guide to this?

Message 4 of 7
(3,210 Views)

You can see that it makes some difference. Storage is cheap, though. How much time do want to spend worrying about a coouple of MB? You will also be testing the installer, I presume.

 

Search for NI-Logos.

 

 

0 Kudos
Message 5 of 7
(3,191 Views)

The full-size Run-Time Engine will be negligible in size if your app contains several thousand VIs. This feature really targets customers who are more hard-drive-constrained, typically with smaller apps. In these use cases, safely de-selecting the soft depedencies on the Run-Time Engine becomes an easier task.

 

As of right now, we do not provide a way to automatically detect which redistributable products are required by your app(s) deployed by the LabVIEW Installer Builder, but it has been a highly desired feature, not so much for de-selecting soft dependencies of the RTE, but for including other products that are not selected by default.

0 Kudos
Message 6 of 7
(3,172 Views)

The constraint here is download bandwidth.

 



@Bob P wrote:

...it has been a highly desired feature, not so much for de-selecting soft dependencies of the RTE, but for including other products that are not selected by default.


This is would be a handy feature when using the Report Generation toolkit.

0 Kudos
Message 7 of 7
(3,133 Views)