From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
LabVIEW Add-on Dev Center » Distributing an Add-on » Building an Installer for an API
In this example we will use the LabVIEW Application Builder to build an installer for a VI-based API. The recommended process for distributing an API, assuming palette menu (.mnu) files and the Example Finder linking file (bin3) have not been created yet, is the following:
**Note: This is the recommended process for developers who have developed/stored their code in a location outside of the LabVIEW directory structure (National Instruments\LabVIEW\). For developers who already have their API files stored in the correct deployment directories as outlined in the File and Folder Names for Integrating into LabVIEW document, skip steps 1-3; these developers will only need to create the palette (.mnu) file(s), Example Finder (.bin3) file, and finally create a source distribution and installer as outlined below.
Note: Remember to uninstall the installer on your build machine to remove your toolkit.
We recognize this process is not ideal, but for plugging into LabVIEW this is a safe method to follow. Part of the reason for this complexity is the palette files and Example Finder files must be linked to files already within the LabVIEW directory structure; since the majority of developers will develop APIs outside of the LabVIEW directories, the process outlined above is absolutely necessary. Alternatively, if you were to develop within the LabVIEW directory structure, you could build your source distribution and installer directly from the LabVIEW directories. For this approach, you would need to configure your SCC application to sync to the directories where you store your files, and the example below will still outline the process for building the source distribution and installer as the directory structure in the example matches that of the LabVIEW directory.
For this example, a .zip file is provided (link at the bottom of the page) containing a set of source files representing the status of a typical development folder after step 6 above. Extract these files to a location on disk. We're going to walk through the process of creating a source distribution and installer for this API.
Source Distribution
Installer
You now have an installer to test on a deployment or test machine. I recommend opening LabVIEW on the machine you install this example to verify your installer has worked. See if you can find the features we installed for the ATX Simple Math example API.