Instrument Driver Only Run-Time Support
If you specify Instrument driver only for the Run-time support option in the Target Settings dialog box for DLLs or the Target Settings dialog box for executables, the project does not link to the entire set of LabWindows/CVI libraries but instead links to a smaller set of functions. The Instrument driver only option is particularly useful for creating instrument driver DLLs. The option allows other applications to use instrument driver DLLs without having to load the large LabWindows/CVI Runtime DLL.
If you use an external compiler and want to use the smaller set of Instrument driver only functions, include CVIversion\extlib\msvc\instrsup.lib or CVIversion\extlib\msvc64\instrsup.lib in your external compiler project instead of cvirt.lib and cvisupp.lib. Remember that when you use an external compiler, you link to that compiler's ANSI C library.
(Linux) The equivalent instrument driver only file is called libinstrsup.so.
The Instrument driver only option supports the following libraries and functions. All the functions supported for Instrument driver only projects are multithread safe.
 |
Note Projects with the Run-time support option set to Instrument driver only do not support the Windows console window. Functions such as FmtOut, ScanIn, printf, and scanf do not display output to the console window for Instrument driver only projects. |
- Formatting and I/O Library (except ArrayToFile, FileToArray, FmtOut, and ScanIn)
- RS-232 Library (except InstallComCallback)
- ANSI C Library (except functions in the Input/Output class and its subclasses)
- The following functions in the Utility Library:
- All functions in the Debugging and Run-time Error Reporting class (except CVIDynamicMemoryInfo)
- All functions in the Timer/Wait class
- Beep
- CVIRTEHasBeenDetached
- DateStr
- InStandaloneExecutable
- TimeStr
- RoundRealToNearestInteger
- TruncateRealNumber
An Instrument driver only project also can link to the following libraries:
- Analysis or Advanced Analysis Library
- GPIB/GPIB 488.2 Library
- VXI Library
- VISA Library
- IVI Library
- NI-DAQmx Library
- Traditional NI-DAQ Library—If the project files call the Config_Alarm_Deadband, Config_ATrig_Event_Message, Config_DAQ_Event_Message, DIG_Change_Message_Config, Get_DAQ_Event, or Peek_DAQ_Event functions in the Traditional NI-DAQ Library, you will get link errors when you build the program in LabWindows/CVI. The link errors occur because the preceding functions use the LabWindows/CVI User Interface Library internally, which is not available in the Instrument driver only runtime DLLs. The project files can call any of the other functions in the Traditional NI-DAQ Library.
If you use a stand-alone compiler and want to use any of these libraries, refer to Using LabWindows/CVI Libraries in External Compilers.