Open
Description
The API is loaded using load_self(), which assumes that LabVIEW loads labview-interop when executing DLL calls from VIs.
With the advent of Owned Types this may not necessarily be True, i.e. for tests that need the LV memory manager, but do not require to be launched through LabVIEW.
Proposed solution:
- Can we detect if we run the link feature standalone and if we do have a DLL path detection?
Now after having written this, I wonder if LV does actually support a headless operation of the memory manager, maybe with the LV Runtime?
Metadata
Metadata
Assignees
Labels
No labels