Q: What are the key features of the LabWindows/CVI 2013 Run-Time Module for Linux? (Available Jan 8, 2014)
The LabWindows/CVI Run-Time Module for Linux provides LabWindows/CVI libraries for Linux so you can compile and run LabWindows/CVI applications on Linux. The module does not offer a LabWindows/CVI interactive development environment (IDE) for Linux.
The latest version of the LabWindows/CVI Run-Time Module for Linux includes a new TDMS library for high performance data streaming to disk, over 100 new advanced analysis libraries and new features for customizing UI controls. Users can also take advantage of concurrent builds across multiple cores and support for new distributions of Red Hat, Scientific Linux and OpenSUSE.
Q: Can I port any existing LabWindows/CVI application to Linux?
You can port existing LabWindows/CVI applications to Linux as long as the application does not use any of the unsupported library functions. In general, following a few simple guidelines assures the portability of a LabWindows/CVI application:
- Write code in strict ANSI C
- Observe and repair all LabWindows/CVI compile, link, and run-time diagnostics
- Avoid using system-dependent calls when possible
- Avoid using nonportable image formats and fonts in your user interface
After installing the LabWindows/CVI Run-Time Module for Linux, refer to the Building Multiplatform Applications LabWindows/CVI Help topic for tips and guidelines on how to write platform-independent LabWindows/CVI applications.
Q: How do I install the module?
You can install the LabWindows/CVI Run-Time Module for Linux by running the INSTALL script that is provided. The INSTALL script ensures that all software requirements are met. LabWindows/CVI by default is installed under the following locations:
Q: How do I build and run my LabWindows/CVI project?
Once you have developed and sufficiently tested your application on Windows, you must copy your project, including source files, to a Linux machine. You then recompile your files on Linux. Use the cvicc command to build a LabWindows/CVI project or compile a source file.
The following commands are available:
||Shows the command syntax. Adding -help and -? also displays the command syntax.
||Builds the release target of project.prj.
|cvicc project.prj project2.prj
||Builds the release targets of project.prj and project2.prj.
||Compiles file.c with default build options.
|cvicc file.c file2.c
||Compiles file.c and file2.c with default build options.
|cvicc file.c project.prj
||Compiles file.c with build options you set for project.prj. file.c does not need to be included in project.prj. project.prj is not built.
|cvicc file.c file2.c project.prj
||Compiles file.c and file2.c with build options you set for project.prj. The source files do not need to be included in project.prj. project.prj is not built.
You can pass any number of source files to be compiled at one time. You can pass any number of projects to be built at one time. If you specify any number of source files, you can specify only one project file.
The compiler returns 0 if all targets are created successfully. If there is any error creating the target, or the build could not start, the compiler returns -1.
The following additional arguments are available:
||Creates the debuggable version of the target. This argument applies only for building projects.
||Forces LabWindows/CVI to recompile all source files you specify and all source files in projects you specify.
||Copies all build output to the logfile you specify.
||Adds more compiler defines to any compiler defines that are set in the project. You can specify multiple defines.
||Indicates that the specified library is required by the project.
||Adds the specific path to the list of locations that cvicc uses to search include files.
For more information about the cvicc command, refer to the Building a Linux Application help topic.
Q: How do I debug my LabWindows/CVI application once I have compiled and built it on Linux?
The LabWindows/CVI Run-Time Module for Linux does not include an IDE for Linux. Instead, you should compile your LabWindows/CVI application with cvicc using the debug switch. You can then use any of the debugging tools that are available on Linux like ddd or gdb to debug your application.
Q: Where is the documentation installed on Linux?
The readme.txt is installed under <installdir>/natinst/cvi2013. The readme provides installation instructions as well as information about building LabWindows/CVI projects and known issues. Use a Web browser to view the LabWindows/CVI Run-Time Module for Linux Help at <InstallDir>/natinst/cvi2013/help/index.htm. The documentation includes a reference for supported functions on Linux.
Q: Where can I purchase the LabWindows/CVI Run-Time Module for Linux?
Visit the LabWindows/CVI Run-Time Module for Linux product page.
Q: Do I need to purchase run-time licenses for every LabWindows/CVI Linux application I deploy?
You do not need additional deployment licenses for distributing applications that were created using the LabWindows/CVI Run-Time Module for Linux.
LabWindows/CVI Resource Page