What to consider
- Does your API or toolkit work when built into an executable?
- If deployment licensing is required, have you documented this for your customers?
- If you plan on supporting multiple RT targets, do your API or toolkit VIs support both target types with the same VIs?
- Have you documented any additional run-time or deployment dependencies?
If your product is a LabVIEW API it must be tested for the use case of being built and deployed in an executable; furthermore, if any extra steps are necessary for deployment licensing these must be documented for your customers. One easy test is to build one of your example VIs into a LabVIEW executable -- troubleshooting this process will give you a good idea of what your customers will experience and you can provide documentation to assist them through this process.
When supporting multiple RT target OSes (PharLap and VxWorks), the same Call Library Function Node can be used by referencing 'DLLname.*' -- LabVIEW will either look for the .dll or .out depending on the target OS. If users must take steps to copy over any dependencies, such as a .out file on VxWorks, these steps should also be either documented for customers or a 'deployment' utility or MAX install script should be used to deploy to the target.
Please refer to the Target Deployment Utility Example for an example of using a LabVIEW Tools menu option to deploy dependencies for your product to a Real-Time target.
Additionally, any extra steps or dependencies required in order to make use of your addon must be documented in your product manual. This includes any deployment licensing schemes in place for your product.
