11-04-2015 05:13 PM
Hello gurus,
I would appreciate suggestions/pointers, as I'm currently stuck: I have a LabVIEW installer that needs to fit on a CD 210M in size. The problem I face is that LabVIEW 2013, and LabVIEW 2015 are able to generate installers in 221M and 225M in size, respectively.
I've created executables and installers on previous versions of LabVIEW (2010, 2011) and do not recall their size being > 200M. Anyhow, I don't have access to either 2010 or 2011, otherwise I would post my results.
Regardless, I'm using LabVIEW 2015 and need to provide an installer (including the run-time engine), however, its size *ideally* needs to be approx 190M. Any suggestions?
The .vi I have used to generate the executable is in the .jpg shown... it does not get any simpler than that!
In advance, thank you for your input.
Cheers!
11-04-2015 05:17 PM
The bulk of the isntaller is the run-time engine. If you can distribute this seperately then your installer size will drop dramatically.
I don't believe there is a "light" run-time engine install available.
11-04-2015 05:25 PM
I've looked at that as well... but if you get the RTE from ni.com as example, it is for sure > 200M
In my case, my customer may not have access to the internet, hence the need for me to provide the .exe and RTE in a CD.
I could also send a compressed .zip, but that is just not ideal IMHO...
11-04-2015 05:28 PM
Why are you limited to 200 MB?
CD's have a capacity of about 700 MB.
11-04-2015 05:31 PM
Or provide two CDs if for some reason you are limited to 200MB (fro example - custom CD shapes often have reduced available sizes).
Unfortuantely I don't think there is going to be any other solution to this.
11-04-2015 05:39 PM
11-04-2015 10:35 PM
Eval kits is just one example; And I'm sure there are many other scenarios where good 'ol CDs might still be in use.
The fact that you don't use CDs does not mean that the rest of the world does not use them.
Cheers!
11-04-2015 10:56 PM
So why are you limiting yourself to 210 MB?
11-04-2015 11:38 PM
11-05-2015 03:39 AM - edited 11-05-2015 03:42 AM
Jack Dunaway wrote a really interesting article about how you can 'segment' the installation of the runtime engine and reduce the number of components that are included in even the basic run-time engine installer. I seem to remember the size savings to be significant enough that I remember about the article years later.
Unfortunately the link is now broken (and I couldn't find a cached copy) - https://connect.wirebirdlabs.com/knowledgebase/articles/172999-segmenting-the-run-time-engine
It's also discussed in this thread: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Build-executibles-that-don-t-require-a-runtime-engine/...
Someone says that they were able to get their installer with VISA down to 35MB!
It might be worth messaging him to see if he still has the article and/or can offer you some advice.