Hello,
I am building an installer for an executable in Labview. When I build the installer, I am including both the LV Run Time Engine (of course, since this is the main reason for the installer) and also the VISA run-time installer. Once this installer is built, I then have a complete self-contained installer so that my application can be run on any computer. This works well and I am very happy with it.
The one caveat is: Sometimes I am writing these applications to be run on a piece of test equipment, calling out the instrument as a localhost VISA resource. This is a pseduo-embedded type of application in that the piece of test equipment, while it is a Windows XP (embedded actually) computer, is typically not as powerful as a full-blown PC host computer. My only complaints are 1) that the installer, once it includes all the necessary components, is a 75 Mb file, which is tough to distribute sometimes (requires me to put it on a download server) and 2) when running on the "less powerful" PC i.e. the piece of test equipment, the application is quite slow in starting up (5 seconds or more).
So, I would greatly appreciate any tips to either 1) reduce the amount of raw data required to provide installers for my application, including LV Run-Time and VISA Run-Time components and/or 2) make the application startup to be quicker somehow. I get the feeling that my applications are relatively simple and could be accomplished with a 500 kb program that runs super-fast and my solution is, instead, to provide a 75 Mb program that takes several seconds to even start. I realize that this is the price that I pay for using such a powerful environment such as Labview to solve the problem, but was just looking for tips to minimize what seems like overkill. I would completely understand if there wasn't much to do, but was hoping for any tips.
Thanks,
Greg
