LabVIEW calls the core library directly through Call Library Function nodes. There is no toolkit to install and no VI package to keep in step with your LabVIEW version — the ABI is stable, so a VI you wire today keeps working.
Configuring the node
Point the node at the shared library, set the calling convention to C (not stdcall), and match the bitness of your LabVIEW installation — a 32-bit LabVIEW needs the 32-bit library. Both are supplied. Byte arrays are passed as Array Data Pointer, and anything returning variable-length data follows the two-call convention: ask for the size, allocate, ask again.
Why this fits test and measurement especially well
A LabVIEW application is usually inseparable from a physical setup: a test cell, a rig, an instrument rack. That machine frequently has no internet connection and never will, which makes online activation the wrong tool and a dongle the obvious one. It also means the licence can move with the rig when the rig moves.
Gate on your calibration constants, limit tables or instrument coefficients rather than on a Boolean wire — a Boolean is one diagram edit away from being replaced with a True constant, and unlike compiled code, a VI is editable by whoever has it.
We ship the wiring instructions rather than a binary VI, deliberately: a .vi is a binary file that cannot be reviewed in a diff, and it would tie you to one LabVIEW version.
