Determine (and Minimize) LabVIEW Build Dependencies?

[NIquist]

Is there a way for LabVIEW to analyze a project and determine auto-magically exactly what additional installers need to be included with the main program installer?  It seems to know it needs to add the associated run-time engine but that's it.  This wouldn't be so bad if adding something like DAQmx or IMAQ didn't take your distribution size from 1MB to 1GB (only slightly exaggerating there).

Which brings up another question:  Can you just install drivers for the one or two hardware devices you're actually using in your program or is a full DAQ installation the only option?

I'm trying to get away from the evils of both extremes. 

    Too Much: Check off everything you think might be applicable and know that it will install but it will be a slow install of a ridiculously huge distribution file.

    Too Little:  Pare it down to the bare bones and get those disgruntled emails when IT can't install your application on a brand new PC.

The Too Little is also very tricky since ANY previous NI software installations might have installed the drivers you need in your current app fooling you into thinking you included everything you needed for that app to run on a fresh PC.  To verify that I had a totally complete install package I tried completely uninstalling all NI software, reboot, and sometimes it still finds NI drivers.  This makes it even more important that there is a reliable way to determine what the installer requirements are.  If there is no way to do it in the LabVIEW project environment does anyone know of any external dependency checking software?

[Brian_A]

Hi NIquist,

Unfortunately there is no automatic function that will do this for you. You will need to know what drivers are needed for your build and manually select them to be included. If you would like this function you can post it in the idea exchange. 

<Brian A | Applications Engineering | National Instruments> 

[SteveChandler]

Niquist, you really should post this as an idea! I will vote for out as soon as I see it.

[Dennis_Knutson]

And in reference to the DAQmx driver, you've had the option for quite a while to install just the run-time.

[FraggerFox]

LabVIEW will not take selected drivers for install, but it will take whichever option you select as a whole. If you want a particular driver to be selected (not the complete option), and eventually, reduce the installer size from 1GB to 300MB, you can use InstallShiel and Inno3D to build the installer, where you would be able to manually define what all you need.....

FraggerFox

[NIquist]

Thanks for the feedback.  I've used InstallShield before but I was hoping that NI software would be best at building NI software into an EXE.  I figured I was just missing some subtle Installer option.

I'll certainly post up the idea at the IE but it seems like a substantially bigger request than most.  Can't hurt to ask though...

Dennis, I did notice the three levels of: DAQmx core > DAQmx core + MAX > DAQmx core + MAX + App Dev Support.  Unfortunately, I didn't see a way to determine how much extra disk space each option (or any other option for that matter) would cost.  I guess I could build up a simple App with one option checked at a time and dtermine their sizes that way. 

[NIquist]

I've added the request to the Idea Exchange:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/LabVIEW-App-Builder-Should-Determine-and-Minimize-Dist...

[SteveChandler]

Great! Since I can only give you one kudu over there I will kudu this one as well 🙂

[NIquist]

Thanks Steve.  Is Kudu the singular form of Kudos??? Sounds right to me. 

Nope, it's one of these:

[SteveChandler]

---

@NIquist wrote:

Thanks Steve.  Is Kudu the singular form of Kudos??? Sounds right to me. 

---

That's what I get for trying to post from my phone using Swipe!