creating standalone executable

[Electronics]

I want to take my .exe file to another computer to run it. but when i take the exe file to another computer that has not the labwindows then it gives me error. like this " The application has failed to start becaz cvirte.dll was not found. Re-installing the application may fix this problem"
how can i make exe file that work irrespective of labwindows/cvi installed or not.
thanks

[RobertoBozzolo]

CVI executables need the CVI Run-time engine to be installed on the target machine. When you install the IDE on a machine you install the run-time engine too, while on other machines you must install it before running the exes.

You can donwload the run-time engine from NI site as a separate (free) product to install on target machines, but the easiest way to install it is to create a distribution kit that sums up your executable, all files related to it (UIR and other files necessary for your application) and the run-time engine. To create a distribution kit you must use the Create distribution kit... function located in the Build menu of the project window.

[mama007]

Hi,

I am also creating a standalone executable (created from CVI7.0) to run on other PC's. In the Target Settings, I have selected run-time support as Full run-time engine and selected embed project UIR's. I have also added all files to executebles under load external modules.

I am only using this application using a DAQ board USB-6008. If I intsall NI-DAQmx from the CD on the target machine, will my executable run with out any problem????

I have tried to create distribution kit, this is adding my executables and UIR's into installation directory. I am still not sure this runs on my target PC. I have thought distribution kit will install all the neccsary components that are required for the project including the drivers, but it just looks like it only create CVI run-time installation. Is this similar to selecting run-time support as Full run-time engine in target settings option.

Thanks in advance

[Mert_A.]

The run-time support option in the Target Settings dialog controls which LabWindows/CVI run-time DLL (cvirte.dll, cvi_lvrt.dll, or instrsup.dll) your program links against when it is built.  Whatever option you choose, you are still responsible for ensuring that the CVI run-time, as well as any other drivers you use, are installed on the target system where your program will be run.  The CVI distribution builder can help you install these run-time dependencies.  With CVI version 8.0 and later, you can bundle drivers such as NI-DAQmx along with your application for installation to the target.  If you have an older version of CVI, you will have to install the drivers separately.

Let me know if you have any further questions.

Mert A.
National Instruments

[mama007]

Thanks for the information.

I am also facing an issue to deploy DAQmx drivers. DAQmx 8.5 is about 800MB in size to download and is even 1GB after the extraction. Is there any way I can find the installations just for the required components(probably just DAQmx8.5 and MAX), so that these can be placed on the server/ made as installation disk along with CVI runtime??? I obviously doesn't need the labview support,DAQ assistant,documentation etc... during the deployment

I have downloaded the CVI runtime7.0 and the installation files are only just 6MB in size.

[Mert_A.]

The DAQmx installer is big.  That's a consequence of bundling the drivers for every DAQ device NI makes into one big package.  There's no way I know of to pare down the DAQmx installer into smaller components.  CVI 8.0+ distribution builder does help alleviate this pain for redistribution purposes by allowing you to include runtime-only "flavors" of the DAQmx driver with your application.  If you have version 8.0 or later, you can save some space by going that route, otherwise you may just have to live with hosting the 1 GB installer on your server, or having a 2-CD distribution for your app + drivers.

Mert A.
National Instruments