Problem:
There are a lot of software dependencies that a custom device developer needs to install to be able to either create a new custom device from a template or open an existing custom device source project and build it. At a minimum, you would want to install:
- LabVIEW/LabVIEW Real-Time that matches the major version and bitness of VeriStand
- VeriStand Support for LabVIEW (included in the VeriStand installation)
- VeriStand Custom Device Development Tools
- (optional - Only needed to create CD from scratch) VeriStand Custom Device Wizard
These dependencies don't seem to be listed anywhere in the handbook. The handbook mentions the VeriStand Custom Device Framework, but doesn't give instructions on how to install it.
Describe the solution you'd like:
I'd like to see a page added to the handbook titled "System Requirements and Software Dependencies" or something like that. The page would list the main dependencies needed for CD development, including links to the various release pages for those packages. It should contain basic installation instructions.
The page should also mention that many custom device may depend on additional toolkits, so developers should refer to the Readme page for those specific custom devices.
Problem:
There are a lot of software dependencies that a custom device developer needs to install to be able to either create a new custom device from a template or open an existing custom device source project and build it. At a minimum, you would want to install:
These dependencies don't seem to be listed anywhere in the handbook. The handbook mentions the VeriStand Custom Device Framework, but doesn't give instructions on how to install it.
Describe the solution you'd like:
I'd like to see a page added to the handbook titled "System Requirements and Software Dependencies" or something like that. The page would list the main dependencies needed for CD development, including links to the various release pages for those packages. It should contain basic installation instructions.
The page should also mention that many custom device may depend on additional toolkits, so developers should refer to the Readme page for those specific custom devices.