NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in this document. If you have feedback on this specific document, please contact NI on this NI Developer Zone post.
The following items are known issues in LabVIEW 2011 C Generator sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Building and Distributing LabVIEW Applications | ||||||
| 214201 Return | LabVIEW datatype definitions can conflict with those in external C code LabVIEW defines certain basic datatypes in the generated C code, viz. Boolean, float32, float64. When integrating the LabVIEW generated C code in a larger C application/code base, you should take precautions to avoid datatype definition conflicts. For eg, if the external code base also defines a 32-bit float as "float32", you will get a compiler error. Workaround: There are multiple ways of avoiding type name conflicts: 1. You can use LabVIEW generated datatypes in your top-level C application. These types are defined in LVDefs_plat.h. This file can be found in labview\CCodeGen\inlcude\os, under the directory for your specific operating system. 2. You can redefine your datatypes with names that are different from those used in the LabVIEW generated C code.
| |||||
| 223962 Return | Leading or trailing white spaces in the Build Specification name might cause C generation to fail When using the LVCG.exe to generate C code from the command line, leading or trailing white spaces in the the Build Specification name might cause the C generation process to fail. LVCG.exe takes the Build Specification name as one of its input parameters and it cannot process leading or trailing white spaces. Workaround: N/A
| |||||
| 228110 Return | LabVIEW generated Makefile compiles all object (.obj) files when creating a DLL The LabVIEW generated Makefile compiles all object files present in the obj directory. If this directory contains object files for VIs that have been removed from your VI hierarchy, they might cause a linker error. Workaround: You can manually delete the obj directory to ensure that all old object files are deleted. Running the make command after this will regenerate the obj directory and all necessary object files.
| |||||
| 231443 Return | LabVIEW does not check Entry/Exit action VIs for syntax when using the Statechart Module Statechart module lets you configure Entry and Exit actions for each state. LabVIEW does not check the VIs used in these actions for syntax. If you use unsupported VIs in the Entry/Exit actions, C generation might fail. Workaround: N/A
| |||||
| 231779 Return | Control References and Property Nodes do not report a warning when used in an exported VI When a top level VI is configured for export by adding it to a C Generator Build Specification, LabVIEW performs syntax checking on it to warn the user if unsupported VIs are used on the Block Diagram. However, Control References and Property Nodes do not report a warning. While the C generation step may succeed, using the generated code in an application will cause compilation errors. Workaround: N/A
| |||||
| 242492 Return | "clean" rule in generated Makefile does not clean all old object (.obj) files You can use the "make clean" on the command line to delete existing object (.obj) files before a new build. However, the clean rule in the LabVIEW generated Makefile only deletes object files created in the last build. If there are older files remaining from one of the previous builds, they will stay in the obj directory. These old object files might cause a linker error. Workaround: You can manually delete the obj directory to ensure that all old object files are deleted. Running the make command after this will regenerate the obj directory and all necessary object files. Alternatively, you can modify the clean rule in the Makefile to do this for you. Replace clean: dummy @del /f/s/q $(OBJS) @del /f/s/q $(LIBSRCOBJS) with clean: dummy @del /f/s/q $(OBJDIR)\*.obj @del /f/s/q $(LIBSRCOBJS)
| |||||
| External Code | ||||||
| 214201 Return | LabVIEW datatype definitions can conflict with those in external C code LabVIEW defines certain basic datatypes in the generated C code, viz. Boolean, float32, float64. When integrating the LabVIEW generated C code in a larger C application/code base, you should take precautions to avoid datatype definition conflicts. For eg, if the external code base also defines a 32-bit float as "float32", you will get a compiler error. Workaround: There are multiple ways of avoiding type name conflicts: 1. You can use LabVIEW generated datatypes in your top-level C application. These types are defined in LVDefs_plat.h. This file can be found in labview\CCodeGen\inlcude\os, under the directory for your specific operating system. 2. You can redefine your datatypes with names that are different from those used in the LabVIEW generated C code.
| |||||
| Functions, VIs, and Express VIs | ||||||
| 231443 Return | LabVIEW does not check Entry/Exit action VIs for syntax when using the Statechart Module Statechart module lets you configure Entry and Exit actions for each state. LabVIEW does not check the VIs used in these actions for syntax. If you use unsupported VIs in the Entry/Exit actions, C generation might fail. Workaround: N/A
| |||||
| 231779 Return | Control References and Property Nodes do not report a warning when used in an exported VI When a top level VI is configured for export by adding it to a C Generator Build Specification, LabVIEW performs syntax checking on it to warn the user if unsupported VIs are used on the Block Diagram. However, Control References and Property Nodes do not report a warning. While the C generation step may succeed, using the generated code in an application will cause compilation errors. Workaround: N/A
| |||||
Document last updated on 7/29/2011