LabWindows/CVI User Group Documents
LabWindows/CVI 2009 introduces the ability to create and distribute 64-bit executables, DLLs, and static libraries. You can create 64-bit applications by selecting Build»Configuration»Release x64 or Build»Configuration»Debug x64.
In order to make use of the increased memory and data storage offered by a 64 bit operating system, you must build a native 64 bit application. While 32 bit applications can be run on a 64 bit operating system, they are constrained to the same virtual memory limitations of a 32 bit operating system. The primary difference between a 32-bit processor and a 64-bit processor is that you have access to more memory through expanded pointers; this allows a 64-bit application to address more memory than a 32-bit applications.
Porting 32-bit code to 64-bit code requires making modifications to ensure that it adheres to 64-bit programming guidelines. When compiling LabWindows/CVI applications for a 64-bit machine, the LabWindows/CVI compiler will flag warnings to help ensure that your code is 64-bit ready. You can review the list of common compiler warnings in the LabWindows/CVI Help to get guidance for properly porting 32-bit code to 64-bit code.Below is an example of compiler warnings that were flagged when compiling a LabWindows/CVI application for a 64-bit machine:
You should also be aware that various LabWindows/CVI functions and attributes were added or updated in LabWindows/CVI 2009 to ensure that projects can compile as both 32-bit and 64-bit applications. Below you will see changes to functions included in toolbox.h from LabWindows/CVI 9.0 and LabWindows/CVI 2009:
LabWindows/CVI 9.0
LabWindows/CVI 2009
Did you find this tip useful? Rate this document or add a comment below.
If you give this a try, share your experience! Add a comment below.
