Filter
Top Products
Chapter 3 Windows 95/NT Compiler/Linker Issues
LabWindows/CVI Programmer Reference Manual 3-16
©
National Instruments Corporation
default library directive, and the linker does not explicitly include a C library in the link, the
linker reports unresolved function references in the object modules.
Object and static library files that LabWindows/CVI creates do not contain a default library
directive. This has different implications for each compiler.
Microsoft Visual C/C++
If you include in your project at least one object file that contains a default library directive,
the Visual C linker uses that library to resolve references in all object and library files, even
the files you create in LabWindows/CVI. Object files you create in Visual C usually contain
default library directives.
If you do not include in your project any object files or libraries you create in Visual C, you
can add the following Visual C libraries to the project to avoid link errors:
libc.lib
oldnames.lib
In the Visual C development environment, add these library names using the Input category
in the Link tab of the Project Settings dialog box.
Borland C/C++
No problems exist with the absence of default library directives when you use the Borland
compiler.
Watcom C/C++
Like Visual C, at least one object file must contain a default library directive to cause the
C library to be linked in. In addition, Watcom also requires a default library directive for
floating-point support.
If you do not include in your project any object files with the required directives, add the
following libraries, in the order shown, to the Libraries setting in the Windows Linking
Switches dialog box:
clib3s
math387
noemu387
Symantec C/C++
Each object file must have the default library directive for the C library. You must explicitly
add the Symantec C library to your project. The library filename is
snn.lib and it is in the
lib subdirectory under the Symantec installation directory.
00ProRef.book : 06chap03.fm Page 16 Monday, March 9, 1998 3:23 PM