LabWindows/CVI Run-Time Engine

Under Linux, the Run-time Engine comes in the form of a shared library called libcvi.so.n. The installation program installs the shared library in the lib subdirectory under the Run-Time Engine installation directory. It also creates the following symbolic links, where cvirte stands for the Run-Time Engine installation directory.

Pathname of Link Target of Link
/usr/local/lib/libcvi.so cvirte/lib/libcvi.so
cvirte/lib/libcvi.so cvirte/lib/libcvi.so.8
/usr/local/lib/libcvintwrk.so cvirte/lib/libcvintwrk.so
cvirte/lib/libcvintwrk.so cvirte/lib/libcvintwrk.so.8
/usr/local/lib/libnianlys.so cvirte/lib/libnianlys.so
cvirte/lib/libnianlys.so cvirte/lib/libanlys.so.8
/usr/local/lib/libinstrsup.so cvirte/lib/libinstrsup.so
cvirte/lib/libinstrsup.so cvirte/lib/libinstrsup.so.8

The following table shows the files that the installation program installs in the Run-Time Engine installation directory.

Run-Time Engine File Description
msgrte.txt Contains text messages
cvirte.rsc Contains binary resources
ni7seg.ttf Font description file
nisystem.ttf Font description file
libcvi.so.n Contains most LabWindows/CVI libraries
libinstrsup.so.n Contains LabWindows/CVI libraries
libnianlys.so.n Contains the Advanced Analysis Library
libcvintwrk.so.n Contains the Internet Library
libLVMesaGL.so.3 LabWindows/CVI support library for lab-style controls
Note  Fonts are not registered at install time. To use the fonts, you must register them. The method for registering fonts varies depending on your Linux distribution.

The LabWindows/CVI Run-Time Engine does not include the shared libraries or drivers for National Instruments hardware. Users can install the shared libraries and drivers for their hardware from the distribution disks that National Instruments supplies.