CVI Build Problems

[Double_D]

I am linking to the library NIDAQmx.lib in my application.  For the new build, I have added the NI-DAQmx 8.6.1 (Full) component to the installer.  This wasn't selected automatically and wasn't included with the previous build.  When I clicked "Check Module Dependencies" in the Edit Installer dialog with NI-DAQmx not selected, the message stated that all necessary merge modules were found.  I guess that this wasn't a problem on my development machine, as the latest version of the driver was already installed, whereas the old version on the target machine is incompatible.  I will try the new build on Monday (which is the only day I can do maintenance on the target machine).

[Mert_A.]

Yes, this makes sense then.  The Check Module Dependencies button is for tracing the dependency chains of MSI merge modules (.msm files) only.  That is, it ensures that any included .msm components that declare dependencies in their ModuleDependency tables can resolve those dependencies during the distribution build.  It does not necessarily detect or report missing runtime dependencies of your application, which is the case with your application's dependency on DAQ.  If DAQ was not automatically selected when you created the distribution, one possible reason would be that you have the NIDAQmx.lib explicitly added to your project tree.  CVI will automatically attempt to link your projects against a number of common libraries (those listed in CVI's "Library" menu) after linking any explicitly specified .lib files. CVI only detects your application's dependency on DAQ if it had to do the "extra" link step to resolve those symbols.  If you explicitly add the .lib to your project, CVI won't know about the dependency and won't auto-select the component in your distribution.

Let me know if anything comes up.

Mert A.
National Instruments