You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
An important part of any custom device is the build of the source distributiion for the configuration and engine.
The engine can be build for different targets which have to be setup in different ways.
As this configuration includes both changes to the custom device labview project file and the custom device xml definition,
ideally the Custom Device wizard would included that!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
An important part of any custom device is the build of the source distributiion for the configuration and engine.
The engine can be build for different targets which have to be setup in different ways.
There is some documentation available here: https://forums.ni.com/t5/NI-VeriStand-Add-Ons-Documents/How-to-run-a-custom-device-on-target-RT-Linux/ta-p/3537624 but it really should be part of the developer guide!
Describe the solution you'd like
Add an update version of: https://forums.ni.com/t5/NI-VeriStand-Add-Ons-Documents/How-to-run-a-custom-device-on-target-RT-Linux/ta-p/3537624 to the developer guide!
As this configuration includes both changes to the custom device labview project file and the custom device xml definition,
ideally the Custom Device wizard would included that!
The text was updated successfully, but these errors were encountered: