Error When Building an Executable Containing LabVIEW Classes Primary Software: LabVIEW Development Systems>>Professional Development SystemPrimary Software Version: 8.6 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: I am trying to create an executable that uses LabVIEW Object Oriented Classes, but the build process fails every time indicating that the main VI became broken after disconnecting type definitions. What am I doing wrong and how can I resolve this problem? Solution: A failure of this type when building an executable is a result of a few selections that can be controlled from the My Application Properties window. The options vary slightly through LabVIEW versions and are described below for LabVIEW version 8.0, 8.2.1, 8.5, and 8.6. However, the primary considerations are to ensure that Debugging is enabled and that the LabVIEW Builder is not disconnecting type definitions.
LabVIEW 8.5 and 8.6
The executable will need to be built with two specific options in mind. These are listed below:
LabVIEW 8.2.1 The executable will need to be built with two specific options selected. They are listed below:
1. Enable Debugging. You can select this option in the Advanced category of the build specifications.
2. Remove unreferenced project library members. You can select this option in the Additional Exclusions category of your build specifications.
LabVIEW 8.0 The executable will need to be built without selecting the Disconnect type definitions and remove unused polymorphic VI instances option from the Advanced category of the build specification.
Related Links: KnowledgeBase 4OKDCDES: Managing the Resulting Files from a Build Containing LabVIEW Classes Attachments:
Report Date: 05/07/2007 Last Updated: 11/04/2008 Document ID: 496CKS45 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
